On Wed, Jan 21, 2004 at 01:39:59PM -0500, Ken Smith wrote: > I have the same machine (Dell 2650) and it's getting locked up in > a very similar way, you don't need to get NFS involved to have > processes get locked uup in getblk. I'm slowly trying to remove > variables but so far it seems like network activity of some sort > helps cause the lockup. The easiest way to make it lock up was > doing backups through the network. But find's cranked up by the > nightly cron jobs can get locked in getblk as well (while there > are no NFS partitions mounted, but things like cvsup updates of > a local repo are happening). Once things start to get locked up > like this the system slowly degrades. I can usually ssh in and > reboot it if I catch it soon enough, if I leave it for a couple > of days it will seem like it's up (rwhod is running) but ssh-ing > in won't work. > > sledge (amd64 machine in the cluster) was showing similar symptoms > this morning, it had failed doing its nightly rebuild/reboot and > things like mtree commands were wedged since a day or two ago. > > The Dell I have here is not really in production at all, if me > doing anything here will help I'm game... OK, sounds like it might be something to do with vnode locking. Turning on DEBUG_VFS_LOCKS might help to find it. Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:39 UTC