Date: Fri, 26 Jun 2009 14:59:18 +0200
From: Thomas Backman <serenity@exscape.org>
To: Stanislav Sedov <stas@FreeBSD.org>
Cc: freebsd-current@freebsd.org, Artem Belevich <fbsdlist@src.cx>
Subject: Re: ZFS : panic("sleeping thread")
Message-ID: <AEA6B136-7464-4A8A-A683-69D651B4625B@exscape.org>
In-Reply-To: <20090626164639.71a34f62.stas@FreeBSD.org>
References: <ed91d4a80905271058mbc1fc68g184def5097080cbc@mail.gmail.com> <993B7B5B-1B6B-48A5-8425-6A1D071335A9@exscape.org> <20090626164639.71a34f62.stas@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 26, 2009, at 02:46 PM, Stanislav Sedov wrote: > On Thu, 18 Jun 2009 13:49:46 +0200 > Thomas Backman <serenity@exscape.org> mentioned: > >> Anyone have any updates on this? I just got a "sleeping thread" panic >> in ZFS after doing a zfs rollback. Unfortunately, "panic" in the >> debugger resulted in "dump device too small" (despite being RAM- >> sized) >> so I don't have a BT... However the BT I got in the debugger was >> *not* >> the same as yours. There was no _sx_xlock in it, but that's pretty >> much all I know about it. :( >> > > Hi, Thomas! > > Can you, please, try with the following patch? Thanks! > > -- > Stanislav Sedov > ST4096-RIPE I could (and might, too), but unfortunately (well, I guess...) I haven't been able to reproduce this, despite writing a script to really stress test it. It's either pretty darn random, or I was simply wrong about the rollback being involved. I've only gotten it once since I started using -CURRENT in early May(?) so I don't think I could tell whether the patch helps or not. :( Regards, Thomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AEA6B136-7464-4A8A-A683-69D651B4625B>