From: "Mike Snitzer" <snitzer@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: forced umount?
Date: Fri, 16 Mar 2007 23:06:52 -0500 [thread overview]
Message-ID: <170fa0d20703162106v47dc13e1u1ae5381576f372ed@mail.gmail.com> (raw)
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/
Its fairly clear that these efforts (e.g. badfs patches) haven't been
given serious consideration for upstream inclusion. Do others see
value in the ability to _reliably_ force a umount by having Linux
discard all IOs, open files, dirty inode buffers, etc of a "bad"
blockdevice? The goal is to not impact the availability or integrity
of Linux while doing so.
Is this forced umount work even considered worthwhile by the greater
Linux community? Is anyone actively working on this?
Mike
next reply other threads:[~2007-03-17 4:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 4:06 Mike Snitzer [this message]
2007-03-17 4:27 ` forced umount? 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
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=170fa0d20703162106v47dc13e1u1ae5381576f372ed@mail.gmail.com \
--to=snitzer@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--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).