[Samba] Missing Files/Missing Folders from an NFS Share

[Jeremy Allison]

On Thu, Feb 16, 2023 at 12:20:27PM -0800, Jeremy Allison via samba wrote:
>
>doesn't return us to the same position in the directory
>listing, then we are broken and will not return the complete
>list of files.
>
>This is what Ralph is saying when he says that NFS is
>broken w.r.t listing directories. What NFS server are
>you using ?

Oh I just remembered, you're using the Amazon NFS
server.

>This looks relevent:
>
>https://lore.kernel.org/all/CAAmbk-e-YQAPo6QyNB0aJyc9qzUShmEC+x5eTR7wqp1ABWADsg@mail.gmail.com/T/

Indeed. Note the comment from Trond (NFS client
maintainer in the Linux kernel).

---------------------------------------------------------------
On Thu, 2022-09-08 at 10:45 +0100, Chris Chilvers wrote:
> I should have flagged this as a bug on the first email.
> 
> I've run into an interesting issue using VAST data, their NFS
> implementation
> makes use of the full 64 bit unsigned range allowed by NFS cookie for
> READDIR
> and READDIRPLUS.
> 
> The issue is that this 64 unsigned value is used for the directory's
> file
> position (d_off), which is a 64 bit signed value. This can cause
> readdir and
> telldir to return negative values.

Known issue that we had to deal with 25 years ago for 32 bit systems
when glibc first decided to make lseek() return signed values (struct
old_linux_direct still has it as an unsigned value).

So VAST have had a long time to learn not to do this...

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust at hammerspace.com
---------------------------------------------------------------

Looks like Amazon may have the same bug.