Date: Mon, 19 Nov 2001 12:02:57 -0800 From: Peter Wemm <peter@wemm.org> To: Doug Rabson <dfr@nlsystems.com> Cc: ia64@FreeBSD.ORG Subject: Re: Background fsck considered harmful... Message-ID: <20011119200257.B00F73811@overcee.netplex.com.au> In-Reply-To: <20011101100011.L549-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote: > I just enabled softupdates and the thing tried to use a background fsck > after a crash. It dies very quickly with: > > dscheck(da0s2f): negative bio_blkno -1917104 > panic: lockmgr: locking against myself > cpuid = 0; panic I ran into this too. I suspect there are two bugs here. One, there is probably a mismatch on a 32/64 bit API somewhere (some #ifdef __alpha__ code that also needs __ia64__ (or __LP64__) perhaps?), and two a locking bug.. perhaps something in dscheck neglected to free a lockmgr lock on return, causing a later locking bug. > Backtrace is approximately: > > panic+250 > lockmgr+9d0 > vinvalbuf+460 > ffs_truncate+460 > ffs_snapshot+2980 > ffs_mount+cd0 > vfs_mount+e10 > mount+120 > syscall+500 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011119200257.B00F73811>