From: Orion Poplawski <orion@cora.nwra.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs4 mount hanging suddenly
Date: Wed, 29 Feb 2012 16:21:34 -0700 [thread overview]
Message-ID: <4F4EB2FE.9040108@cora.nwra.com> (raw)
In-Reply-To: <20120229231732.GD6506@fieldses.org>
On 02/29/2012 04:17 PM, J. Bruce Fields wrote:
> On Wed, Feb 29, 2012 at 03:29:36PM -0700, Orion Poplawski wrote:
>> Just starting today, one of our user's nfs mounted home directory
>> has started locking up. Client is Fedora 16 32-bit, server is
>> CentOS 5.7 32-bit. Have not seen this particular problem elsewhere
>> (yet).
>>
>> I captured this trace on the server after the hang:
>>
>> http://sw.cora.nwra.com/tmp/marie-nfs-home-lwang-hang.pcap
>>
>> 1 0.000000 10.10.20.15 -> 10.10.10.1 NFS V4 COMP Call<EMPTY>
>> PUTFH;GETATTR GETATTR
>> 2 0.000133 10.10.10.1 -> 10.10.20.15 NFS V4 COMP Reply (Call
>> In 1)<EMPTY> PUTFH;GETATTR GETATTR
>> 3 0.000421 10.10.20.15 -> 10.10.10.1 TCP 879> nfs [ACK]
>> Seq=137 Ack=225 Win=17738 Len=0 TSV=3584653 TSER=2438333196
>> 4 0.000519 10.10.20.15 -> 10.10.10.1 NFS V4 COMP Call<EMPTY>
>> PUTFH;ACCESS ACCESS;GETATTR GETATTR
>> 5 0.000587 10.10.10.1 -> 10.10.20.15 NFS V4 COMP Reply (Call
>> In 4)<EMPTY> PUTFH;ACCESS ACCESS;GETATTR GETATTR[Unreassembled
>> Packet [incorrect TCP checksum]]
>> 6 0.040522 10.10.20.15 -> 10.10.10.1 TCP 879> nfs [ACK]
>> Seq=289 Ack=465 Win=17738 Len=0 TSV=3584694 TSER=2438333196
>> 7 0.451636 10.10.20.15 -> 10.10.10.1 NFS V4 COMP Call<EMPTY>
>> PUTFH;SAVEFH SAVEFH;OPEN OPEN;DELEGRETURN DELEGRETURN;Unknown
>
> That looks weird. Looking at the pcap--ok, the "delegreturn" is a
> mistake, there's no delegreturn there.
>
>> 8 0.451892 10.10.10.1 -> 10.10.20.15 NFS V4 COMP Reply (Call
>> In 7)<EMPTY> PUTFH;SAVEFH SAVEFH;OPEN OPEN(10008)
>
> That probably means the server is waiting for the client to return a
> delegation.
>
> Either the server's confused about their being a delegation, or the
> client's failing to return one it should?
>
> --b.
All way over my head. Any way to check in more detail?
thanks.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
next prev parent reply other threads:[~2012-02-29 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 22:29 nfs4 mount hanging suddenly Orion Poplawski
2012-02-29 23:17 ` J. Bruce Fields
2012-02-29 23:21 ` Orion Poplawski [this message]
2012-03-01 13:50 ` Myklebust, Trond
2012-03-01 15:34 ` Orion Poplawski
2012-03-01 19:28 ` J. Bruce Fields
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=4F4EB2FE.9040108@cora.nwra.com \
--to=orion@cora.nwra.com \
--cc=bfields@fieldses.org \
--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;
as well as URLs for NNTP newsgroup(s).