NFS problem: file doesn't appear in file listing, but can be accessed directly

[Rick Macklem]

> On 08/08/2010 02:06 AM, Rick Macklem wrote:
> >> On 07.08.2010, at 02:35, Rick Macklem wrote:
> >>
> >> I agree, this must be some kind of server issue then. Still, I
> >> wonder
> >> why the solaris client didn't show the problem...
> >>
> >>
> > 2 things:
> > 1 - the solaris client uses ReaddirPlus and not Readdir RPCs by
> >      default (I can't remember if that default can be overridden?).
> I don't know whether this counts or not, but I've tried with an old
> Solaris (x86) 8 (uname says it's Generic_108529-06).
> 
> > ps: I don't recall the previous emails mentioning that the "ls"
> >      was ok for a solaris client.
> >
> It was in 4C582968.9000303 at fsn.hu:
> "I've mounted the share from an old Solaris box, which sees the file."
> 
> This means, when I issue an ls | grep problematic_fname, I can see the
> filename.
> BTW, this turned out to be incorrect, because I've tested with the
> same
> (one of the missing) filename.
> Doing a find . in the directory on both FreeBSD and Solaris client
> shows
> some differences.
> So what I have now is: both the normal and the experimental NFSD show
> the problem on both FreeBSD and Solaris clients (only the missing file
> names are different).
> 
> On Solaris there are 78 files missing, on FreeBSD there are 193, I
> haven't checked that they are persistent across reboots or not.

I believe that this problem might be fixed by r216774 in head (for the
regular NFS server) and r216691 in head (for the experimental NFS server).

The above patches fixes a problem that would occur when ZFS generated
non monotonically increasing directory offset cookies and readdir in
the server would skip over some directory entries.

rick