From: Arjan van de Ven <arjan@infradead.org>
To: Mike Snitzer <snitzer@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: forced umount?
Date: Sun, 18 Mar 2007 20:16:19 +0100 [thread overview]
Message-ID: <1174245379.3538.252.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <170fa0d20703162106v47dc13e1u1ae5381576f372ed@mail.gmail.com>
On Fri, 2007-03-16 at 23:06 -0500, Mike Snitzer wrote:
> I'm interested in understanding the state of Linux with regard to
> _really_ forcing a filesystem to unmount.
>
> There is a (stale) project at OSDL that has various implementations:
> http://developer.osdl.org/dev/fumount/
the problem with the people who say they want forced umount is.. that
most of the time they either want
1) get rid of the namespace entry
or
2) want to stop any and all IO to a certain device/partition
1) is already supported with lazy umount (umount -l)
for 2), it's not forced umount that they want, it's really an IO
disconnect (which scsi supports btw in 2.6 kernels).
So.. depending on which of the 2 you are, it's there. Just it's not
called "forced umount".....
next prev parent reply other threads:[~2007-03-18 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 4:06 Mike Snitzer
2007-03-17 4:27 ` Jeremy Fitzhardinge
2007-03-17 5:37 ` Mike Snitzer
2007-03-17 10:53 ` Pekka Enberg
2007-03-26 21:34 ` Phillip Susi
2007-03-27 6:32 ` Pekka J Enberg
2007-03-28 14:46 ` Phillip Susi
2007-03-17 5:24 ` Gene Heskett
2007-03-18 19:16 ` Arjan van de Ven [this message]
2007-03-18 20:13 ` Matthew Wilcox
2007-03-18 23:45 ` Jan Engelhardt
2007-03-18 20:20 ` Mike Snitzer
2007-03-26 11:21 ` Pozsar Balazs
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=1174245379.3538.252.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@gmail.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
all inboxes | Powered by JetHome®