Re: zfs import panic

On Tue, Nov 13, 2007 at 03:55:06PM +0100, Pawel Jakub Dawidek wrote:
> On Mon, Nov 12, 2007 at 06:52:15PM -0200, Alexandre Biancalana wrote:
> > Hi list,
> > 
> >  After an spontaneous reboot this weekend our backup server is
> > panic'ing on zfs import. I've the vmcore file but I can't debug this
> > with kgdb
> > 
> > :/var/crash # more info.3
> > Dump header from device /dev/ad0s1b
> >   Architecture: amd64
> >   Architecture Version: 2
> >   Dump Length: 103477248B (98 MB)
> >   Blocksize: 512
> >   Dumptime: Mon Nov 12 14:56:12 2007
> >   Hostname:
> >   Magic: FreeBSD Kernel Dump
> >   Version String: FreeBSD 7.0-BETA2 #0: Mon Nov 12 11:49:07 BRST 2007
> >     root_at_:/usr/src/sys/amd64/compile/MANNY.debug
> >   Panic String: solaris assert: ss == NULL, file:
> > /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/space_map.c,
> > line: 110
> >   Dump Parity: 2217569595
> >   Bounds: 3
> >   Dump Status: good
> 
> This looks like http://bugs.opensolaris.org/view_bug.do?bug_id=6458218,
> but fix for this bug is already in FreeBSD's version...
> To recover your data you can try removing /boot/zfs/zpool.cache file
> before loading zfs.ko module, and then try to import your pool with:
> 
> 	# zpool import -o ro <pool_name>

BTW. You could try booting from Indiana CD (Solaris) and see if you can
import the pool from there.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd_at_FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!