Have you already extracted the core file of the kernel crash ?
(and btw activated dump device for such dumping happen at next reboot...)
Have you also tried applying the latest kernel/zfs patches and try
importing the pool afterwards ?
Thomas
On 08/18/2011 06:40 PM, Stu Whitefish wrote:
Hi Thomas,
Thanks for that link. That's very similar but not identical. There's a
different line number in zfs_ioctl.c, mine and Preston's fail on line 1815. It
could be because of a difference in levels in that module of course, but the
traceback is not identical either. Ours show brand_sysenter and the one you
linked to shows brand_sys_syscall. I don't know what all that means but it is
different. Anyway at least two of us have identical failures.
I was not using crypto, just a plain jane mirror on 2 drives. Possibly I had
compression on a few file systems but everything else was allowed to default.
Here are our screenshots in case anybody doesn't want to go through the thread.
http://imageshack.us/photo/my-images/13/zfsimportfail.jpg/
http://prestonconnors.com/zvol_get_stats.jpg
I hope somebody can help with this. It's not a good feeling having so much data
gone.
Thanks for your help. Oracle, are you listening?
Jim
----- Original Message -----
From: Thomas Gouverneur<t...@ians.be>
To: zfs-discuss@opensolaris.org
Cc: Stu Whitefish<swhitef...@yahoo.com>
Sent: Thursday, August 18, 2011 1:57:29 PM
Subject: Re: [zfs-discuss] Kernel panic on zpool import. 200G of data
inaccessible!
You're probably hitting bug 7056738 ->
http://wesunsolve.net/bugid/id/7056738
Looks like it's not fixed yet @ oracle anyway...
Were you using crypto on your datasets ?
Regards,
Thomas
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss