On Mon, 30 Aug 2010, Jeff Bacon wrote:
All of this would be ok... except THOSE ARE THE ONLY DEVICES THAT WERE PART OF THE POOL. How can it be missing a device that didn't exist?
The device(s) in question are probably the logs you refer to here:
I can't obviously use b134 to import the pool without logs, since that would imply upgrading the pool first, which is hard to do if it's not imported.
The stack trace you show is indicative of a memory corruption that may have gotten out to disk. In other words, ZFS wrote data to ram, ram was corrupted, then the checksum was calculated and the result was written out.
Do you have a core dump from the panic? Also, what kind of DRAM does this system use?
If you're lucky, then there's no corruption and instead it's a stale config that's causing the problem. Try removing /etc/zfs/zpool.cache and then doing an zpool import -a
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
