Date: Tue, 11 Mar 2008 01:35:33 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Eric F Crist <ecrist@secure-computing.net> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS kernel panic in single user Message-ID: <47D5D3D5.30609@FreeBSD.org> In-Reply-To: <6A002150-F8D8-4958-ACA8-7178403C6A4F@secure-computing.net> References: <6A002150-F8D8-4958-ACA8-7178403C6A4F@secure-computing.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric F Crist wrote: > Hey folks, > > Please 'reply-all' as I'm not on the mailing list. > > For background, we've got the following setup: > > Dell PowerEdge 1650 w/2xP3 1.113GHz 1GB ECC RAM > Dell SCSI ACI Backplane 1x3 > 2x 73GB Seagate 10K SCSI Drives > 1x IDE->CF Converter > 1x 1GB CF Card > > We loosely followed the instructions over at > http://www.ish.com.au/solutions/articles/freebsdzfs. There is one key > difference to our setup from the ish.com.au instructions. We are using > the CF card for our /bootdir partition to get the FreeBSD kernel loaded > enough to load the ZFS modules. We don't have a boot record or anything > on the two SCSI drives. Our idea being that, if a drive fails, the CF > card and all the boot goodness stays where it is. > > To my point. I ran across the ZFSKnownProblems wiki page which strongly > encourages the reporting of any problems we have. From a booted system, > I issued the 'shutdown now' command to bring the system down to > single-user mode. Issuing a reboot command from this point, I get the > following errors: > > Spin lock 0xc0bdca00 (sched lock) held by 0xc3f10c60 (tid 100001) > too long > panic: spin lock held too long Please add WITNESS and DDB and determine the backtrace of the thread holding the lock, then file this information in a PR. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D5D3D5.30609>