On 14/12/16 11:04, Mariusz Dabrowski wrote: > Hi, > this patch affects only reading GPT from disk. It fixes minor issue when > there > were no warning from mdadm when user was trying to create 1-disk RAID 0 > with > external metadata on disk with some partitions and given array size was > smaller > than total size of all partitions on this disk (mdadm failed to read GPT > because it was using wrong offset). > In both instances I'm thinking of, iirc, a user pulled a working array from one machine, tried to assemble it in another, then went back to the original machine and the GPT had disappeared. I'm clutching a bit at straws, but when the same bug bites more than one user, you think something must be behind it. And as you can tell from the scenario I describe, nothing *should* have been writing to disk, yet the disk got corrupted. > I couldn't reproduce those incidents so I can't tell that this patch > fixes the > root cause of this issue. It'll have to stay on the "mysterious" list then :-) > > Regards, > Mariusz Cheers, Wol -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
