From: Linas Vepstas <linas@austin.ibm.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: James Bruce <bruce@andrew.cmu.edu>, bert hubert <ahu@ds9a.nl>,
Greg KH <greg@kroah.com>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.9-rc4] USB && mass-storage && disconnect broken semantics
Date: Wed, 13 Oct 2004 19:01:36 +0000 [thread overview]
Message-ID: <20041013190136.GD12237@austin.ibm.com> (raw)
In-Reply-To: <200410121224.44910.oliver@neukum.org>
On Tue, Oct 12, 2004 at 12:24:44PM +0200, Oliver Neukum was heard to remark:
>
> > With *nix, most data only gets written at unmount, so the only way this
> > can "sanely" work is for mounts you haven't written to. That case is of
>
> This is not a law of nature. You can mount sync as well. That, of course,
> sucks in terms of performance and wear. A reasonable compromise
> would be to do sync on close.
> Supermount did this years ago.
As a practical matter, sync-on-file-close should solve most
of the practical problem of data corruption if the device is
yanked before being onmounted. However, when I read
'man 2 open' there is no O_SYNC_ON_CLOSE.
Similarly 'man 8 mount' doesn't list any option -o synconclose
It sure would be nice to be able to set up a sync-on-file-close
in the hotplug equiv of /etc/fstab for USB devices ...
(When I think of sync-on-file-close, I don't mean 'global sync
when the file is closed', I mean 'sync only that file's data and
metadata only when the file is closed'. That way, you don't slow
down systems doing a lot of i/o on other, unrelated files)
--linas
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-10-13 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 12:07 [2.6.9-rc4] USB && mass-storage && disconnect broken semantics bert hubert
2004-10-11 15:37 ` Kay Sievers
2004-10-11 16:07 ` David Brownell
2004-10-12 5:54 ` bert hubert
2004-10-12 8:22 ` James Bruce
2004-10-12 10:24 ` Oliver Neukum
2004-10-12 10:46 ` bert hubert
2004-10-13 19:01 ` Linas Vepstas [this message]
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=20041013190136.GD12237@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=ahu@ds9a.nl \
--cc=bruce@andrew.cmu.edu \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
/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;
as well as URLs for NNTP newsgroup(s).