Date: Thu, 17 Mar 2011 07:39:27 +0200 From: Volodymyr Kostyrko <c.kworr@gmail.com> To: Freddie Cash <fjwcash@gmail.com> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: ZFS import panic with r219703 Message-ID: <4D819E8F.6040306@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
17.03.2011 01:03, Freddie Cash 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) == 0, file: > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/space_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. Had some issues with gptboot this > morning and the system locking up and rebooting a bunch, and now the > pool won't import. Oh, the garbled space_map issue. The system will assert any time the pool is imported in r/w. ZFSv28 is able to import pool in r/o state and this is as far as I know the only way to recover data from such pool. Anyway pool should be recreated. -- Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D819E8F.6040306>