Date: Wed, 6 Oct 2010 20:51:49 +0200 From: Kai Gallasch <gallasch@free.de> To: freebsd-fs@freebsd.org Subject: Re: Locked up processes after upgrade to ZFS v15 Message-ID: <E5332812-379B-4EC1-A134-12176C718B2E@free.de> In-Reply-To: <201010061732.o96HW2Vi005945@higson.cam.lispworks.com> References: <39F05641-4E46-4BE0-81CA-4DEB175A5FBE@free.de> <201010061732.o96HW2Vi005945@higson.cam.lispworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 06.10.2010 um 19:32 schrieb Martin Simmons: >>>>>> On Wed, 6 Oct 2010 14:28:31 +0200, Kai Gallasch said: >>=20 >> How can I debug this and get further information? >=20 > 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 = =20 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 procstat for process 24731 (state: zfsmrb) # procstat -k -k 24731 PID TID COMM TDNAME KSTACK = =20 24731 102273 httpd - mi_switch+0x21b = sleepq_switch+0x123 sleepq_wait+0x4d _sleep+0x369 zfs_freebsd_read+0x2a6 = VOP_READ_APV+0xaf vnode_pager_generic_getpages+0x3ea = VOP_GETPAGES_APV+0xb5 vnode_pager_getpages+0x8c vm_fault+0x685 = trap_pfault+0x128 trap+0x52c calltrap+0x8 In my original post I wrote that only apache httpd processes would lock = up.. This is wrong. Several other non-httpd processes also got stuck in state = zfs or zfsmrb. -Kai.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E5332812-379B-4EC1-A134-12176C718B2E>