zfs discuss - Sep 2010 - Kernel panic on ZFS import - how do I recover?

I posted this on the www.nexentastor.org forums, but no answer so far, so I
apologize if you are seeing this twice. I am also engaged with nexenta support,
but was hoping to get some additional insights here.

I am running nexenta 3.0.3 community edition, based on 134. The box crashed
yesterday, and goes into a reboot loop (kernel panic) when trying to import my
data pool, screenshot attached. What I have tried thus far:

Boot off of DVD, both 3.0.3 and 3.0.4 beta 8. ''zpool import -f
data01'' causes the panic in both cases.
Boot off of 3.0.4 beta 8, ran zpool import -fF data01
That gives me a message like "Pool data01 returned to its stat as of
...", and then panics.

The import -fF does seem to import the pool, but then immediately panic. So
after booting off of DVD, I can boot from my hard disks, and the system will not
import the pool because it was last imported from another system.

I have moved /etc/zfs/zfs.cache out of the way, but no luck after a reboot and
import.

zpool import shows all of my disks are OK, and the pool itself is online.

Is it time to start working with zdb? Any suggestions?

This box is hosting development VMs, so I have some people idling their thumbs
at the moment.

Thanks everyone,

-Scott
-- 
This message posted from opensolaris.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen shot 2010-09-23 at 5.47.25 PM.png
Type: application/octet-stream
Size: 77386 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100923/15d64ee6/attachment-0001.obj>

Have you tried setting zfs_recover & aok in /etc/system or setting it 
with the mdb?

Read how to set via /etc/system
http://opensolaris.org/jive/thread.jspa?threadID=114906

mdb debugger
http://www.listware.net/201009/opensolaris-zfs/46706-re-zfs-discuss-how-to-set-zfszfsrecover1-and-aok1-in-grub-at-startup.html

After you get the variables set and system booted, try importing, then 
running a scrub.

Dave

On 09/23/10 19:48, Scott Meilicke wrote:
> I posted this on the www.nexentastor.org forums, but no answer so far, so I
apologize if you are seeing this twice. I am also engaged with nexenta support,
but was hoping to get some additional insights here.
>
> I am running nexenta 3.0.3 community edition, based on 134. The box crashed
yesterday, and goes into a reboot loop (kernel panic) when trying to import my
data pool, screenshot attached. What I have tried thus far:
>
> Boot off of DVD, both 3.0.3 and 3.0.4 beta 8. ''zpool import -f
data01'' causes the panic in both cases.
> Boot off of 3.0.4 beta 8, ran zpool import -fF data01
> That gives me a message like "Pool data01 returned to its stat as of
...", and then panics.
>
> The import -fF does seem to import the pool, but then immediately panic. So
after booting off of DVD, I can boot from my hard disks, and the system will not
import the pool because it was last imported from another system.
>
> I have moved /etc/zfs/zfs.cache out of the way, but no luck after a reboot
and import.
>
> zpool import shows all of my disks are OK, and the pool itself is online.
>
> Is it time to start working with zdb? Any suggestions?
>
> This box is hosting development VMs, so I have some people idling their
thumbs at the moment.
>
> Thanks everyone,
>
> -Scott
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>   

-- 


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100923/fecb5ddd/attachment.html>

Brilliant. I set those parameters via /etc/system, rebooted, and the pool
imported with just the ?f switch. I had seen this as an option earlier,
although not that thread, but was not sure it applied to my case.

Scrub is running now. Thank you very much!

-Scott


On 9/23/10 7:07 PM, "David Blasingame Oracle" <david.blasingame at
oracle.com>
wrote:
> Have you tried setting zfs_recover & aok in /etc/system or setting it
with the
> mdb?
> 
> Read how to set via /etc/system
> http://opensolaris.org/jive/thread.jspa?threadID=114906
> 
> mdb debugger
>
http://www.listware.net/201009/opensolaris-zfs/46706-re-zfs-discuss-how-to-set
> -zfszfsrecover1-and-aok1-in-grub-at-startup.html
> 
> After you get the variables set and system booted, try importing, then
running
> a scrub. 
> 
> Dave
> 
> On 09/23/10 19:48, Scott Meilicke wrote:
>>  
>> I posted this on the www.nexentastor.org
<http://www.nexentastor.org>
>> forums, but no answer so far, so I apologize if you are seeing this
twice. I
>> am also engaged with nexenta support, but was hoping to get some
additional
>> insights here. 
>> 
>> I am running nexenta 3.0.3 community edition, based on 134. The box
crashed
>> yesterday, and goes into a reboot loop (kernel panic) when trying to
import
>> my data pool, screenshot attached. What I have tried thus far:
>> 
>> Boot off of DVD, both 3.0.3 and 3.0.4 beta 8. ''zpool import -f
data01'' causes
>> the panic in both cases.
>> Boot off of 3.0.4 beta 8, ran zpool import -fF data01
>> That gives me a message like "Pool data01 returned to its stat as
of ...",
>> and then panics.
>> 
>> The import -fF does seem to import the pool, but then immediately
panic. So
>> after booting off of DVD, I can boot from my hard disks, and the system
will
>> not import the pool because it was last imported from another system.
>> 
>> I have moved /etc/zfs/zfs.cache out of the way, but no luck after a
reboot
>> and import.
>> 
>> zpool import shows all of my disks are OK, and the pool itself is
online.
>> 
>> Is it time to start working with zdb? Any suggestions?
>> 
>> This box is hosting development VMs, so I have some people idling their
>> thumbs at the moment.
>> 
>> Thanks everyone,
>> 
>> -Scott
>>   
>>  
>> 
>> 
>> 
>> _______________________________________________
>> zfs-discuss mailing list
>> zfs-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>   
> 

--------------------------------------------------------------------------------
We value your opinion!  How may we serve you better? 
Please click the survey link to tell us how we are doing:
http://www.craneae.com/ContactUs/VoiceofCustomer.aspx
Your feedback is of the utmost importance to us. Thank you for your time.
--------------------------------------------------------------------------------
Crane Aerospace & Electronics Confidentiality Statement:
The information contained in this email message may be privileged and is 
confidential information intended only for the use of the recipient, or any 
employee or agent responsible to deliver it to the intended recipient. Any 
unauthorized use, distribution or copying of this information is strictly
prohibited
and may be unlawful. If you have received this communication in error, please
notify
the sender immediately and destroy the original message and all attachments from
your electronic files.
--------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100923/973fac22/attachment-0001.html>

I just realized that the email I sent to David and the list did not make the
list (at least as jive can see it), so here is what I sent on the 23rd:

Brilliant. I set those parameters via /etc/system, rebooted, and the pool
imported with just the ?f switch. I had seen this as an option earlier, although
not that thread, but was not sure it applied to my case.

Scrub is running now. Thank you very much! 

-Scott

Update: The scrub finished with zero errors.
-- 
This message posted from opensolaris.org