From: Chuck Lever <chuck.lever@oracle.com>
To: Guillaume Rousse <Guillaume.Rousse-MZpvjPyXg2s@public.gmane.org>
Cc: Linux NFSv4 mailing list <nfsv4@linux-nfs.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: unmount -l does not send unmount request to the server
Date: Fri, 19 Mar 2010 16:22:32 -0400 [thread overview]
Message-ID: <4BA3DD08.20209@oracle.com> (raw)
In-Reply-To: <4B9D49CC.8080603-MZpvjPyXg2s@public.gmane.org>
On 03/14/2010 04:40 PM, Guillaume Rousse wrote:
> 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_DETAC=
H)
>> indicates whether the kernel was able to completely unmount that fil=
e
>> 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 be=
ing
>> 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=
?
You might consider filing a bug in the NFSv4 bugzilla on linux-nfs.org.
--=20
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2010-03-19 20:24 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
[not found] ` <4B9D49CC.8080603-MZpvjPyXg2s@public.gmane.org>
2010-03-19 20:22 ` Chuck Lever [this message]
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=4BA3DD08.20209@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Guillaume.Rousse-MZpvjPyXg2s@public.gmane.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.