From: Steve Dickson <SteveD@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Christopher T Vogan <cvogan@us.ibm.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSERR_STALE on umount with 3.10.0.RC5 kernel
Date: Wed, 26 Jun 2013 15:20:40 -0400 [thread overview]
Message-ID: <51CB3F08.9050005@RedHat.com> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA93F422610@SACEXCMBX04-PRD.hq.netapp.com>
On 18/06/13 15:59, Myklebust, Trond wrote:
>> -----Original Message-----
>> From: Christopher T Vogan [mailto:cvogan@us.ibm.com]
>> Sent: Tuesday, June 18, 2013 3:56 PM
>> To: Myklebust, Trond
>> Cc: linux-nfs@vger.kernel.org
>> Subject: Re: NFSERR_STALE on umount with 3.10.0.RC5 kernel
>>
>> The NFS server uses UMNT as a signal to remove the client from its mount
>> table. Also at this time the Server cleans up other information about the now
>> disconnected client. Why would the client attempt to access the NFS server
>> once it has stated its going to unmount? I do not see the point of the
>> GETATTR request after UMNT call.
>
> As I said, the umount.nfs utility is doing the umount system call after UMNT, so the
> client does a lookup of the umount path at that time.
>
> IOW: This has nothing to do with the kernel. If you feel it is a bug, then please ask
> SteveD to file a fix against nfs-utils.
>
I just took a look at the umount code and it appears the UMNT call and
umount() system call are being done in the correct order...
The UMNT call is done in nfs_umount23() which is follow by either
mnt_context_do_umount() (if using the libmount code) or del_mtab()
which make the umount() system call....
Would it be possible to post a bzip2 binary network trace file so I can
poke around... something similar:
tshark -w /tmp/data.pcap host <server>
bzip2 /tmp/data.pcap
steved.
next prev parent reply other threads:[~2013-06-26 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 13:47 NFSERR_STALE on umount with 3.10.0.RC5 kernel Christopher T Vogan
2013-06-18 15:09 ` Myklebust, Trond
2013-06-18 19:55 ` Christopher T Vogan
2013-06-18 19:59 ` Myklebust, Trond
2013-06-26 19:20 ` Steve Dickson [this message]
2013-06-26 19:25 ` Myklebust, Trond
2013-06-26 21:24 ` Christopher T Vogan
2013-06-27 0:51 ` Myklebust, Trond
2013-06-27 4:41 ` Jeff Layton
2013-06-28 12:06 ` Jeff Layton
2013-09-10 20:18 ` Christopher T Vogan
2013-06-27 19:25 ` Christopher T Vogan
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=51CB3F08.9050005@RedHat.com \
--to=steved@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=cvogan@us.ibm.com \
--cc=linux-nfs@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