Date: Thu, 4 Apr 2013 11:12:48 -0500 From: Kevin Day <toasty@dragondata.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org Subject: Re: kern/177536: zfs livelock (deadlock) with high write-to-disk load Message-ID: <FE62319F-4BF5-4E35-9320-590457C79FE2@dragondata.com> In-Reply-To: <515DA525.3020006@FreeBSD.org> References: <201304041540.r34Fe1Ka057203@freefall.freebsd.org> <D75AD2BC-E02A-45D2-BDDE-57B99ED77AA0@dragondata.com> <515DA525.3020006@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 4, 2013, at 11:07 AM, Andriy Gapon <avg@FreeBSD.org> wrote: > on 04/04/2013 19:05 Kevin Day said the following: > [a lot] >=20 > One link: https://wiki.freebsd.org/AvgZfsDeadlockDebug Sorry, should have mentioned i've seen this. I've tried procstat, but i've failed at keeping it cached long enough to = use it when this happens. If I try running it, the shell gets stuck in = 'ufs'. I'm going to add a cron job to just run procstat periodically so = hopefully i can run it without it needing to touch the disks. I built a more debug friendly kernel and tried to drop to ddb when this = happened, but it didn't provide anything useful. When I hit 'enter' on = 'alltrace' it hard locked without printing anything. I haven't been able to trigger a core dump, and this system has no = serial or firewire ports for live debugging.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE62319F-4BF5-4E35-9320-590457C79FE2>