Did you try a read-only import as well? I THINK it goes like this:

zpool import -o ro -o cachefile=none -F -f badpool

Did you manage to capture any error output? For example, is it an option for 
you to set up a serial console and copy-paste the error text from the serial 
terminal on another machine?

As far as I know there are no other releases of Solaris 11 yet, and since the 
code is now developed behind closed doors (due to be opened after Solaris 11 OS 
public GA release), no other implementations of ZFS match its v31 features. 

In part (another part being licensing) this is why the open community at large 
shunned the S11X release - its ZFS version not yet interoperable (unlike the 
options with OpenIndiana on different kernels and FreeBSD all supporting zpool 
v28, not so sure Linux-FUSE - but maybe it is close too), and you can't look at 
the source code to see what might go wrong, or build a debug version which 
would not kernel-panic.

Speaking of which, you might try to enforce dumping the kernel memory to a 
dedicated volume/slice/partition so as to stacktrace it with the kernel 
debugger. Maybe that would yield something...

//Jim
-- 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to