Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <BF47B6B7-CB52-4E14-94B0-E28FD5C52234@oracle.com>
In-Reply-To: <BF47B6B7-CB52-4E14-94B0-E28FD5C52234@oracle.com>
From:   Olga Kornievskaia <aglo@umich.edu>
Date:   Tue, 6 Sep 2022 11:30:00 -0400
Message-ID: <CAN-5tyGxxp-TD-zjjkMoS-snPYyfy+PuCV4BR6eofdmFt=-7Dw@mail.gmail.com>
Subject: Re: nfs/001 failing
To:     Chuck Lever III <chuck.lever@oracle.com>
Cc:     Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Sep 5, 2022 at 12:33 PM Chuck Lever III <chuck.lever@oracle.com> wrote:
>
> Hi-
>
> Bruce reminded me I'm not the only one seeing this failure
> these days:
>
> > nfs/001 4s ... - output mismatch (see /root/xfstests-dev/results//nfs/001.out.bad)
> >    --- tests/nfs/001.out      2019-12-20 17:34:10.569343364 -0500
> >    +++ /root/xfstests-dev/results//nfs/001.out.bad    2022-09-04 20:01:35.502462323 -0400
> >    @@ -1,2 +1,2 @@
> >     QA output created by 001
> >    -203
> >    +3
> >    ...
>
>
> I'm looking at about 5 other priority bugs at the moment. Can
> someone else do a little triage?
>

Is there any more info about this (like exported file system or
something or a network trace)? I typically hit this issue when I get a
client and it doesn't have nfs4_getfacl command installed.

>
> --
> Chuck Lever
>
>
>