[Bug 20717] Improve async/sync writing behaviour for removable devices

Chris Weiss cweiss at gmail.com
Fri Mar 3 18:46:57 UTC 2006


Public bug report changed:
https://launchpad.net/malone/bugs/20717

Comment:
um, i understand the flash wear part, but for disk performance, the data
still takes the same amount of time to actualy write to the disk, sync
or not.  it's just a matter of the user being told when the data is
really and completely commited to disk.

I'd like to petition to reopen this bug, data loss (which just confused
the hell out of me for 20 minutes with a 1GB flash disk) is a LOT bigger
deal then wearing out the flash, in fact this async option just cause
not only FAT corruption but also uneeded writes to the flash as I have
to keep guessing when it was really done writting so I could unplug the
dive.

your efforts to save my flash have now caused extra wear.  I'll manage
my own flash lifetime thank you, and I don't care about performance as
much as knowing when the data is commited to disk.  again, async has not
helped performance (still takes as long as it takes) and has actualy
hurt my flash lifetime.  mission NOT accomplished.




More information about the kernel-bugs mailing list