Hi, 2013/3/4 <q1we...@i.com.ua>: > Hi, > >> os-prober uses 'mount -o ro', or grub-mount from 1.45: > > Please excuse me if this is trivial, but > '-o ro' does not prevent write access! > According to man: > > "Note that, depending on the filesystem type, state and kernel > behavior, the system may still write to the device. For example, > Ext3 or ext4 will replay its journal if the filesystem is dirty. > To prevent this kind of write access, you may want to mount ext3 > or ext4 filesystem with "ro,noload" mount options or set > the block device to read-only mode, see command blockdev(8)." > > Maybe for XFS also? To clarify my prior email os-prober tries grub-mount which is expected to be non-desctructive and falls back to mount -o ro in case grub-mount failed. It can be checked in /usr/share/os-prober/common.sh .
Setting block device to read-only should not be done, since like in the scenario this bug covers the block device can be exported and used via network. IMO the logic for setting the right fs dependent option to mount the fs in true read-only mode should be implemented in the mount command instead of os-prober to let other programs using mount use it, too. BTW, the XFS option is "norecovery" for skipping log recovery. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
