Linux-NFS Archive on lore.kernel.org
 help / Atom feed
* xfstest generic/089 failed on NFSv2
@ 2018-12-09 17:21 zhangxiaoxu (A)
  2019-01-10 20:11 ` bfields
  0 siblings, 1 reply; 2+ messages in thread
From: zhangxiaoxu (A) @ 2018-12-09 17:21 UTC (permalink / raw)
  To: anna.schumaker, trond.myklebust, linux-nfs, Hou Tao, miaoxie,
	zhaohongjiang

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?






^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: xfstest generic/089 failed on NFSv2
  2018-12-09 17:21 xfstest generic/089 failed on NFSv2 zhangxiaoxu (A)
@ 2019-01-10 20:11 ` bfields
  0 siblings, 0 replies; 2+ messages in thread
From: bfields @ 2019-01-10 20:11 UTC (permalink / raw)
  To: zhangxiaoxu (A)
  Cc: anna.schumaker, trond.myklebust, linux-nfs, Hou Tao, miaoxie,
	zhaohongjiang

On Mon, Dec 10, 2018 at 01:21:43AM +0800, zhangxiaoxu (A) wrote:
> 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?

I've seen intermittent generic/089 failures as well and haven't had the
time to track them down.  From your description it does sound like a
potentialy server bug.

--b.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-09 17:21 xfstest generic/089 failed on NFSv2 zhangxiaoxu (A)
2019-01-10 20:11 ` bfields

Linux-NFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nfs/0 linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ https://lore.kernel.org/linux-nfs \
		linux-nfs@vger.kernel.org linux-nfs@archiver.kernel.org
	public-inbox-index linux-nfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-nfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox