Date: Thu, 19 Nov 2015 17:38:21 +0100 From: Yamagi Burmeister <lists@yamagi.org> To: rs@bytecamp.net Cc: freebsd-fs@freebsd.org Subject: Re: filesystem deadlock, process in vodead state Message-ID: <20151119173821.b3da4b7d92571b723d4c5e5f@yamagi.org> In-Reply-To: <564D9930.1080509@bytecamp.net> References: <564D9930.1080509@bytecamp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, last week I've observed a similar deadlock on a FreeBSD 10.2 machine with UFS filesystem. I haven't saved the procstat output because I suspected broken hardware (The SSD wearout indicator was down to 22. There weren't any ATA errors in dmesg), but as far as I remember the kernel stacks looked similar. ufs_open() instead of zfs_freebsd_open() of course. Regards, Yamagi On Thu, 19 Nov 2015 10:41:04 +0100 Robert Schulze <rs@bytecamp.net> wrote: > Hi, > > on an SSD-only mirrored pool which was idle for about 30 days, I noticed > a stuck chksetuid run from periodic. The "find" process is stuck on > vodead state. > > I found out which directory is affected via procstat -f and tried to ls > it, now this ls is stuck in above state, too (no surprise). > > procstat -kk output is: > > 1816 102485 find - mi_switch+0xe1 > sleepq_wait+0x3a _sleep+0x287 vnode_create_vobject+0x100 > zfs_freebsd_open+0xf5 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 > vn_open_cred+0x33e kern_openat+0x26f amd64_syscall+0x33a Xfast_syscall+0xfb > > 71376 102400 ls - mi_switch+0xe1 > sleepq_wait+0x3a _sleep+0x287 vnode_create_vobject+0x100 > zfs_freebsd_open+0xf5 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 > vn_open_cred+0x33e kern_openat+0x26f amd64_syscall+0x33a Xfast_syscall+0xfb > > The processes are not killable. > So what is this state and how to fix the deadlocked filesystem? I'm able > to give any debugging information, just give me some pointers. > > # uname: FreeBSD 10.2-RELEASE-p5 #1 r289218 > > # zpool status > > pool: home > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > home ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > gpt/mirror0-a ONLINE 0 0 0 > gpt/mirror0-b ONLINE 0 0 0 > mirror-1 ONLINE 0 0 0 > gpt/mirror1-a ONLINE 0 0 0 > gpt/mirror1-b ONLINE 0 0 0 > mirror-2 ONLINE 0 0 0 > gpt/mirror2-a ONLINE 0 0 0 > gpt/mirror2-b ONLINE 0 0 0 > mirror-3 ONLINE 0 0 0 > gpt/mirror3-a ONLINE 0 0 0 > gpt/mirror3-b ONLINE 0 0 0 > > errors: No known data errors > > > with kind regards, > Robert Schulze > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -- Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151119173821.b3da4b7d92571b723d4c5e5f>