Date: Thu, 9 Mar 2006 17:50:06 GMT From: Kris Kennaway <kris@obsecurity.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/94261: [ufs2] deadlock between ffs_mksnap and mysnc Message-ID: <200603091750.k29Ho6mU043317@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/94261; it has been noted by GNATS. From: Kris Kennaway <kris@obsecurity.org> To: Steve Watt <steve@Watt.COM> Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/94261: [ufs2] deadlock between ffs_mksnap and mysnc Date: Thu, 9 Mar 2006 12:40:44 -0500 On Wed, Mar 08, 2006 at 11:15:43PM -0800, Steve Watt wrote: > >Environment: > System: FreeBSD wattres.Watt.COM 5.5-PRERELEASE FreeBSD 5.5-PRERELEASE #11: Wed Mar 1 10:54:09 PST 2006 root@wattres.Watt.COM:/usr/obj/usr/src/sys/WATTRES i386 > > > > >Description: > > Per a thread on -hackers back in May '05 titled "snapshots and innds", > I'm finally getting around (sorry) to filing the PR. > > I got a kernel core dump that I can do useful stuff with. The system > was mostly operating normally, except that any attempt to access the > /news partition (which has articles, tradspool.map, overviews, and > incoming/outgoing data) would get stuck in "suspfs". > > So I forced a dump from ddb. The mount point does (as one would > expect) have MNTK_SUSPEND set. > > I see mksnap_ffs sitting waiting for "ufs" (really vnode 0xc19af318), > which it got to via: This is probably fixed with Tor's latest commits to 6.1. I don't know if he intends to merge the changes to 5.5, but that branch is basically dead and you should upgrade to 6.x. Can you confirm it is fixed in 6.1? Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603091750.k29Ho6mU043317>