On Thu, Mar 17, 2011 at 9:24 AM, Freddie Cash <fjwc...@gmail.com> wrote: > On Wed, Mar 16, 2011 at 4:03 PM, Freddie Cash <fjwc...@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) == 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. > > 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.
Damn, of course that would be too easy. :( Adding or removing any data from the pool still causes it to panic with the dmu_free_range() assertion. -- Freddie Cash fjwc...@gmail.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
