From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: "umount" of ceph filesystem that has become unavailable hangs forever
Date: Thu, 17 Jun 2010 11:36:58 +0000 (UTC) [thread overview]
Message-ID: <hvd1cq$5tm$3@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1006161151420.22082@cobra.newdream.net
> I'm hesitant to add a blanket umount timeout, as that could prevent
> proper writeout of cached data/metadata in some cases. So I think the
> goal should be that if a normal umount hangs for some reason, you should
> be able to intervene to add the 'force' if things don't go well.
the option to force the umount if the regular umount hangs would be really
cool.
- Thomas
next prev parent reply other threads:[~2010-06-17 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:35 "umount" of ceph filesystem that has become unavailable hangs forever Peter Niemayer
2010-06-16 18:56 ` Sage Weil
2010-06-17 11:36 ` Thomas Mueller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-23 11:36 Sébastien Paolacci
2010-07-23 11:42 ` Anton V.G.
2010-07-23 16:56 ` Sage Weil
2010-07-24 8:36 ` Sébastien Paolacci
2010-07-27 10:49 ` Anton VG
2010-07-27 17:18 ` Sage Weil
2010-07-23 11:43 Anton
2010-07-23 12:08 ` Sébastien Paolacci
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='hvd1cq$5tm$3@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@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