Linux NFS development
 help / color / mirror / Atom feed
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: Wed, 29 Mar 2023 00:15:52 +0000	[thread overview]
Message-ID: <3218f65a-dcf6-32c3-5eed-32e2aa9735e5@fujitsu.com> (raw)
In-Reply-To: <d09ec9bc-a49a-81da-d746-87ba9a137833@fujitsu.com>

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
------------------------------------------------

  parent reply	other threads:[~2023-03-29  0:17 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
2023-03-17 18:14       ` Mora, Jorge
2023-03-29  0:15       ` zhoujie2011 [this message]
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=3218f65a-dcf6-32c3-5eed-32e2aa9735e5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox