On Mon, 2011-08-01 at 23:23 -0400, Jim Rees wrote: > Myklebust, Trond wrote: > > That's a different issue. If you do an 'echo t >/proc/sysrq-trigger', > then do you see any other process that is stuck in the nfs layer and > that might be holding the inode->i_mutex? > > Hard to tell. There are a couple of possibilities. I've put the console > output here, and will investigate more in the morning: > > http://www.citi.umich.edu/projects/nfsv4/pnfs/block/download/console.txt Hmm... You don't seem to have all the mutex debugging options enabled, but I strongly suspect that this thread is the culprit. > t_mtab D 0000000000000000 0 1833 1698 0x00000080 > ffff880072f73ac8 0000000000000086 ffff880072f73a98 ffffffff00000000 > ffff880072f72010 ffff8800698fdc00 0000000000012c80 ffff880072f73fd8 > ffff880072f73fd8 0000000000012c80 ffffffff81a0c020 ffff8800698fdc00 > Call Trace: > [<ffffffffa01f5a52>] ? rpc_queue_empty+0x29/0x29 [sunrpc] > [<ffffffffa01f5a81>] rpc_wait_bit_killable+0x2f/0x33 [sunrpc] > [<ffffffff81453eec>] __wait_on_bit+0x43/0x76 > [<ffffffff81453f88>] out_of_line_wait_on_bit+0x69/0x74 > [<ffffffffa01f5a52>] ? rpc_queue_empty+0x29/0x29 [sunrpc] > [<ffffffff81069213>] ? autoremove_wake_function+0x38/0x38 > [<ffffffffa01f5f0a>] __rpc_execute+0xed/0x249 [sunrpc] > [<ffffffffa01f60a3>] rpc_execute+0x3d/0x42 [sunrpc] > [<ffffffffa01efbca>] rpc_run_task+0x79/0x81 [sunrpc] > [<ffffffffa028c3b7>] nfs4_call_sync_sequence+0x60/0x81 [nfs] > [<ffffffff810fe4af>] ? kmem_cache_alloc_trace+0xab/0xbd > [<ffffffffa028c55e>] _nfs4_call_sync_session+0x14/0x16 [nfs] > [<ffffffffa0279b7d>] ? nfs_alloc_fattr+0x24/0x57 [nfs] > [<ffffffffa028ecd1>] _nfs4_proc_remove+0xcd/0x110 [nfs] > [<ffffffffa028ed43>] nfs4_proc_remove+0x2f/0x55 [nfs] > [<ffffffffa027524f>] nfs_unlink+0xf5/0x1a3 [nfs] > [<ffffffff81114c66>] vfs_unlink+0x70/0xd1 > [<ffffffff8111714d>] do_unlinkat+0xd5/0x161 > [<ffffffff8112247e>] ? mntput+0x21/0x23 > [<ffffffff8111381d>] ? path_put+0x1d/0x21 > [<ffffffff8109932e>] ? audit_syscall_entry+0x119/0x145 > [<ffffffff811171ea>] sys_unlink+0x11/0x13 > [<ffffffff8145b612>] system_call_fastpath+0x16/0x1b Any idea which file that thread is deleting, and why that might be hanging? -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
