https://bugzilla.novell.com/show_bug.cgi?id=188187 jeffm@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com, dkukawka@novell.com AssignedTo|kernel- |kde-maintainers@suse.de |maintainers@forge.provo.nove| |ll.com | ------- Comment #5 from jeffm@novell.com 2006-10-11 09:12 MST ------- To answer the original question: FAT32 (at least in our kernels, I don't know if this is upstream yet) has a -oflush option that pushes data to disk more quickly than normal writeback would. It isn't as slow or safe as -osync, but if you don't pull out your USB drive while the lights are still flashing, it should be safe. NTFS doesn't have such an option, so -osync is used. Without it, you'd see severe file system corruption if the device was removed before the data was entirely written out. As a note, -oro,async is effectively the same as -oro. async only applies to writing out data and if the file system is mounted read only, there's nothing to write. That said, this isn't a kernel problem. The kernel is doing what it's told here. There are defaults, such as read-write, in place and those shouldn't change. If read-only behavior is desired, KDE/HAL needs to pass the read-only flag. I'm returning this one back to the KDE team and CCing Kay and Danny so this can get sorted out. -- 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, or are watching someone who is.