--mvpLiMfbWzRoNl4x
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 01, 2004 at 12:43:55PM -0700, Bill Studenmund wrote:
> On Mon, May 31, 2004 at 10:42:36AM +0200, uwe@6bone.informatik.uni-leipzi=
g.de wrote:
> > hello,
> >=20
> > to show you the problem I will do the following:
> >=20
> > 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
> >=20
> > 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?
>=20
> Please ktrace the rm command while performing this test. Without that=20
> information, it is impossible to tell if the problem is with the nfs=20
> client code or with the rm command.

Actually, from looking at the logs, I think your rm command is messed up,=
=20
or something's wrong in READDIR handling. You'll note that there is only=20
one READDIR call in your log. When I tested this, I got a READDIR on each=
=20
directory.

rm is supposed to look at everything and dive into directories. Either=20
info isn't getting back right to tell rm that "foo" is a directory, or rm=
=20
is ignoring that fact.

Take care,

Bill

--mvpLiMfbWzRoNl4x
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAvORyWz+3JHUci9cRAk0BAJ9RBeDv2CjCd2wQkg+x1QlYuAU79QCgiMMx
rWnqHzUR4BtU9gNMF4ttViU=
=JuIc
-----END PGP SIGNATURE-----

--mvpLiMfbWzRoNl4x--