[email protected] writes:
[snip]
>> Isn't is possible to avoid this problem by mounting an ext3 filesystem
>> as readonly ext2? Provided the filesystem isn't dirty it should be
>> doable. (And provided the filesystem doesn't use any ext3 extensions
>> that are incompatible with ext2.)
> from the last discussion I saw on the kernel mailing list, no. the act of
> mounting the ext3 filesystem as ext2 read-only will change it as the unsupported
> extentions get turned off (and I think the journal contents at least are lost as
> part of this)
The fact of the matter is that it really doesn't matter whether mounting
it read-only actually corrupts the data on disk or not. Regardless, it
should not be done, because you are accessing a dirty filesystem that is
still in use, and consequently there are no guarantees that either the
metadata or the file contents are consistent. It isn't necessary for
hibernation to be able to access mounted partitions anyway.
--
Jeremy Maitin-Shepard
-
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]
