On Thu, Jan 11, 2001 at 10:47:03AM -0500, Paul Mather wrote:
> Okay, thanks.  But, alas, when I do that find, it also never returns,
> and hangs around forever in the "vnlock" state.

Ha. yes, of course.

> 
> Can anyone suggest the problem of which this is indicative?  Am I naive
> in assuming that if there was a bad block, for example, eventually the
> disk I/O would bomb out with EIO or similar?

I guess it's a directory which is locked, preventing accesses to
files inside it. A good way to find which directory is locked is to start
a 'find / -xdev -print'.
It will hang too but with some luck you'll be able to guess which directory
it is from what's printed.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--