https://bugzilla.novell.com/show_bug.cgi?id=300694#c8 Szabolcs Szakacsits <szaka@sienet.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |szaka@sienet.hu --- Comment #8 from Szabolcs Szakacsits <szaka@sienet.hu> 2007-08-21 05:07:16 MST --- Hi! From NTFS-3G upstream: I think the fundamental problem here is that that the install/boot shouldn't stop if non OS critical file system can't be mounted. That is, trying to make NTFS mounted is not the right approach here, in my opinion. There can be many, different reasons why a file system is unmountable. NTFS-3G has extra sanity checks which are not included in ordinary file system drivers (i.e. it can detect unconfigured, unactivated, not correctly setup RAID, Dynamic Disks, etc). The "unclean volume" error is caused basically always by ntfsresize which is completely safe to ignore. Setting the NTFS volume flag dirty is used as a workaround for partition editors not doing correct NTFS partitioning. So, ntfsresize tricks Windows via the file system to fix the Windows partition, not the file system. The name of the 'force' mount option is also misleading. What it does in real is it ignores the file system dirty flag which was set by ntfsresize (see above) and it fixes/resets the NTFS journal file if needed. It's planned to ignore the otherwise unused "dirty flag" without a warning by default and use a new, more explanatory 'fix' mount option for the second and online repair cases. The driver already fixes silently minor corruptions what other drivers leave behind and this approach will be used more intensively in the future (ZFS also does online fsck, offline fsck is the past). -- 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.