From: "zhoujie2011@fujitsu.com" <zhoujie2011@fujitsu.com>
To: "Mora, Jorge" <Jorge.Mora@netapp.com>, Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: nfstest_delegation test can not stop
Date: Fri, 17 Mar 2023 09:00:12 +0000 [thread overview]
Message-ID: <d09ec9bc-a49a-81da-d746-87ba9a137833@fujitsu.com> (raw)
In-Reply-To: <BYAPR06MB4296C2EA5A613C7178DE2381E1BF9@BYAPR06MB4296.namprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2734 bytes --]
hi,
> Can you provide a log file for the run?
run following command and test result is attached.
./nfstest_delegation --nfsversion=4 -e /nfsroot --server 192.168.122.110
--client 192.168.122.109 --trcdelay 10 -v all --createlog --keeptraces
--rexeclog recall22 >nfstest-delegationv4-log_recall22 2>&1
In server run "cat /etc/exports" output is following.
/nfsroot *(rw,insecure,no_subtree_check,no_root_squash,fsid=1)
best regards,
On 3/15/23 22:28, Mora, Jorge wrote:
> Hello,
>
> Can you provide a log file for the run?
>
> ./nfstest_delegation -s 192.168.68.86 -e /export -v all --createlog
> --keeptraces --rexeclog recall22
>
> --Jorge
>
> *From: *Jeff Layton <jlayton@kernel.org>
> *Date: *Wednesday, March 15, 2023 at 5:40 AM
> *To: *zhoujie2011@fujitsu.com <zhoujie2011@fujitsu.com>, Mora, Jorge
> <Jorge.Mora@netapp.com>
> *Cc: *linux-nfs <linux-nfs@vger.kernel.org>
> *Subject: *Re: nfstest_delegation test can not stop
>
> NetApp Security WARNING: This is an external email. Do not click links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
>
>
>
> On Tue, 2023-03-14 at 02:28 +0000, zhoujie2011@fujitsu.com wrote:
> > hi,
> >
> > I run following test command and stuck at recall12 recall14 recall20
> > recall22 recall40 recall42 recall48 recall50.
> >
> > ./nfstest_delegation --nfsversion=4 -e /nfsroot --server <server ip>
> > --client <client2 ip> --trcdelay 10
> > ./nfstest_delegation --nfsversion=4.1 -e /nfsroot --server <server ip>
> > --client <client2 ip> --trcdelay 10
> > ./nfstest_delegation --nfsversion=4.2 -e /nfsroot --server <server ip>
> > --client <client2 ip> --trcdelay 10
> >
> > recall12 recall14 recall20 recall22 recall40 recall42 recall48 recall50
> > tests write files after remove.
> > After comment out above testcases result is:
> > 646 tests (588 passed, 58 failed)
> > FAIL: WRITE delegation should be granted
> >
> > run ./nfstest_dio have following messages.
> > INFO: 16:19:51.455222 - WRITE delegations are not available -- skipping
> > tests expecting write delegations
> >
> > test OS: RHEL9.2 Nightly Build
> > Why do these testcases can not stop?
>
> Are you asking why these testcases don't pass? If you're testing against
> the kernel's NFS server then it's because it does not (yet) support
> write delegations.
> --
> Jeff Layton <jlayton@kernel.org>
>
--
------------------------------------------------
zhoujie
Dept 1
No. 6 Wenzhu Road,
Nanjing, 210012, China
TEL:+86+25-86630566-8508
FUJITSU INTERNAL:7998-8508
E-Mail:zhoujie2011@fujitsu.com
------------------------------------------------
[-- Attachment #2: nfstest-delegationv4-log_recall22 --]
[-- Type: text/plain, Size: 6622 bytes --]
OPTS: 17:06:47.835063 - ./nfstest_delegation --nfsversion=4 -e /nfsroot --server 192.168.122.110 --client 192.168.122.109 --trcdelay 10 -v all --createlog --keeptraces --rexeclog recall22
OPTS: 17:06:47.835117 - basename =
OPTS: 17:06:47.835158 - bugmsgs = None
OPTS: 17:06:47.835180 - client = 192.168.122.109
OPTS: 17:06:47.835201 - client-ipaddr = None
OPTS: 17:06:47.835222 - client-nfsvers = 4.0,4.1
OPTS: 17:06:47.835249 - createlog = True
OPTS: 17:06:47.835268 - createtraces = False
OPTS: 17:06:47.835286 - datadir =
OPTS: 17:06:47.835304 - export = /nfsroot
OPTS: 17:06:47.835322 - file =
OPTS: 17:06:47.835339 - filesize = 64k
OPTS: 17:06:47.835357 - interface = None
OPTS: 17:06:47.835383 - iodelay = 0.1
OPTS: 17:06:47.835403 - iptables = /usr/sbin/iptables
OPTS: 17:06:47.835420 - isatty = False
OPTS: 17:06:47.835444 - keeptraces = True
OPTS: 17:06:47.835460 - kill = /usr/bin/kill
OPTS: 17:06:47.835476 - lock-len = 4096
OPTS: 17:06:47.835492 - lock-offset = 0
OPTS: 17:06:47.835507 - lock-poffset = 8192
OPTS: 17:06:47.835522 - messages = /var/log/messages
OPTS: 17:06:47.835537 - mtopts = hard,rsize=4096,wsize=4096
OPTS: 17:06:47.835552 - mtpoint = /mnt/t
OPTS: 17:06:47.835566 - nconnect = 1
OPTS: 17:06:47.835581 - nfiles = 2
OPTS: 17:06:47.835596 - nfsdebug =
OPTS: 17:06:47.835611 - nfserrors = False
OPTS: 17:06:47.835625 - nfsstat = /usr/sbin/nfsstat
OPTS: 17:06:47.835640 - nfsstats = False
OPTS: 17:06:47.835655 - nfsversion = 4
OPTS: 17:06:47.835669 - nocleanup = False
OPTS: 17:06:47.835684 - nomount = False
OPTS: 17:06:47.835698 - notimestamps = False
OPTS: 17:06:47.835712 - notty = False
OPTS: 17:06:47.835727 - offset-delta = 4k
OPTS: 17:06:47.835742 - pktdisp = False
OPTS: 17:06:47.835756 - port = 2049
OPTS: 17:06:47.835771 - proto = tcp
OPTS: 17:06:47.835785 - rexeclog = True
OPTS: 17:06:47.835800 - rmtraces = False
OPTS: 17:06:47.835817 - rpcdebug =
OPTS: 17:06:47.835831 - rsize = 4k
OPTS: 17:06:47.835845 - runtest = recall22
OPTS: 17:06:47.835860 - sec = sys
OPTS: 17:06:47.835874 - server = 192.168.122.110
OPTS: 17:06:47.835889 - setup-delay = 4.0
OPTS: 17:06:47.835904 - sudo = /usr/bin/sudo
OPTS: 17:06:47.835918 - tag =
OPTS: 17:06:47.835933 - tbsize = 192k
OPTS: 17:06:47.835947 - tcpdump = /usr/sbin/tcpdump
OPTS: 17:06:47.835962 - tmpdir = /tmp
OPTS: 17:06:47.835976 - tracepoints =
OPTS: 17:06:47.835991 - trcdelay = 10.0
OPTS: 17:06:47.836005 - trcevents = /sys/kernel/debug/tracing/events
OPTS: 17:06:47.836020 - trcpipe = /sys/kernel/debug/tracing/trace_pipe
OPTS: 17:06:47.836035 - truncate = False
OPTS: 17:06:47.836050 - tverbose = 1
OPTS: 17:06:47.836064 - verbose = all
OPTS: 17:06:47.836078 - warnings = False
OPTS: 17:06:47.836093 - wsize = 4k
OPTS: 17:06:47.836108 - xunit-report = False
OPTS: 17:06:47.836123 - xunit-report-file = None
INFO: 17:06:47.836160 - SYSTEM: Linux nfstest-client1 5.14.0-244.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jan 25 15:35:31 EST 2023 x86_64
DBG5: 17:06:47.836264 - Get routing info: /usr/sbin/ip route get 192.168.122.110
DBG2: 17:06:47.867201 - Start remote procedure server at 192.168.122.109
DBG7: 17:06:48.888674 - SETUP starts
DBG5: 17:06:48.888932 - Sync all buffers to disk
DBG2: 17:06:48.913056 - Unmount volume: /usr/bin/sudo umount -f /mnt/t
DBG2: 17:06:48.961319 - Mount volume: /usr/bin/sudo mount -o vers=4,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.122.110:/nfsroot /mnt/t
DBG5: 17:06:49.337525 - Get the actual NFS version of mount point: findmnt /mnt/t
DBG6: 17:06:49.341831 - NFS version of mount point: 4.2
DBG2: 17:06:49.341964 - Creating file [/mnt/t/nfstest_delegation_20230317_170647_f_001] 65536@0
DBG2: 17:06:49.390516 - Creating file [/mnt/t/nfstest_delegation_20230317_170647_f_002] 65536@0
DBG2: 17:06:49.412867 - Creating file [/mnt/t/nfstest_delegation_20230317_170647_f_003] 65536@0
DBG5: 17:06:49.436684 - Sync all buffers to disk
DBG2: 17:06:49.455950 - Unmount volume: /usr/bin/sudo umount -f /mnt/t
DBG7: 17:06:49.521806 - SETUP done
TIME: 5.697167s
*** Recall WRITE delegation with RENAME (DST) with file lock
TEST: Running test 'recall22'
DBG5: 17:06:53.526464 - Sync all buffers to disk
DBG2: 17:06:53.541589 - Unmount volume: /usr/bin/sudo umount -f /mnt/t
DBG4: 17:06:53.555982 - Check if mount point directory exists: ssh -t -t 192.168.122.109 "test -e '/mnt/t'"
DBG4: 17:06:53.775447 - Check if mount point is a directory: ssh -t -t 192.168.122.109 "test -d '/mnt/t'"
DBG5: 17:06:53.988721 - Sync all buffers to disk
DBG2: 17:06:54.004577 - Unmount volume: ssh -t -t 192.168.122.109 "/usr/bin/sudo umount -f /mnt/t"
DBG2: 17:06:54.254966 - Trace start: /usr/bin/sudo /usr/sbin/tcpdump -i enp1s0 -n -B 196608 -s 0 -w /tmp/nfstest_delegation_20230317_170647_001.cap host 192.168.122.108 or 192.168.122.109
DBG2: 17:06:55.373898 - Mount volume: /usr/bin/sudo mount -o vers=4,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.122.110:/nfsroot /mnt/t
DBG5: 17:06:55.434114 - Get the actual NFS version of mount point: findmnt /mnt/t
DBG6: 17:06:55.438054 - NFS version of mount point: 4.2
DBG2: 17:06:55.438258 - Mount volume: ssh -t -t 192.168.122.109 "/usr/bin/sudo mount -o vers=4.0,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.122.110:/nfsroot /mnt/t"
DBG5: 17:06:55.987738 - Get the actual NFS version of mount point: ssh -t -t 192.168.122.109 "findmnt /mnt/t"
DBG6: 17:06:56.207984 - NFS version of mount point: 4.0
DBG4: 17:06:56.208168 - Open /mnt/t/nfstest_delegation_20230317_170647_f_001 so open owner sticks around
DBG2: 17:06:56.209105 - Open file for WRITE [/mnt/t/nfstest_delegation_20230317_170647_f_002]
PASS: Open file for WRITE should succeed
DBG3: 17:06:56.209407 - Lock /mnt/t/nfstest_delegation_20230317_170647_f_002 (F_SETLK, F_WRLCK) start=0 len=4096
PASS: Lock file with F_WRLCK should succeed
DBG3: 17:06:56.209769 - Write file on client holding delegation [/mnt/t/nfstest_delegation_20230317_170647_f_002]
PASS: Write file on client holding delegation should succeed
DBG2: 17:06:56.310349 - Rename into the file (DST) from another client to recall delegation [nfstest_delegation_20230317_170647_f_003 -> nfstest_delegation_20230317_170647_f_002]
PASS: Rename into the file (DST) from another client should succeed
next prev parent reply other threads:[~2023-03-17 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 2:28 nfstest_delegation test can not stop zhoujie2011
2023-03-15 11:40 ` Jeff Layton
[not found] ` <BYAPR06MB4296C2EA5A613C7178DE2381E1BF9@BYAPR06MB4296.namprd06.prod.outlook.com>
2023-03-17 9:00 ` zhoujie2011 [this message]
2023-03-17 18:14 ` Mora, Jorge
2023-03-29 0:15 ` zhoujie2011
2023-03-29 18:30 ` Mora, Jorge
[not found] ` <c34c8f71-d048-6ed5-9268-7623ce083874@fujitsu.com>
2023-03-30 16:57 ` Mora, Jorge
2023-03-31 2:15 ` zhoujie2011
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=d09ec9bc-a49a-81da-d746-87ba9a137833@fujitsu.com \
--to=zhoujie2011@fujitsu.com \
--cc=Jorge.Mora@netapp.com \
--cc=jlayton@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.