Date: Thu, 17 Mar 2011 09:24:50 -0700 From: Freddie Cash <fjwcash@gmail.com> To: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: ZFS import panic with r219703 Message-ID: <AANLkTikwOhLe4=1b-zc4XCMHeL=ANvApyww%2BjG5gykC5@mail.gmail.com> In-Reply-To: <AANLkTikEBAXz6LO3JOJq7ro0_MRcSUBZa2Fq0WdcJxsQ@mail.gmail.com> References: <AANLkTikEBAXz6LO3JOJq7ro0_MRcSUBZa2Fq0WdcJxsQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 16, 2011 at 4:03 PM, Freddie Cash <fjwcash@gmail.com> wrote: > Anytime I try to import my pool built using 24x HAST devices, I get > the following message, and the system reboots: > > panic: solaris assert: dmu_free_range(os, smo->smo_object, 0, -1ULL, > tx) =3D=3D 0, file: > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/spa= ce_map.c, > line: 484 > > Everything runs nicely if I don't import the pool. > > Doing a "zpool import" shows that one of the HAST devices is FAULTED > "corrupted data". > > Haven't tried anything to remove/replace the faulted device, just > wanted to see if anyone knew what the above error meant. > > Pool was created using r219523 and successfully copied over 1 TB of > data from another ZFS system. =C2=A0Had some issues with gptboot this > morning and the system locking up and rebooting a bunch, and now the > pool won't import. Hrm, it looks like the "pool roll-back on import" feature is working. # zpool import -F -d /dev/hast storage The above command imported the pool successfully. No dmu_free_range() errors. No solaris assert. No kernel panic. Will try hammering on the system a bit to see if that sticks or whether the space_map errors show up again. --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikwOhLe4=1b-zc4XCMHeL=ANvApyww%2BjG5gykC5>