From: Oliver Neukum <oliver@neukum.org>
To: James Bruce <bruce@andrew.cmu.edu>
Cc: 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: Tue, 12 Oct 2004 10:24:44 +0000 [thread overview]
Message-ID: <200410121224.44910.oliver@neukum.org> (raw)
In-Reply-To: <416B9436.3010902@andrew.cmu.edu>
> 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.
> course not currently handled very well, but writing would be damn near
> impossible to unmount well. In order to keep the device consistent, the
> only thing you can do is wait for the user to reinsert the device and
> then clear your caches. However they might have modified the storage in
You cannot. That's giving mlock() to everybody.
[..]
> Automated mounting with special fixed names can already be done, this
> has little to do with forced dismounting. Use something like udev for
> this part.
Exactly.
[..]
> All I ever expect the kernel to eventually support is forced dismount of
> devices that haven't been written to. I think from there its up to
Devices break. You have to cope with devices going away suddenly.
You are not required to ensure data integrity in all cases, but the system
must not suffer. To allow that you must be able to get rid of the mounts
even if users do not cooperate.
Regards
Oliver
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-10-12 10:24 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 [this message]
2004-10-12 10:46 ` bert hubert
2004-10-13 19:01 ` Linas Vepstas
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=200410121224.44910.oliver@neukum.org \
--to=oliver@neukum.org \
--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 \
/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).