Date: Fri, 8 Oct 2010 16:19:07 +0100 From: Martin Simmons <martin@lispworks.com> To: freebsd-fs@freebsd.org Subject: Re: Locked up processes after upgrade to ZFS v15 Message-ID: <201010081519.o98FJ7qJ026875@higson.cam.lispworks.com> In-Reply-To: <E5332812-379B-4EC1-A134-12176C718B2E@free.de> (message from Kai Gallasch on Wed, 6 Oct 2010 20:51:49 %2B0200) References: <39F05641-4E46-4BE0-81CA-4DEB175A5FBE@free.de> <201010061732.o96HW2Vi005945@higson.cam.lispworks.com> <E5332812-379B-4EC1-A134-12176C718B2E@free.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Wed, 6 Oct 2010 20:51:49 +0200, Kai Gallasch said: > > Am 06.10.2010 um 19:32 schrieb Martin Simmons: > > >>>>>> On Wed, 6 Oct 2010 14:28:31 +0200, Kai Gallasch said: > >> > >> How can I debug this and get further information? > > > > procstat -k -k $pid will generate a backtrace (or replace $pid by -a for all > > processes). > > procstat for process 12111 (state: zfs) > sonnenkraft:~ # procstat -k -k 12111 > PID TID COMM TDNAME KSTACK > 12111 102385 httpd - mi_switch+0x21b sleepq_switch+0x123 sleepq_wait+0x4d __lockmgr_args+0x7ae vop_stdlock+0x39 VOP_LOCK1_APV+0x9b _vn_lock+0x57 vget+0x7b cache_lookup+0x4e0 vfs_cache_lookup+0xc0 VOP_LOOKUP_APV+0xb7 lookup+0x3d3 namei+0x457 vn_open_cred+0x1e3 kern_openat+0x181 syscall+0x102 Xfast_syscall+0xe2 It looks like this thread is waiting for a lock. So the question is, which thread is holding the lock? It might be possible to see from procstat -k -k -a but otherwise I think you will need to run it with kdb and look at the lock. __Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010081519.o98FJ7qJ026875>