From: Denis Vlasenko <vda@ilport.com.ua>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: mhw@wittsend.com, linux-kernel@vger.kernel.org
Subject: Re: Sync option destroys flash!
Date: Wed, 18 May 2005 10:03:29 +0300 [thread overview]
Message-ID: <200505181003.29501.vda@ilport.com.ua> (raw)
In-Reply-To: <20050516231839.GB8032@hh.idb.hist.no>
On Tuesday 17 May 2005 02:18, Helge Hafting wrote:
> On Sun, May 15, 2005 at 10:00:26PM +0300, Denis Vlasenko wrote:
> >
> > What we really need, is a less thorough version of O_SYNC.
> > O_SYNC currently guarantees that when syscall returns, data
> > is on media (or at least in disk drive's internal cache :).
> >
> > This is exactly what really paranoid people want.
> > Journalling labels, all that good stuff.
> >
> > But there are many cases where people just want to say
> > 'write out dirty data asap for this device', so that
> > I can copy files to floppy, wait till it stops making
> > noise, and eject a disk. Samr for flash if it has write
> > indicator (mine has a diode).
> >
> I don't really see the need for a new mode.
> Mount without o_sync, but use the sync command
> once to get things written out. Or
> use the umount command before ejecting, it syncs
> the device before returning. I use umount all the time
> when using compactflash. The wear is minimal.
I just want this to happen automatically
(automounter helps with this) and at once
(i.e. without delay prior to start of writeout).
Caching (delaying) writes for hard disks makes tons of sense,
but not as much for removable media.
--
vda
next prev parent reply other threads:[~2005-05-18 7:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 16:20 Sync option destroys flash! Michael H. Warfield
2005-05-13 17:17 ` Lennart Sorensen
2005-05-13 17:53 ` Michael H. Warfield
2005-05-13 18:09 ` Lennart Sorensen
2005-05-13 18:21 ` Michael H. Warfield
2005-05-13 18:26 ` Lennart Sorensen
2005-05-13 18:52 ` Flash device types Mark Rustad
2005-05-13 18:53 ` Sync option destroys flash! Michael H. Warfield
2005-05-13 17:58 ` Zan Lynx
2005-05-13 18:13 ` Lennart Sorensen
2005-05-13 18:40 ` Alan Cox
2005-05-13 19:10 ` Michael H. Warfield
2005-05-13 22:00 ` Alan Cox
2005-05-13 22:22 ` Måns Rullgård
2005-05-13 23:24 ` Jon Masters
2005-05-13 23:01 ` Jeffrey Hundstad
2005-05-13 23:27 ` Jon Masters
2005-05-14 10:17 ` Jörn Engel
2005-05-14 1:05 ` Michael H. Warfield
2005-05-17 13:30 ` Lennart Sorensen
2005-05-13 21:25 ` Lee Revell
2005-05-13 22:43 ` Alan Cox
2005-05-15 19:00 ` Denis Vlasenko
2005-05-16 0:23 ` Mark Lord
2005-05-16 9:29 ` David Woodhouse
2005-05-16 16:42 ` Pavel Machek
2005-05-16 13:01 ` Richard B. Johnson
2005-05-16 23:18 ` Helge Hafting
2005-05-18 7:03 ` Denis Vlasenko [this message]
2005-05-17 7:59 ` Colin Leroy
[not found] <43Ldl-NM-25@gated-at.bofh.it>
[not found] ` <43M9s-1B8-39@gated-at.bofh.it>
[not found] ` <43MCx-1UF-27@gated-at.bofh.it>
[not found] ` <43MVz-2hL-1@gated-at.bofh.it>
2005-05-13 23:59 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2005-05-14 2:43 linux
2005-05-17 13:36 ` Lennart Sorensen
2005-05-17 20:31 ` linux
2005-05-17 20:43 ` Richard B. Johnson
2005-05-18 13:37 ` Lennart Sorensen
[not found] <43UT5-jT-3@gated-at.bofh.it>
2005-05-14 4:34 ` Robert Hancock
2005-05-18 11:13 linux
2005-05-18 12:01 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200505181003.29501.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mhw@wittsend.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox