https://bugzilla.novell.com/show_bug.cgi?id=300694#c3 Bernhard Kaindl <bk@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bk@novell.com AssignedTo|bk@novell.com |fehr@novell.com --- Comment #3 from Bernhard Kaindl <bk@novell.com> 2007-08-20 09:49:59 MST --- Hi Thomas, could it be that /mnt/windows/C was only created for vfat and ntfs but not now with ntfs-3g? This bug at least seems to suggest that. I will try to get ntfs-3g changed to mount also volumes which are scheduled for check (but then only mount them read-only, unless -oforce is used), but I do not know whether this will happen and if that will cover all possibilities of a mount of ntfs-3g failing. Thomas, could you either: a) switch back to fstype "ntfs" for ntfs-partitions b) tolerate an error from mounting partitions with ntfs-3g when they are mounted. (Note: ntfs-3g could be used somewhere outside of /mnt/windows, but as ntfs-3g currently same level permission support as FAT (only fixed for whole fs using mount flags), it's not desirable to use it seriously for system files) I think that b) would be most desirable to prevent the complete abort of the installation if an error mounting some windows NTFS partition fails. Having b) implemented after installation, in the installed system may also be desirable because that would allow to set the options, boot into windows, check the filesystem as described by the mount error which yast2 disk shows and boot back into Linux and not having to redo all mount options again. PS: Please remove "nls=utf8" from the ntfs-3g mount flags, it's ignored by ntfs-3g and replaced by the locale=en_US.UTF-8, which you already added. PPS: In bug 293429, coolo suggested to use fmask=133,dmask=022, so these should replace the umask=0002 which is currently in the default options string, because umask=0002 acts very different with ntfs-3g (default permissions are then 775 [rwxrwxr-x] instead of the default of 777, not 555 [r-xr-xr-x] instead of the default of 500 [r-x-------] as it is with ntfs). Having 644 for files and 755 for directories as caused by fmask=133,dmask=022 with ntfs-3g seems more desirable. Coolo also suggested: noauto,user, which I'd second. Then the NTFS windows partitions would not be mounted by default and then any error in mounting NTFS partitions would not occur at boot (or during installation) but when the user really wants to access them. Having many partitions mounted with ntfs-3g can -- 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.