On Sat, 2012-03-24 at 12:53 -0400, Matt W. Benjamin wrote: > Hi, > > I don't think anything is. Or, people originally reported the behavior against knfsd. > > Matt There is a known issue with ext2/3/4 generating non-unique readdir cookies. It rarely hits you when you are creating small directories, but it frequently hits you with larger ones. A fix is underway that should significantly reduce the frequency of cookie collisions. Recent NFS clients will actually detect the presence of those cookie loops, and log them in the kernel syslog. That would therefore be the first thing that I'd check if confronted with this kind of problem. Cheers Trond > ----- "Trond Myklebust" <Trond.Myklebust@xxxxxxxxxx> wrote: > > > On Sat, 2012-03-24 at 12:34 -0400, Matt W. Benjamin wrote: > > > Hi, > > > > > > Folks testing linux nfs + Ganesha with bonnie++ have noticed the > > issue described here (but I didn't see traffic on this list): > > > > > > http://bugs.centos.org/view.php?id=5496 > > > https://bugzilla.redhat.com/show_bug.cgi?id=789452 > > > > > > Ie, an application which unlinks on an open (nfs) directory stream, > > and continues to read and unlink progressively, will generally not see > > all the entries originally in the stream. Reopening the stream ives > > the "correct" result. So, apparently older clients were more > > forgiving, as mentioned in the links. Is the current behavior one the > > client is intending? > > > > > > Thanks, > > > > > > Matt > > > > What is so particular about the ganesha readdir implementation? > > > > -- > > Trond Myklebust > > Linux NFS client maintainer > > > > NetApp > > Trond.Myklebust@xxxxxxxxxx > > www.netapp.com > -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com ��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
