Comment 8 for bug 1857914

Hello
It took me a little while to reproduce the incident.
I only wanted to put what seemed to me the minimum necessary.
But I couldn't reproduce the incident.
So I replayed the initial scenario. I also couldn't rebuild.
So I destroyed the inaccessible partition to make a new one now called SDB1

You will find attached a file containing all the commands executed as well as some returns and three trace files for returns of certain commands.

You will find that I did at the same time for another partition which has no errors.

At the beginning the order of the partitions was 1 2 3 4. The error was on the partitions 2 and 3 but the partition 1 had not been treated.
I deleted partition 1 to put it at the end of the disk. I was never able to cause the incident.
So I deleted partitions 1 and 3. I just recreated them.

My opinion is that the bug is triggered for partitions stored at the beginning of the disc !!!

Good research.