The solution here was to upgrade to snv_78. By upgrade I mean
re-jumpstart the system.
I tested snv_67 via net-boot but the pool paniced just as below. I also
attempted using zfs_recover without success.
I then tested snv_78 via net-boot, used both aok=1 and
zfs:zfs_recover=1 and was able
Your system seems to have hit the BUG 6458218 :
http://bugs.opensolaris.org/view_bug.do?bug_id=6458218
It is fixed in snv_60. As far ZFS, snv_43 is quite old.
--
Prabahar.
On Jan 12, 2008, at 11:15 PM, Ben Rockwood wrote:
Today, suddenly, without any apparent reason that I can find, I'm
Hi Ben
Not that I know much, but while monitoring the posts I read sometime long ago
that there was a bug/race condition in slab allocator which results in panic on
double free (ss != NULL).
I think zpool is fine but your system is tripping on this bug. Since it is
snv43, I'd suggest
Most probable culprit (close, but not identical stacktrace):
http://bugs.opensolaris.org/view_bug.do?bug_id=6458218
Fixed since snv60.
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
as its been pointed out it likely 6458218
but a zdb -e poolname
will tell you alittle more
Rob
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Today, suddenly, without any apparent reason that I can find, I'm
getting panic's during zpool import. The system paniced earlier today
and has been suffering since. This is snv_43 on a thumper. Here's the
stack:
panic[cpu0]/thread=99adbac0: assertion failed: ss != NULL, file:
