https://bugzilla.novell.com/show_bug.cgi?id=300694#c19 --- Comment #19 from Bernhard Kaindl <bk@novell.com> 2007-08-21 12:06:58 MST --- Created an attachment (id=158813) --> (https://bugzilla.novell.com/attachment.cgi?id=158813) Patch to automatically fall back to read-only mount if volume is dirty
Maybe best would be to create a boot.ntfs-3g that handles mounting of the ntfs-3g entries from fstab and add a "nontfs-3g" to -t option in boot.localfs.
So the handling of ntfs-3g would at least be in a central plase without unnecessary messing up boot.localfs. /etc/init.d/boot.ntfs-3g should then be part of ntfs-3g RPM.
Yes, I thought of this already to be sure that ntfs-3g does not cause any problems during system boot. Using 10.2, I tested what happens when a system is booted with a dirty NTFS volume in /etc/fstab after ntfs-3g fails to mount it: In this test the other non-root filesystem (/home) was mounted as usual (it was mounted before the ntfs volume but I think mount does not abort mounting when one fstab entry fails) and it printed this to the console Volume is scheduled for check. Please boot into Windows TWICE, or use the 'force' mount option. For example type on the command line: mount -t ntfs-3g /ntfs.image /media/ntfs -o force Or add the option to the relevant row in the /etc/fstab file: /ntfs.image /media/ntfs ntfs-3g defaults,force 0 0 boot.localfs ended with status "failed" but otherwise the system came up nicely. AFAICS, the implications which a separate ntfs-3g mount script would have are: 1) There would not even be an attempt to mount ntfs-3g volumes at boot if ntfs-3g is not installed, no error message would be seen. 2) The 'nontfs-3g' in /etc/init.d/boot.localfs would also cause that somebody who does not install our ntfs-3g rpm but installs ntfs-3g from source would have to also install a similar mount script or remove the nontfs-3g from /etc/init.d/boot.localfs 3) Mount failures of ntfs-3g would not be shown as an boot failure in boot.localfs but as one in the ntfs-3g mount script. Implication 1) may be desirable or not (maybe we should give an error during boot when ntfs-3g is in fstab but ntfs-3g is not installed), Implication 2) is likely bearable and 3) is likely nice, but I do not see a a pressing need from any of those. While this does not exclude the possiblity of a failed ntfs-3g mount at boot, the new attachment of this comment has the first working patch to fall back to an read-only mount if the NTFS volume is dirty. The previous patch to allow to mount a dirty volume with "ro" (without force) is part of this patch because it builds on it. I think I am also half-way done to implement that specifying "rw" explicitly, not implicitly as part of the "defaults" mount option causes ntfs-3g to mount read-write or fail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.