> > > bash-2.05b# mkdir -p foo/foo/foo
> > > bash-2.05b# rm -rf foo
> > > rm: foo/foo: Operation not permitted
> > > rm: foo: Directory not empty
> > > 
> > > I recorded the nfs communication at a network trace
> > > (http://139.18.25.35/maillinglist.cap)
> > > Can anyone give me a hint what the problem could be?
> > 
> > Please ktrace the rm command while performing this test. Without that 
> > information, it is impossible to tell if the problem is with the nfs 
> > client code or with the rm command.
> 
> Actually, from looking at the logs, I think your rm command is messed up, 
> or something's wrong in READDIR handling. You'll note that there is only 
> one READDIR call in your log. When I tested this, I got a READDIR on each 
> directory.
> 
> rm is supposed to look at everything and dive into directories. Either 
> info isn't getting back right to tell rm that "foo" is a directory, or rm 
> is ignoring that fact.

my guess is, SFU always return nlink==2 for directory and
it confuses our fts.

YAMAMOTO Takashi