Date: Thu, 11 Dec 2003 18:40:51 -0500 From: Jesse Guardiani <jesse@wingnet.net> To: freebsd-current@freebsd.org Subject: Re: LOR: ffs_snapshot.c from 5.2-BETA Message-ID: <brava3$jpb$2@sea.gmane.org> References: <bra7n5$c1l$1@sea.gmane.org> <200312112212.hBBMC6eF056403@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Don Lewis wrote: > On 11 Dec, Jesse Guardiani wrote: >> Don Lewis wrote: >> >>> On 9 Dec, Jesse Guardiani wrote: >>>> Howdy list, >>>> >>>> Has anyone seen this yet? Happened while I was fsck'ing my >>>> external USB hard drive a few days ago. Didn't see anything >>>> recent like this in the archive (Nov was the closest, but it >>>> looked like a separate issue). >>>> >>>> >>>> acquiring duplicate lock of same type: "vnode interlock" >>>> 1st vnode interlock @ ufs/ffs/ffs_snapshot.c:488 >>>> 2nd vnode interlock @ ufs/ffs/ffs_snapshot.c:491 >>>> Stack backtrace: >>>> backtrace(c06df4ef,c06e3b95,c06eca1f,1eb,246) at backtrace+0x17 >>>> witness_lock(c42b9a28,8,c06eca1f,1eb,c3b48678) at witness_lock+0x672 >>>> _mtx_lock_flags(c42b9a28,0,c06eca16,1eb,c19dbf00) at >>>> _mtx_lock_flags+0xba >>>> ffs_snapshot(c3abbc00,bfbfed88,70,c05482f3,c073f800) at >>>> ffs_snapshot+0x1759 >>> >>> A related LOR was reported a few days ago. I think it is harmless, but >>> I also think I know how to fix it. >> >> Going once... Going twice... > > It's more complicated that I thought at first. I hoping to have some > time to work on it over the holidays. Well at least you understand the problem and are willing to work on it. :) I'm thread ignorant. Hopefully one of my relatives will buy me "Programming with POSIX Threads" by David R. Butenhof, for Christmas so I can stop feeling so useless. :) -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?brava3$jpb$2>