Hi Matt,
trying to import our corrupted zpool with snv_60 and 'set zfs:zfs_recover=1' in
/etc/system give us:
Apr 3 20:35:56 SERVER141 ^Mpanic[cpu3]/thread=fffec3860f20:
Apr 3 20:35:56 SERVER141 genunix: [ID 603766 kern.notice] assertion failed:
ss-ss_start = start (0x67b800 =
Gino,
I just had a similar experience and was able to import the pool when I
added the readonly option (zpool import -f -o ro )
Ernie
Gino Ruopolo wrote:
Hi Matt,
trying to import our corrupted zpool with snv_60 and 'set zfs:zfs_recover=1' in
/etc/system give us:
Apr 3 20:35:56
I forgot to mention we are using S10U2.
Gino
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Gino Ruopolo wrote:
Hi All,
Last week we had a panic caused by ZFS and then we
had a corrupted
zpool! Today we are doing some test with the same
data, but on a
different server/storage array. While copying the
data ... panic!
And again we had a corrupted zpool!!
This is bug
Any chance these fixes will make it into the normal Solaris RS patches?
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
