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

On Mon, May 31, 2004 at 10:42:36AM +0200, uwe@6bone.informatik.uni-leipzig.=
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?

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. Also, what kernel version are you=20
using?

> ktrace rm -rf foo/foo
> kdump > kdump.txt

Then make kdump.txt available.

Take care,

Bill

--uQr8t48UFsdbeI+V
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAvNx7Wz+3JHUci9cRAqDgAKCEi9FfRVTTGeUpeHfm/RIXPQ88HACfdt7e
/nBNWTyrBJUN91Vvp7qdxHQ=
=hUiw
-----END PGP SIGNATURE-----

--uQr8t48UFsdbeI+V--