vfat 'sync' mount option is not really 'sync'

Bug #8693 reported by Martin Pitt
36
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Chuck Short

Bug Description

In Ubuntu we use to mount removable devices with the 'sync' option, so that
users can just rip out their usb devices without having it to unmount manually.
However, this does not really work, after copying a large file onto the device,
the copy will be corrupted if the device is unplugged immediately after cp
finishes; also, if sync is called after the copy operation, it still writes data
onto the device.

Revision history for this message
Matt Zimmerman (mdz) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

It seems that this bug is not trivial to fix, so this is probably a Hoary issue.

Revision history for this message
Martin Pitt (pitti) wrote :

Hi Herbert!

Do you happen to know whether and when this will be fixed on the kernel front?

Since this is really a kernel bug, would you mind if it is assigned to you?

Revision history for this message
Herbert Xu (herbert-gondor) wrote :

Yes this is a kernel bug. Matt, I presume we're leaving this alone for now?

Revision history for this message
Matt Zimmerman (mdz) wrote :

This is a feature enhancement for the kernel, and so it is too late for Warty.
We will likely do something about it during the Hoary development cycle.

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 9964 has been marked as a duplicate of this bug. ***

Revision history for this message
Matt Zimmerman (mdz) wrote :

It looks like the vfat maintainer is working on this:

http://lkml.org/lkml/2004/11/24/133

Revision history for this message
Chuck Short (zulcss) wrote :

I pinged the author of the patch. Hopefully we will hear back from him.

Revision history for this message
Chuck Short (zulcss) wrote :

I heard back from the author and he sent me a whole list of patches to be
applied to vfat. However, he is not going to submit them upstream until
2.6.12-preX. Matt, do you want these patches incorporated into hoary, or wait
til hoary+1?

chuck

Revision history for this message
Matt Zimmerman (mdz) wrote :

What is your opinion of the patches, with regard to potential for
destabilization? If they are very simple, we can consider it. However, if the
author is not planning to submit them yet, does that mean he does not consider
them ready?

Revision history for this message
Chuck Short (zulcss) wrote :

I asked Ogawa Hirofumi about it, he believes that they are safe to use however
if you have critical data or if you dont wish to test them, dont use them. I can
build a test kernel with them this weekend and test them out. I dont have
anything critical on my usb jump drive that I need.

chuck

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 12763 has been marked as a duplicate of this bug. ***

Revision history for this message
Matt Zimmerman (mdz) wrote :

Did you have a chance to test the patches? I'm starting to feel that it would
be safer to delay this to 5.10

Revision history for this message
Chuck Short (zulcss) wrote :

This should be fixed in 2.6.12

Revision history for this message
Chuck Short (zulcss) wrote :

New kernel will hit the archive soon for breezy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.