From: Ian Turner <vectro@vectro.org>
To: linux-kernel@vger.kernel.org
Subject: waiting for MNT_DETACH
Date: Sun, 2 Jul 2006 14:51:24 -0400 [thread overview]
Message-ID: <200607021451.24595.vectro@vectro.org> (raw)
Hello all,
I administer a two-node high-availability cluster using DRBD and heartbeat.
One of my concerns is that at failover time, the replicated filesystem might
be in use. I can stop the official services that use the filesystem, but some
other transient scripts might have reason to probe it for a second or two.
umount -l seems like the answer to this question, in that one can ensure no
new accesses will be made to the filesystem, while those that exist can take
their time to finish. The catch is, there does not appear to be a way to tell
if the unmount has really completed or not.
So, here's the question: Is there a way to check if a call to umount2(...,
MNT_DETACH) has completed or not?
Thanks,
--Ian Turner
next reply other threads:[~2006-07-02 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 18:51 Ian Turner [this message]
2006-07-03 22:43 ` Ingo Oeser
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=200607021451.24595.vectro@vectro.org \
--to=vectro@vectro.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
all inboxes | Powered by JetHome®