Samuel Thibault wrote:
Hm, so the root cause there seems that the installer found 2 legs of a
mirror and mounted them independently, recovering them independently...
But why did that cause problems?
Because that thrashed his data (or at least it didn't help to keep data
safe).
Other options you may have in the installer, though, is to check for
md superblocks before mounting bare partitions, or maybe use the
BLKROSET ioctl to set the block device to read-only prior to mount,
for added insurance...
That's one the things proposed in the bugreport yes.
The reason I suggest other options is because intentionally mounting a
corrupted FS may not really be the way you want to go... norecovery on
xfs at least is an option of last resort, not something to use by default.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
