On Wed, 2002-11-27 at 05:33, Theodore Ts'o wrote: 
> Well, even if the NFS server is generating bad cookies (and that may
> be possible), the NFS client should be more robust and not spin in a
> loop forever.
> 
> Can you send me a directory list (from the server) of the directory in
> question?  Also, can you send me the output of dumpe2fs -h on the
> filesystem.  I'll need the later to get the seed for the htree hash,
> so I can try replicating this on my end.

The hash seed is 80f11989-89cc-4046-80d8-4aef72a7f80f (extracted with
tune2fs -l).  The listing is attached.

> Also, have you tried running e2fsck on filesystem on the server?  It
> would be very interesting to confirm whether or not the filesystem is
> consistent.

This happens very regularly.  Each time it does I create a new directory
and move everything over, which presumably works because it rehashes
everything and/or changes the alignment of particular direntries with
respect to the NFS reply packets.  What I'm saying is that if the
filesystem is getting into an inconsistent state, it is doing so at a
very high rate.  I'll check it anyway... all OK.

	J