Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Regression in 5.1.20: Reading long directory fails
From:   Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <ufapnkhqjwm.fsf@epithumia.math.uh.edu>
Date:   Tue, 3 Sep 2019 15:08:22 -0400
Cc:     Wolfgang Walter <linux@stwm.de>,
        "J. Bruce Fields" <bfields@fieldses.org>,
        linux-nfs@vger.kernel.org, km@cm4all.com,
        linux-kernel@vger.kernel.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <70F51337-A68B-473B-88B9-0CAC3D6F2AB9@oracle.com>
References: <ufak1bhyuew.fsf@epithumia.math.uh.edu> <ufay2zduosz.fsf@epithumia.math.uh.edu> <ufa5zm9s7kz.fsf@epithumia.math.uh.edu> <4418877.15LTP4gqqJ@stwm.de> <ufapnkhqjwm.fsf@epithumia.math.uh.edu>
To:     Jason L Tibbitts III <tibbs@math.uh.edu>
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk


On Sep 3, 2019, at 3:06 PM, Jason L Tibbitts III <tibbs@math.uh.edu> wrote:

>>>>>> "WW" =3D=3D Wolfgang Walter <linux@stwm.de> writes:
>=20
> WW> What filesystem do you use on the server? xfs?
>=20
> Yeah, it's XFS.
>=20
> WW> If yes, does it use 64bit inodes (or started to use them)?
>=20
> These filesystems aren't super old, and were all created with the
> default RHEL7 options.

I think that means no 64-bit inodes.


> I'm not sure how to check that 64 bit inodes are
> being used, though.  xfs_info says:
>=20
> meta-data=3D/dev/mapper/nas-faculty--08 isize=3D256    agcount=3D4, agsize=
=3D3276800 blks
>         =3D                       sectsz=3D512   attr=3D2, projid32bit=3D1=

>         =3D                       crc=3D0        finobt=3D0 spinodes=3D0
> data     =3D                       bsize=3D4096   blocks=3D13107200, imaxp=
ct=3D25
>         =3D                       sunit=3D0      swidth=3D0 blks
> naming   =3Dversion 2              bsize=3D4096   ascii-ci=3D0 ftype=3D0
> log      =3Dinternal               bsize=3D4096   blocks=3D6400, version=3D=
2
>         =3D                       sectsz=3D512   sunit=3D0 blks, lazy-coun=
t=3D1
> realtime =3Dnone                   extsz=3D4096   blocks=3D0, rtextents=3D=
0
>=20
> WW> Do you set a fsid when you export the filesystem?
>=20
> I have never done so on any server.
>=20
> And note that the servers are basically unchanged for quite some time,
> while the problem I'm having is new.  I want to find some server-related
> cause for this but so far I haven't been able to do so.  It seems my
> best option now seems to be to migrate all data off of this server and
> then wipe, reinstall and see if the problem reoccurs.
>=20
> - J<