* nfstest_delegation test can not stop @ 2023-03-14 2:28 zhoujie2011 2023-03-15 11:40 ` Jeff Layton 0 siblings, 1 reply; 8+ messages in thread From: zhoujie2011 @ 2023-03-14 2:28 UTC (permalink / raw) To: mora; +Cc: linux-nfs 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? best regards, -- ------------------------------------------------ zhoujie Dept 1 No. 6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566-8508 FUJITSU INTERNAL：7998-8508 E-Mail：zhoujie2011@fujitsu.com ------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfstest_delegation test can not stop 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> 0 siblings, 1 reply; 8+ messages in thread From: Jeff Layton @ 2023-03-15 11:40 UTC (permalink / raw) To: zhoujie2011, mora; +Cc: linux-nfs 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> ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <BYAPR06MB4296C2EA5A613C7178DE2381E1BF9@BYAPR06MB4296.namprd06.prod.outlook.com>]
* Re: nfstest_delegation test can not stop [not found] ` <BYAPR06MB4296C2EA5A613C7178DE2381E1BF9@BYAPR06MB4296.namprd06.prod.outlook.com> @ 2023-03-17 9:00 ` zhoujie2011 2023-03-17 18:14 ` Mora, Jorge 2023-03-29 0:15 ` zhoujie2011 0 siblings, 2 replies; 8+ messages in thread From: zhoujie2011 @ 2023-03-17 9:00 UTC (permalink / raw) To: Mora, Jorge, Jeff Layton; +Cc: linux-nfs [-- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfstest_delegation test can not stop 2023-03-17 9:00 ` zhoujie2011 @ 2023-03-17 18:14 ` Mora, Jorge 2023-03-29 0:15 ` zhoujie2011 1 sibling, 0 replies; 8+ messages in thread From: Mora, Jorge @ 2023-03-17 18:14 UTC (permalink / raw) To: zhoujie2011, Jeff Layton; +Cc: linux-nfs Hello, Could you send me all the files created by the run, both log files and the packet trace (/tmp/nfstest_delegation_20230317_170647*)? --Jorge From: zhoujie2011@fujitsu.com <zhoujie2011@fujitsu.com> Date: Friday, March 17, 2023 at 3:00 AM 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 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. 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 ------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfstest_delegation test can not stop 2023-03-17 9:00 ` zhoujie2011 2023-03-17 18:14 ` Mora, Jorge @ 2023-03-29 0:15 ` zhoujie2011 2023-03-29 18:30 ` Mora, Jorge 1 sibling, 1 reply; 8+ messages in thread From: zhoujie2011 @ 2023-03-29 0:15 UTC (permalink / raw) To: Mora, Jorge, Jeff Layton; +Cc: linux-nfs ping On 3/17/23 16:58, zhoujie2011 wrote: > 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 ------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfstest_delegation test can not stop 2023-03-29 0:15 ` zhoujie2011 @ 2023-03-29 18:30 ` Mora, Jorge [not found] ` <c34c8f71-d048-6ed5-9268-7623ce083874@fujitsu.com> 0 siblings, 1 reply; 8+ messages in thread From: Mora, Jorge @ 2023-03-29 18:30 UTC (permalink / raw) To: zhoujie2011, Jeff Layton; +Cc: linux-nfs Hello, I am still waiting for all the files created for the run, not just the output to the screen: /tmp/nfstest_delegation_20230317_170647* --Jorge ________________________________________ From: zhoujie2011@fujitsu.com <zhoujie2011@fujitsu.com> Sent: Tuesday, March 28, 2023 6:15 PM To: Mora, Jorge; Jeff Layton Cc: linux-nfs 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. ping On 3/17/23 16:58, zhoujie2011 wrote: > 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 ------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <c34c8f71-d048-6ed5-9268-7623ce083874@fujitsu.com>]
* Re: nfstest_delegation test can not stop [not found] ` <c34c8f71-d048-6ed5-9268-7623ce083874@fujitsu.com> @ 2023-03-30 16:57 ` Mora, Jorge 2023-03-31 2:15 ` zhoujie2011 0 siblings, 1 reply; 8+ messages in thread From: Mora, Jorge @ 2023-03-30 16:57 UTC (permalink / raw) To: zhoujie2011, Jeff Layton; +Cc: linux-nfs Hello, First of all, the --client option can be used successfully when the system in which you are running the test is able to capture the traffic for both clients, e.g., when you are running VMware and both clients are VMs. If you are using real clients, tcpdump will only capture traffic for the local system. ./nfstest_delegation -h Test options: --runtest=RUNTEST Comma separated list of tests to run, if list starts with a '^' then all tests are run except the ones listed [default: 'all'] --client=CLIENT Remote NFS client and options used for recall delegation tests. Clients are separated by a ',' and each client definition is a list of arguments separated by a ':' given in the following order if positional arguments is used (see examples): clientname:server:export:nfsversion:port:proto:sec:mtpoint [default: 'nfsversion=3:proto=tcp:port=2049'] --client-nfsvers=CLIENT_NFSVERS Comma separated list of valid NFS versions to use in the --client option. An NFS version from this list, which is different than that given by --nfsversion, is selected and included in the --client option [default: 4.0,4.1] The second client is a combination of --client and --client-nfsvers and the default for --client is 'nfsversion=3:proto=tcp:port=2049'. This means that the mount for the second 'client' is on the main client with the following nfs mount options: 'nfsversion=4.0:proto=tcp:port=2049' or 'nfsversion=4.1:proto=tcp:port=2049' depending on the value for option --nfsversion. In you case, --nfsversion=4 (if you mean 4.0) the mount options for the second client should be 'nfsversion=4.1...'. This way main mount is 4.0 (holding delegation) and the second mount is 4.1 (recall delegation) on the same system so the network traffic could be fully captured. Of course, if you specify --nfsversion=4, the client will mount either 4.2, 4.1 or 4.0 (in your logs: NFS version of mount point: 4.2). You need to explicitly specify the NFS version as 4.0, 4.1 or 4.2. The reason why the test is hanging is because the server is sending NFS4ERR_DELAY to COMMIT: 133 2023-03-30 07:46:22.533580 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0xfd10f3db SEQUENCE;PUTFH;OPEN;GETFH;ACCESS;GETATTR stid:1,0xe37587e3 rd_deleg_stid:1,0xf1c0280d FH:0x634cb2d9 135 2023-03-30 07:46:22.533973 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0xfe10f3db SEQUENCE;PUTFH;OPEN;GETFH;ACCESS;GETATTR stid:1,0x497c4f68 FH:0x62ab8136 136 2023-03-30 07:46:22.534191 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0xff10f3db SEQUENCE;PUTFH;LOCK FH:0x62ab8136 WRITE_LT off:0 len:4096 open(stid:1,0x497c4f68, seqid:0) seqid:0 137 2023-03-30 07:46:22.534304 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0xff10f3db SEQUENCE;PUTFH;LOCK stid:1,0xd4ab77d1 146 2023-03-30 07:46:22.659988 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x0011f3db SEQUENCE;PUTFH;WRITE;GETATTR FH:0x62ab8136 stid:0,0xd4ab77d1 off:0 len:4096 UNSTABLE4 147 2023-03-30 07:46:22.660009 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x0111f3db SEQUENCE;PUTFH;WRITE;GETATTR FH:0x62ab8136 stid:0,0xd4ab77d1 off:4096 len:4096 UNSTABLE4 ... 191 2023-03-30 07:46:22.660695 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1011f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 192 2023-03-30 07:46:22.672090 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1011f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY 194 2023-03-30 07:46:22.778177 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1111f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 195 2023-03-30 07:46:22.779064 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1111f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY 197 2023-03-30 07:46:22.882100 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1211f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 198 2023-03-30 07:46:22.882566 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1211f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY 200 2023-03-30 07:46:22.986157 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1311f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 201 2023-03-30 07:46:22.986931 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1311f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY As Jeff mentioned earlier, Linux server does not grant write delegations. I don't know what server are you using but the OPEN clearly shows it did not grant a write delegation so this test should fail. Here is a sample run against a RHEL 8.6 server: ./nfstest_delegation -s 192.168.68.86 -e /export --nfsversion 4.0 -v all --createlog --keeptraces --rexeclog --tracepoints nfs,nfs4 recall22 *** Recall WRITE delegation with RENAME (DST) with file lock TEST: Running test 'recall22' DBG5: 10:48:51.644258 - Sync all buffers to disk DBG2: 10:48:51.651724 - Unmount volume: /usr/bin/sudo umount -f /mnt/t DBG5: 10:48:51.684054 - Sync all buffers to disk DBG2: 10:48:51.685482 - Unmount volume: /usr/bin/sudo umount -f /mnt/t_01 DBG2: 10:48:51.719133 - Enable trace points: /usr/bin/sudo sh -c "echo 1 > /sys/kernel/debug/tracing/events/nfs/enable" DBG2: 10:48:51.761795 - Enable trace points: /usr/bin/sudo sh -c "echo 1 > /sys/kernel/debug/tracing/events/nfs4/enable" DBG2: 10:48:51.805703 - Capturing trace points: /usr/bin/sudo sh -c "cat /sys/kernel/debug/tracing/trace_pipe > /tmp/nfstest_delegation_20230330_104846_001.out" DBG2: 10:48:51.808284 - Trace start: /usr/bin/sudo /usr/sbin/tcpdump -i ens160 -n -B 196608 -s 0 -w /tmp/nfstest_delegation_20230330_104846_001.cap host 192.168.68.87 DBG2: 10:48:52.904843 - Mount volume: /usr/bin/sudo mount -o vers=4.0,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.68.86:/export /mnt/t DBG5: 10:48:53.045345 - Get the actual NFS version of mount point: findmnt /mnt/t DBG6: 10:48:53.053811 - NFS version of mount point: 4.0 DBG2: 10:48:53.054069 - Mount volume: /usr/bin/sudo mount -o vers=4.1,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.68.86:/export /mnt/t_01 DBG5: 10:48:53.194449 - Get the actual NFS version of mount point: findmnt /mnt/t_01 DBG6: 10:48:53.202076 - NFS version of mount point: 4.1 DBG4: 10:48:53.202297 - Open /mnt/t/nfstest_delegation_20230330_104846_f_001 so open owner sticks around DBG2: 10:48:53.207257 - Open file for WRITE [/mnt/t/nfstest_delegation_20230330_104846_f_002] PASS: Open file for WRITE should succeed DBG3: 10:48:53.208168 - Lock /mnt/t/nfstest_delegation_20230330_104846_f_002 (F_SETLK, F_WRLCK) start=0 len=4096 PASS: Lock file with F_WRLCK should succeed DBG3: 10:48:53.209489 - Write file on client holding delegation [/mnt/t/nfstest_delegation_20230330_104846_f_002] PASS: Write file on client holding delegation should succeed DBG2: 10:48:53.310548 - Rename into the file (DST) from another client to recall delegation [nfstest_delegation_20230330_104846_f_003 -> nfstest_delegation_20230330_104846_f_002] PASS: Rename into the file (DST) from another client should succeed DBG3: 10:48:53.320851 - Write file after conflicting operation [/mnt/t/nfstest_delegation_20230330_104846_f_002] PASS: Write file after conflicting operation may succeed DBG4: 10:48:53.447733 - Close /mnt/t/nfstest_delegation_20230330_104846_f_002 DBG5: 10:48:53.450185 - Sync all buffers to disk DBG2: 10:48:53.457125 - Unmount volume: /usr/bin/sudo umount -f /mnt/t DBG5: 10:48:53.515896 - Sync all buffers to disk DBG2: 10:48:53.520120 - Unmount volume: /usr/bin/sudo umount -f /mnt/t_01 DBG5: 10:48:55.580838 - Get all processes: ps -ef DBG5: 10:48:55.621321 - Stopping packet trace capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348494 DBG5: 10:48:55.656126 - Stopping packet trace capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348489 DBG2: 10:48:55.788319 - Disable trace points: /usr/bin/sudo sh -c "echo 0 > /sys/kernel/debug/tracing/events/nfs/enable" DBG2: 10:48:55.829243 - Disable trace points: /usr/bin/sudo sh -c "echo 0 > /sys/kernel/debug/tracing/events/nfs4/enable" DBG5: 10:48:55.875925 - Get all processes: ps -ef DBG2: 10:48:55.908161 - Stopping trace points capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348493 DBG2: 10:48:55.939992 - Stopping trace points capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348492 DBG2: 10:48:55.972241 - Stopping trace points capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348488 DBG1: 10:48:56.104525 - trace_open [/tmp/nfstest_delegation_20230330_104846_001.cap] PASS: OPEN should be sent PASS: OPEN should be sent with CLAIM_NULL PASS: OPEN should be sent with the name of the file to be opened PASS: OPEN should be sent with the filehandle of the directory FAIL: WRITE delegation should be granted TIME: 4.570563s I also added option --tracepoints to collect all nfs and nfs4 tracepoints. These are the files that are created: ll /tmp/nfstest_delegation_20230330_104846* -rw-r--r--. 1 tcpdump tcpdump 106776 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846_001.cap (packet trace) -rw-r--r--. 1 root root 64218 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846_001.out (tracepoints) -rw-rw-r--. 1 mora mora 317 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846_01.log (second 'client' process log file) -rw-rw-r--. 1 mora mora 9779 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846.log (main logfile) --Jorge ________________________________________ From: zhoujie2011@fujitsu.com <zhoujie2011@fujitsu.com> Sent: Wednesday, March 29, 2023 7:42 PM To: Mora, Jorge; Jeff Layton Cc: linux-nfs 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. hi, > I am still waiting for all the files created for the run, not just the output to the screen: > > /tmp/nfstest_delegation_20230317_170647* The log file is attached. best regards, > > ping > > On 3/17/23 16:58, zhoujie2011 wrote: >> 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 > ------------------------------------------------ -- ------------------------------------------------ zhoujie Dept 1 No. 6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566-8508 FUJITSU INTERNAL：7998-8508 E-Mail：zhoujie2011@fujitsu.com ------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfstest_delegation test can not stop 2023-03-30 16:57 ` Mora, Jorge @ 2023-03-31 2:15 ` zhoujie2011 0 siblings, 0 replies; 8+ messages in thread From: zhoujie2011 @ 2023-03-31 2:15 UTC (permalink / raw) To: Mora, Jorge, Jeff Layton; +Cc: linux-nfs hi, Thanks for reply. > Of course, if you specify --nfsversion=4, the client will mount either 4.2, 4.1 or 4.0 (in your logs: NFS version of mount point: 4.2). You need to explicitly specify the NFS version as 4.0, 4.1 or 4.2. I understand. > Here is a sample run against a RHEL 8.6 server: > ./nfstest_delegation -s 192.168.68.86 -e /export --nfsversion 4.0 -v all --createlog --keeptraces --rexeclog --tracepoints nfs,nfs4 recall22 I run test OK in RHEL 8.6 server. best regards, On 3/31/23 00:57, Mora, Jorge wrote: > Hello, > > First of all, the --client option can be used successfully when the system in which you are running the test is able to capture the traffic for both clients, e.g., when you are running VMware and both clients are VMs. If you are using real clients, tcpdump will only capture traffic for the local system. > > ./nfstest_delegation -h > Test options: > --runtest=RUNTEST > Comma separated list of tests to run, if list starts with a '^' then > all tests are run except the ones listed [default: 'all'] > --client=CLIENT > Remote NFS client and options used for recall delegation tests. > Clients are separated by a ',' and each client definition is a list > of arguments separated by a ':' given in the following order if > positional arguments is used (see examples): > clientname:server:export:nfsversion:port:proto:sec:mtpoint [default: > 'nfsversion=3:proto=tcp:port=2049'] > --client-nfsvers=CLIENT_NFSVERS > Comma separated list of valid NFS versions to use in the --client > option. An NFS version from this list, which is different than that > given by --nfsversion, is selected and included in the --client > option [default: 4.0,4.1] > > The second client is a combination of --client and --client-nfsvers and the default for --client is 'nfsversion=3:proto=tcp:port=2049'. This means that the mount for the second 'client' is on the main client with the following nfs mount options: 'nfsversion=4.0:proto=tcp:port=2049' or 'nfsversion=4.1:proto=tcp:port=2049' depending on the value for option --nfsversion. In you case, --nfsversion=4 (if you mean 4.0) the mount options for the second client should be 'nfsversion=4.1...'. This way main mount is 4.0 (holding delegation) and the second mount is 4.1 (recall delegation) on the same system so the network traffic could be fully captured. > > Of course, if you specify --nfsversion=4, the client will mount either 4.2, 4.1 or 4.0 (in your logs: NFS version of mount point: 4.2). You need to explicitly specify the NFS version as 4.0, 4.1 or 4.2. > > The reason why the test is hanging is because the server is sending NFS4ERR_DELAY to COMMIT: > 133 2023-03-30 07:46:22.533580 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0xfd10f3db SEQUENCE;PUTFH;OPEN;GETFH;ACCESS;GETATTR stid:1,0xe37587e3 rd_deleg_stid:1,0xf1c0280d FH:0x634cb2d9 > 135 2023-03-30 07:46:22.533973 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0xfe10f3db SEQUENCE;PUTFH;OPEN;GETFH;ACCESS;GETATTR stid:1,0x497c4f68 FH:0x62ab8136 > 136 2023-03-30 07:46:22.534191 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0xff10f3db SEQUENCE;PUTFH;LOCK FH:0x62ab8136 WRITE_LT off:0 len:4096 open(stid:1,0x497c4f68, seqid:0) seqid:0 > 137 2023-03-30 07:46:22.534304 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0xff10f3db SEQUENCE;PUTFH;LOCK stid:1,0xd4ab77d1 > 146 2023-03-30 07:46:22.659988 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x0011f3db SEQUENCE;PUTFH;WRITE;GETATTR FH:0x62ab8136 stid:0,0xd4ab77d1 off:0 len:4096 UNSTABLE4 > 147 2023-03-30 07:46:22.660009 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x0111f3db SEQUENCE;PUTFH;WRITE;GETATTR FH:0x62ab8136 stid:0,0xd4ab77d1 off:4096 len:4096 UNSTABLE4 > ... > 191 2023-03-30 07:46:22.660695 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1011f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 > 192 2023-03-30 07:46:22.672090 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1011f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY > 194 2023-03-30 07:46:22.778177 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1111f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 > 195 2023-03-30 07:46:22.779064 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1111f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY > 197 2023-03-30 07:46:22.882100 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1211f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 > 198 2023-03-30 07:46:22.882566 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1211f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY > 200 2023-03-30 07:46:22.986157 192.168.122.108 -> 192.168.122.110 NFS v4.2 call xid:0x1311f3db SEQUENCE;PUTFH;COMMIT FH:0x62ab8136 off:0 len:0 > 201 2023-03-30 07:46:22.986931 192.168.122.110 -> 192.168.122.108 NFS v4.2 reply xid:0x1311f3db SEQUENCE;PUTFH;COMMIT NFS4ERR_DELAY > > As Jeff mentioned earlier, Linux server does not grant write delegations. I don't know what server are you using but the OPEN clearly shows it did not grant a write delegation so this test should fail. > > Here is a sample run against a RHEL 8.6 server: > ./nfstest_delegation -s 192.168.68.86 -e /export --nfsversion 4.0 -v all --createlog --keeptraces --rexeclog --tracepoints nfs,nfs4 recall22 > > *** Recall WRITE delegation with RENAME (DST) with file lock > TEST: Running test 'recall22' > DBG5: 10:48:51.644258 - Sync all buffers to disk > DBG2: 10:48:51.651724 - Unmount volume: /usr/bin/sudo umount -f /mnt/t > DBG5: 10:48:51.684054 - Sync all buffers to disk > DBG2: 10:48:51.685482 - Unmount volume: /usr/bin/sudo umount -f /mnt/t_01 > DBG2: 10:48:51.719133 - Enable trace points: /usr/bin/sudo sh -c "echo 1 > /sys/kernel/debug/tracing/events/nfs/enable" > DBG2: 10:48:51.761795 - Enable trace points: /usr/bin/sudo sh -c "echo 1 > /sys/kernel/debug/tracing/events/nfs4/enable" > DBG2: 10:48:51.805703 - Capturing trace points: /usr/bin/sudo sh -c "cat /sys/kernel/debug/tracing/trace_pipe > /tmp/nfstest_delegation_20230330_104846_001.out" > DBG2: 10:48:51.808284 - Trace start: /usr/bin/sudo /usr/sbin/tcpdump -i ens160 -n -B 196608 -s 0 -w /tmp/nfstest_delegation_20230330_104846_001.cap host 192.168.68.87 > DBG2: 10:48:52.904843 - Mount volume: /usr/bin/sudo mount -o vers=4.0,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.68.86:/export /mnt/t > DBG5: 10:48:53.045345 - Get the actual NFS version of mount point: findmnt /mnt/t > DBG6: 10:48:53.053811 - NFS version of mount point: 4.0 > DBG2: 10:48:53.054069 - Mount volume: /usr/bin/sudo mount -o vers=4.1,proto=tcp,sec=sys,hard,rsize=4096,wsize=4096 192.168.68.86:/export /mnt/t_01 > DBG5: 10:48:53.194449 - Get the actual NFS version of mount point: findmnt /mnt/t_01 > DBG6: 10:48:53.202076 - NFS version of mount point: 4.1 > DBG4: 10:48:53.202297 - Open /mnt/t/nfstest_delegation_20230330_104846_f_001 so open owner sticks around > DBG2: 10:48:53.207257 - Open file for WRITE [/mnt/t/nfstest_delegation_20230330_104846_f_002] > PASS: Open file for WRITE should succeed > DBG3: 10:48:53.208168 - Lock /mnt/t/nfstest_delegation_20230330_104846_f_002 (F_SETLK, F_WRLCK) start=0 len=4096 > PASS: Lock file with F_WRLCK should succeed > DBG3: 10:48:53.209489 - Write file on client holding delegation [/mnt/t/nfstest_delegation_20230330_104846_f_002] > PASS: Write file on client holding delegation should succeed > DBG2: 10:48:53.310548 - Rename into the file (DST) from another client to recall delegation [nfstest_delegation_20230330_104846_f_003 -> nfstest_delegation_20230330_104846_f_002] > PASS: Rename into the file (DST) from another client should succeed > DBG3: 10:48:53.320851 - Write file after conflicting operation [/mnt/t/nfstest_delegation_20230330_104846_f_002] > PASS: Write file after conflicting operation may succeed > DBG4: 10:48:53.447733 - Close /mnt/t/nfstest_delegation_20230330_104846_f_002 > DBG5: 10:48:53.450185 - Sync all buffers to disk > DBG2: 10:48:53.457125 - Unmount volume: /usr/bin/sudo umount -f /mnt/t > DBG5: 10:48:53.515896 - Sync all buffers to disk > DBG2: 10:48:53.520120 - Unmount volume: /usr/bin/sudo umount -f /mnt/t_01 > DBG5: 10:48:55.580838 - Get all processes: ps -ef > DBG5: 10:48:55.621321 - Stopping packet trace capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348494 > DBG5: 10:48:55.656126 - Stopping packet trace capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348489 > DBG2: 10:48:55.788319 - Disable trace points: /usr/bin/sudo sh -c "echo 0 > /sys/kernel/debug/tracing/events/nfs/enable" > DBG2: 10:48:55.829243 - Disable trace points: /usr/bin/sudo sh -c "echo 0 > /sys/kernel/debug/tracing/events/nfs4/enable" > DBG5: 10:48:55.875925 - Get all processes: ps -ef > DBG2: 10:48:55.908161 - Stopping trace points capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348493 > DBG2: 10:48:55.939992 - Stopping trace points capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348492 > DBG2: 10:48:55.972241 - Stopping trace points capture: /usr/bin/sudo /usr/bin/kill -SIGINT 348488 > DBG1: 10:48:56.104525 - trace_open [/tmp/nfstest_delegation_20230330_104846_001.cap] > PASS: OPEN should be sent > PASS: OPEN should be sent with CLAIM_NULL > PASS: OPEN should be sent with the name of the file to be opened > PASS: OPEN should be sent with the filehandle of the directory > FAIL: WRITE delegation should be granted > TIME: 4.570563s > > I also added option --tracepoints to collect all nfs and nfs4 tracepoints. These are the files that are created: > ll /tmp/nfstest_delegation_20230330_104846* > -rw-r--r--. 1 tcpdump tcpdump 106776 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846_001.cap (packet trace) > -rw-r--r--. 1 root root 64218 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846_001.out (tracepoints) > -rw-rw-r--. 1 mora mora 317 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846_01.log (second 'client' process log file) > -rw-rw-r--. 1 mora mora 9779 Mar 30 10:48 /tmp/nfstest_delegation_20230330_104846.log (main logfile) > > > --Jorge > > ________________________________________ > From: zhoujie2011@fujitsu.com <zhoujie2011@fujitsu.com> > Sent: Wednesday, March 29, 2023 7:42 PM > To: Mora, Jorge; Jeff Layton > Cc: linux-nfs > 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. > > > > > hi, > >> I am still waiting for all the files created for the run, not just the output to the screen: >> >> /tmp/nfstest_delegation_20230317_170647* > The log file is attached. > > best regards, > >> >> ping >> >> On 3/17/23 16:58, zhoujie2011 wrote: >>> 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 >> ------------------------------------------------ > > -- > ------------------------------------------------ > zhoujie > Dept 1 > No. 6 Wenzhu Road, > Nanjing, 210012, China > TEL：+86+25-86630566-8508 > FUJITSU INTERNAL：7998-8508 > E-Mail：zhoujie2011@fujitsu.com > ------------------------------------------------ -- ------------------------------------------------ zhoujie Dept 1 No. 6 Wenzhu Road, Nanjing, 210012, China TEL：+86+25-86630566-8508 FUJITSU INTERNAL：7998-8508 E-Mail：zhoujie2011@fujitsu.com ------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2023-03-31 2:15 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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.