Re: nfs/001 failing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 5, 2022 at 12:33 PM Chuck Lever III <chuck.lever@xxxxxxxxxx> 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
>
>
>



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux