linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "zhangxiaoxu (A)" <zhangxiaoxu5@huawei.com>
To: <anna.schumaker@netapp.com>, <trond.myklebust@hammerspace.com>,
	<linux-nfs@vger.kernel.org>, Hou Tao <houtao1@huawei.com>,
	<miaoxie@huawei.com>, <zhaohongjiang@huawei.com>
Subject: xfstest generic/089 failed on NFSv2
Date: Mon, 10 Dec 2018 01:21:43 +0800	[thread overview]
Message-ID: <c0072355-7300-85d9-6333-7c5e0009fc75@huawei.com> (raw)

Hi All,
I run the xfstest on nfsv2, the case generic/089 will failed with timeout sometimes.

The top of the stack always on 'nlmclnt_block' function.
And the 'nlmclnt_lock' function will retry every 30s.
So, the test case is killed by the timer and failed.

We open the nlm_debug, found that:
The client send unlock message to server, and the server handle it correct.
But no 'NLM_LCK_GRANTED' message send to the client.

The configuration about the xfstest and nfs server:

The local.config of the xfstest is:
export FSTYP=nfs
export TEST_DEV=192.168.240.61:/export/ext4/test
export TEST_DIR=/nfs/test
export SCRATCH_DEV=192.168.240.61:/export/ext4/scratch
export SCRATCH_MNT=/nfs/scratch
export NFS_MOUNT_OPTIONS="-o acl,rw,relatime,vers=2,lock"

The nfs server just export the share directory.

I don't know why this case is skip from https://wiki.linux-nfs.org/wiki/index.php/Xfstests
If any problem about the fcntl(F_SETLKW) wait so long time?






             reply	other threads:[~2018-12-09 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-09 17:21 zhangxiaoxu (A) [this message]
2019-01-10 20:11 ` xfstest generic/089 failed on NFSv2 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=c0072355-7300-85d9-6333-7c5e0009fc75@huawei.com \
    --to=zhangxiaoxu5@huawei.com \
    --cc=anna.schumaker@netapp.com \
    --cc=houtao1@huawei.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=trond.myklebust@hammerspace.com \
    --cc=zhaohongjiang@huawei.com \
    /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).