On Thu, 2016-04-14 at 14:15 -0500, Ziemowit Pierzycki wrote: > [<ffffffffa012d158>] rpc_wait_bit_killable+0x38/0x80 [sunrpc] > [<ffffffffa012d11d>] __rpc_wait_for_completion_task+0x2d/0x30 > [sunrpc] > [<ffffffffa05caf30>] nfs4_run_open_task+0x130/0x1a0 [nfsv4] > [<ffffffffa05cd77d>] nfs4_open_recover_helper+0x16d/0x230 [nfsv4] > [<ffffffffa05cd875>] nfs4_open_recover+0x35/0xb0 [nfsv4] > [<ffffffffa05cff5d>] nfs4_open_expired.isra.60+0xcd/0x180 [nfsv4] > [<ffffffffa05d003e>] nfs40_open_expired+0x2e/0x40 [nfsv4] > [<ffffffffa05e3805>] nfs4_do_reclaim+0x175/0x5f0 [nfsv4] > [<ffffffffa05e416e>] nfs4_run_state_manager+0x4ee/0x7d0 [nfsv4] > [<ffffffff810bc8b8>] kthread+0xd8/0xf0 > [<ffffffff8177999f>] ret_from_fork+0x3f/0x70 > [<ffffffffffffffff>] 0xffffffffffffffff > > Waiting for something to complete but it can't? > Yes. That stack means that it's trying to reclaim an open file (on NFSv4.0), and is waiting on the reply. > On Thu, Apr 14, 2016 at 2:08 PM, Benjamin Coddington > <bcodding@xxxxxxxxxx> wrote: > > > > > > On Thu, 14 Apr 2016, Ziemowit PIerzycki wrote: > > > > > > > > I have a strange issue when NFS4 mounts to a Netapp filer freeze > > > on my Linux > > > KVMs. Looking over few things I noticed a process "10.10.10.20- > > > man" is in D > > > state but I can't find anything information about it. Mainly > > > because > > > 10.10.10.20 is the IP of the filer and searching for "-man" is > > > too generic. > > > > > > Why would this process be frozen? > > This is the nfs4 state manager process. What's in the file: > > /proc/<pid of that process>/stack > > > > Ben > -- > 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 -- Jeff Layton <jlayton@xxxxxxxxxxxxxxx> -- 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
