From: Arjan van de Ven <arjan@linux.intel.com>
To: Ric Wheeler <ric@emc.com>
Cc: Valerie Henson <val_henson@linux.intel.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: topics for the file system mini-summit
Date: Sat, 03 Jun 2006 16:13:29 +0200 [thread overview]
Message-ID: <44819909.5020801@linux.intel.com> (raw)
In-Reply-To: <44819398.4030603@emc.com>
Ric Wheeler wrote:
>>
> Any thoughts about what the right semantics are for properly doing a
> forced unmount and how whether it is doable near term (as opposed to the
> more strategic/long term issues laid out in this thread) ?
I would like to ask you take one step back; in the past when I have seen
people want "forced unmount" they wanted instead somethings else that they
thought (at that point incorrectly) forced unmount would solve.
there's a few things an unmount does
1) detach from the namespace (tree)
2) shut down the filesystem to
2a) allow someone else to mount/fsck/etc it
2b) finish stuff up and put it in a known state (clean)
3) shut down IO to a fs for another node to take over
(which is what the "incorrectly" is about technically)
next prev parent reply other threads:[~2006-06-03 14:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 21:44 topics for the file system mini-summit Ric Wheeler
2006-05-26 16:48 ` Andreas Dilger
2006-05-27 0:49 ` Ric Wheeler
2006-05-27 14:18 ` Andreas Dilger
2006-05-28 1:44 ` Ric Wheeler
2006-05-29 0:11 ` Matthew Wilcox
2006-05-29 2:07 ` Ric Wheeler
2006-05-29 16:09 ` Andreas Dilger
2006-05-29 19:29 ` Ric Wheeler
2006-05-30 6:14 ` Andreas Dilger
2006-06-07 10:10 ` Stephen C. Tweedie
2006-06-07 14:03 ` Andi Kleen
2006-06-07 18:55 ` Andreas Dilger
2006-06-01 2:19 ` Valerie Henson
2006-06-01 2:42 ` Matthew Wilcox
2006-06-01 3:24 ` Valerie Henson
2006-06-01 12:45 ` Matthew Wilcox
2006-06-01 12:53 ` Arjan van de Ven
2006-06-01 20:06 ` Russell Cattelan
2006-06-02 11:27 ` Nathan Scott
2006-06-01 5:36 ` Andreas Dilger
2006-06-03 13:50 ` Ric Wheeler
2006-06-03 14:13 ` Arjan van de Ven [this message]
2006-06-03 15:07 ` Ric Wheeler
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=44819909.5020801@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ric@emc.com \
--cc=val_henson@linux.intel.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;
as well as URLs for NNTP newsgroup(s).