On Tue, Nov 23, 2004 at 11:50:23AM +0800, David Teigland wrote: > > On Mon, Nov 22, 2004 at 12:44:07PM -0800, Daniel McNeil wrote: > > > The full stack traces are available here: > > http://developer.osdl.org/daniel/gfs_umount_hang/ > > Thanks, it's evident that the dlm became "stuck" on the node that's not > doing the umount. All the hung processes are blocked on the dlm's > "in_recovery" lock. There also seems to be a GFS process with a failed "down_write" in dlm_unlock which might be a clue. It's not the in_recovery lock because that's only held for read during normal locking operations so it must be either the res_lock or the ls_unlock_sem. odd as those are normally only held for very short time periods. -- patrick
