From: xuhuan <xuhuan.fnst@cn.fujitsu.com>
To: <mora@netapp.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: nfstest_cache :directory listing changed before acdirmin
Date: Fri, 27 Jul 2018 10:47:57 +0800 [thread overview]
Message-ID: <3c1e663c-7391-92f5-ccfe-e833a2fbc4af@cn.fujitsu.com> (raw)
Hi Jorge.
I tested nfstest_cache on the lastest kernel,there were some
FAIL in the result.(It failed with all versions of nfs)
Is this the cache's bug? Or i missed some arguments ?
./nfstest_cache --nfsversion=4 -e /nfsroot --server 192.168.227.10 --client 192.168.227.12 >cache4.log
(version 3,4.1,4.2 had the same result).
*** Verify consistency of data caching with NFSv4 on a directory acdirmin = 10
TEST: Running test 'acdirmin_data'
FAIL: Directory listing should have not changed at t=0
FAIL: Directory listing should have not changed just before acdirmin
PASS: Directory listing should have changed just after acdirmin
TIME: 10.308059s
*** Verify consistency of data caching with NFSv4 on a directory acdirmin = 10 acdirmax = 20
TEST: Running test 'acdirmax_data'
FAIL: Directory listing should have not changed at t=0
FAIL: Directory listing should have not changed just before acdirmax
PASS: Directory listing should have changed just after acdirmax
FAIL: Directory listing should have not changed just before acdirmin
PASS: Directory listing should have changed just after acdirmin
TIME: 1m0.623938s
*** Verify consistency of data caching with NFSv4 on a directory actimeo = 10
FAIL: Directory listing should have not changed at t=0
FAIL: Directory listing should have not changed just before actimeo
PASS: Directory listing should have changed just after actimeo
TIME: 11.027872s
Huan Xu
reply other threads:[~2018-07-27 4:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3c1e663c-7391-92f5-ccfe-e833a2fbc4af@cn.fujitsu.com \
--to=xuhuan.fnst@cn.fujitsu.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mora@netapp.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).