Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 May 2013 18:02:42 +0300
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        Hartmut Brandt <hartmut.brandt@dlr.de>, current@freebsd.org
Subject:   Re: files disappearing from ls on NFS
Message-ID:  <E1UYHVS-000AcL-NB@kabab.cs.huji.ac.il>
In-Reply-To: <1685137855.94411.1367583746151.JavaMail.root@erie.cs.uoguelph.ca>
References:  <1685137855.94411.1367583746151.JavaMail.root@erie.cs.uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
> Hartmut Brandt wrote:
> > Hi,
> > 
> > I've updated one of my -current machines this week (previous update
> > was in
> > february). Now I see a strange effect (it seems only on NFS mounts):
> > ls or
> > even echo * will list only some files (strange enough the first files
> > from
> > the normal, alphabetically ordered list). If I change something in the
> > directory (delete a file or create a new one) for some time the
> > complete
> > listing will appear but after sime time (seconds to a minute or so)
> > again
> > only part of the files is listed.
> > 
> > A ktrace on ls /usr/src/lib/libc/gen shows that getdirentries is
> > called
> > only once (returning 4096). For a full listing getdirentries is called
> > 5
> > times with the last returning 0.
> > 
> > I can still open files that are not listed if I know their name,
> > though.
> > 
> > The NFS server is a Windows 2008 server with an OpenText NFS Server
> > which
> > works without problems to all the other FreeBSD machines.
> > 
> > So what could that be?
> > 
> Someone else reported missing files returned via "ls" recently, when
> they used a small readdirsize (below 8K). I haven't yet had a change to try
> and reproduce it or do any snooping around.
> 
> There haven't been any recent changes to readdir in the NFS client,
> except a trivial one that adds a check for vnode type being VDIR,
> so I don't see that it can be a recent NFS change.
> 
> If you can increase the readdirsize, try that to see if it avoids
> the problem. "nfsstat -m" shows you what the mount options end up
> being after doing the mount. The server might be limiting the readdirsize
> to 4K, so you should check, even if you specify a large value for
> the mount.

I don't know about current, but on 9.1-stable, the nfsstat -m only works
for root! nfsstat can be run by anybody.

> 
> rick
> 
> > Regards,
> > harti
> > _______________________________________________
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
> > "freebsd-current-unsubscribe@freebsd.org"
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
> 





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1UYHVS-000AcL-NB>