From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux NFSv4 mailing list <nfsv4@linux-nfs.org>
Subject: Re: unmount -l does not send unmount request to the server
Date: Sun, 14 Mar 2010 21:40:44 +0100 [thread overview]
Message-ID: <4B9D49CC.8080603@inria.fr> (raw)
In-Reply-To: <7123090D-5BB9-4CF5-A024-56345DD8136F@oracle.com>
Le 19/01/2010 17:37, Chuck Lever a =E9crit :
> As far as I understand it, "-l" means the kernel will do the local
> detach from the system's file name space whenever there are no more
> users (ie entirely asynchronously). I don't think umount2(MNT_DETACH)
> indicates whether the kernel was able to completely unmount that file
> system by the time the call returns, so there's perhaps no way for
> umount.nfs to know whether it should send the UMNT request. If the
> server is slow or unresponsive, that file system won't be unmounted
> until long after the umount.nfs command has exited.
> =
> This shouldn't be much of a big deal, since the server's rmtab is
> "ornamental" according to the man page. No one should rely on it being
> accurate.
> =
> A possible way to fix this is to have the kernel send the UMNT.
It makes sense, but it doesn't seem to trigger much interest :)
Should I open a bug somewhere, to ensure the issue won't be forgotten ?
-- =
BOFH excuse #196:
Me no internet, only janitor, me just wax floors.
next prev parent reply other threads:[~2010-03-14 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B530EFF.9000205@inria.fr>
2010-01-19 16:37 ` unmount -l does not send unmount request to the server Chuck Lever
2010-03-14 20:40 ` Guillaume Rousse [this message]
[not found] ` <4B9D49CC.8080603-MZpvjPyXg2s@public.gmane.org>
2010-03-19 20:22 ` Chuck Lever
2010-03-19 20:57 ` Trond Myklebust
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=4B9D49CC.8080603@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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