https://bugzilla.novell.com/show_bug.cgi?id=309074#c8 Bernhard Kaindl <bk@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |szaka@sienet.hu Severity|Major |Blocker Status|NEW |ASSIGNED Summary|Installation finished with error |Dirty NTFS: Installation aborts after error | |message that NTFS partition can't be mounted --- Comment #8 from Bernhard Kaindl <bk@novell.com> 2007-09-24 08:38:24 MST --- Hi Thomas, now I agree with your statement in comment #9 in bug 300694: Let's revert the ntfs-3g change in yast2-storage and use the kernel's read-only NTFS filesystem as it's known to reliably mount the filesystem, whereas ntfs-3g does not do so yet (with the default options). Reason(s): Standard fstab semantics / fstab options not properly supported: * always mount the filesystem, no matter how broken the state of the filesystem is (if it *can* be mounted, mount it). Examples are: * FAT (which is very defensive and will spit error messages if it has errors, but if can mount, it will mount) and * hfsplus (which falls back to read-only if the filesystem was not cleanly unmounted, is marked locked or is marked journaled) * I made a patch which does the same which hfsplus does (fall back to read-only on dirty volumes) for ntfs-3g (it's attached to bug 300694), but unfortunately the need for it wasn't considered upstream yet, I hope it will in the future at some time tough. * Support for the user/users options in fstab not given. Would need suid ntfs-3g which is not considered safe so far or kernel-supported user mounting, which is an proposal of the fuse maintainer but which is in mainline yet. Raising severity to blocker because 300694 was already blocker and this is the same issue, just reappearing because we assumed that the update to the new version had fixed the issue. I fact it only touched one of the issues, but not one of the two remaining problems which I described the the second paragraph. I also changed the Summary to be more specific. We can still ship the ntfs-3g package, but I'll document the issues which it has in in it's package description. ntfs-config for read-write mounts: For users which want to mount to mount ntfs-3g read-write, we have the package ntfs-config, which is also not yet mature, but which is integrated into the desktop menu and which users can use (experimentally, as it does not use persistent file names, which is a must for external devices if you have more than one) to mount NTFS partitions read-write. I'll ask to ship it on the DVDs/CDs - so far it's not on the DVDs/CDs yet. Future permission support: I also want to add that an experimental patch which adds NTFS permission support has appeared and is being further improved, so the permissions model which ntfs-3g has now could be considered as "1st" generation and with NTFS permissions supported it should also be safer to mount read-write by default. -- 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.