From: "zhoujie2011@fujitsu.com" <zhoujie2011@fujitsu.com>
To: mora <mora@netapp.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: nfstest_delegation test can not stop
Date: Tue, 14 Mar 2023 02:28:09 +0000 [thread overview]
Message-ID: <d5ed9eec-4bf4-8d70-0960-a30b2ef03938@fujitsu.com> (raw)
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
------------------------------------------------
next reply other threads:[~2023-03-14 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 2:28 zhoujie2011 [this message]
2023-03-15 11:40 ` nfstest_delegation test can not stop 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
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=d5ed9eec-4bf4-8d70-0960-a30b2ef03938@fujitsu.com \
--to=zhoujie2011@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