[lkml]   [2005]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Sync option destroys flash!
On Fri, May 13, 2005 at 11:58:19AM -0600, Zan Lynx wrote:
> Err, no, the sync flag is a wonderful idea. I use sync on jump drives
> (although I won't now that I've read about this problem) because I can
> copy a file to it and as soon as the green light stops flashing I can
> yank it out without bothering to click or type anything to "eject" it.
> Requiring "eject" on removable media is a dumb idea.
> Perhaps FAT updates could be cached and delayed until some # of ms after
> the last write.
> Turning the sync flag off and adjusting the values
> in /proc/sys/vm/dirty_* would have the same effect, but would change it
> on all devices, not just removables.
> Maybe we need a way to set dirty_* per block device?

Well you could just make a way to start writing data to the device
within 1s or so, and then assuming your device has a light indicating
activity (it better), then when the light has been off for a couple of
seconds, you can remove it.

I wish every removeable media drive had a soft eject button on it and a
locking mechanism like zip drive, jax drive, cdrom/dvd, mac floppy
drive, etc. They are seriously needed to tell the os what the user is
trying to do to the poor media. That way the os can see when the user
wants to take the media out, flush it, unlock and eject. Doesn't help
if the eject button doesn't signal the OS of course, but at least on
some drives it does. Being able to remove media from a system without
telling the OS first is just bad design.

Len Sorensen
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-05-13 20:18    [W:0.056 / U:8.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site