From: Trond Myklebust <trondmy@hammerspace.com>
To: "jiufei.xue@linux.alibaba.com" <jiufei.xue@linux.alibaba.com>,
"aglo@umich.edu" <aglo@umich.edu>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"joseph.qi@linux.alibaba.com" <joseph.qi@linux.alibaba.com>
Subject: Re: [bug report] task hang while testing xfstests generic/323
Date: Tue, 5 Mar 2019 14:45:46 +0000 [thread overview]
Message-ID: <b729878b38f32053890a592a91f0645f15caa96f.camel@hammerspace.com> (raw)
In-Reply-To: <1417d6c8-3602-d895-a036-44031a7c1e98@linux.alibaba.com>
On Tue, 2019-03-05 at 13:09 +0800, Jiufei Xue wrote:
> But now I have found something new that may helpful. When the problem
> happened, rpc_status was set to -121 which returned from
> nfs4_xdr_dec_open->decode_putfh. I think it is the cause that client
> can
> not update the stateid.
>
> kworker/u4:0-7 [001] .... 559.920542: nfs4_xdr_dec_open:
> status=0 openstateid=40289:0xd4bdfeb7
> kworker/1:0-2929 [001] .... 559.920550:
> nfs4_open_stateid_update: error=0 (OK) fileid=00:2b:12
> fhandle=0x1e4566cb stateid=40289:0xd4bdfeb7
> kworker/1:0-2929 [001] .... 559.920551: nfs4_open_release:
> cancel=1 rpc_status=0 rpc_done=1 openstateid=40289:0xd4bdfeb7
>
> nfsd-2741 [001] .... 559.920571: nfsd_compound_status:
> op=1/6 OP_SEQUENCE status=0
> nfsd-2741 [001] .... 559.920575: nfsd_compound_status:
> op=2/6 OP_PUTFH status=0
> nfsd-2741 [001] .... 559.920581:
> nfsd_inc_and_copy_stateid: client 5c7df867:90134041 stateid
> 00031b7d:00009d62 // 40290
> nfsd-2741 [001] .... 559.920584: nfsd_compound_status:
> op=3/6 OP_OPEN status=0
> nfsd-2741 [001] .... 559.920584: nfsd_compound_status:
> op=4/6 OP_GETFH status=0
> nfsd-2741 [001] .... 559.920585: nfsd_compound_status:
> op=5/6 OP_ACCESS status=0
> nfsd-2741 [001] .... 559.920588: nfsd_compound_status:
> op=6/6 OP_GETATTR status=0
> kworker/u4:0-7 [001] .... 559.920622: nfs4_xdr_dec_open:
> status=-121 openstateid=0:0x7bd5c66f // added for debug
> kworker/1:0-2929 [001] .... 559.920628: nfs4_open_release:
> cancel=1 rpc_status=-121 rpc_done=1 openstateid=0:0x7bd5c66f // added
> for debug
>
> And we got this error in dmesg:
> [ 559.834808] nfs: Server returned operation 53 but we issued a
> request for 22
> [ 559.835741] nfs: Server returned operation 53 but we issued a
> request for 22
>
> However, I don't kown why the client received two OP_SEQUENCE
> response.
> Any ideas?
>
No, that's quite weird... Were you able to catch this behaviour on
wireshark? It would be interesting to see if the server is actually
sending 2 SEQUENCE ops or if that is a corruption that occurs on the
client.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-03-05 14:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 10:10 [bug report] task hang while testing xfstests generic/323 Jiufei Xue
2019-02-28 22:26 ` Olga Kornievskaia
2019-02-28 23:56 ` Trond Myklebust
2019-03-01 5:19 ` Jiufei Xue
2019-03-01 5:08 ` Jiufei Xue
2019-03-01 8:49 ` Jiufei Xue
2019-03-01 13:08 ` Trond Myklebust
2019-03-02 16:34 ` Jiufei Xue
2019-03-04 15:20 ` Jiufei Xue
2019-03-04 15:50 ` Trond Myklebust
2019-03-05 5:09 ` Jiufei Xue
2019-03-05 14:45 ` Trond Myklebust [this message]
2019-03-06 9:59 ` Jiufei Xue
2019-03-06 16:09 ` bfields
2019-03-10 22:20 ` Olga Kornievskaia
2019-03-11 14:30 ` Trond Myklebust
2019-03-11 15:07 ` Olga Kornievskaia
2019-03-11 15:13 ` Olga Kornievskaia
2019-03-15 6:30 ` Jiufei Xue
2019-03-15 20:33 ` Olga Kornievskaia
2019-03-15 20:55 ` Trond Myklebust
2019-03-16 14:11 ` Jiufei Xue
2019-03-19 15:33 ` Olga Kornievskaia
2019-03-11 15:12 ` Trond Myklebust
2019-03-11 15:14 ` Olga Kornievskaia
2019-03-11 15:28 ` 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=b729878b38f32053890a592a91f0645f15caa96f.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=Anna.Schumaker@netapp.com \
--cc=aglo@umich.edu \
--cc=bfields@fieldses.org \
--cc=jiufei.xue@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.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