Hi,
I have problem with Solaris 10. I know that this forum is for OpenSolaris but
may be someone will have an idea.
My box is crashing on any attempt to import zfs pool. First crash happened on
export operation and since then I cannot import pool anymore due to kernel
panics. Is there any way o
> Your pools have no redundancy...
Box is connected to two fabric switches via different HBAs, storage is RAID5,
MPxIP is ON, and all after that my pools have no redundancy?!?!
> ...and got corrupted, therefore there is nothing ZFS
This is exactly what I would like to know. HOW this could happen
> I would recommend you to make multiple LUNs visible
> to ZFS, and create
So, you are saying that ZFS will cope better with failures then any other
storage system, right? I'm just trying to imagine...
I've got, lets say, 10 disks in the storage. They are currently in RAID5
configuration and giv
> Try to change uberblock
> http://www.opensolaris.org/jive/thread.jspa?messageID=
> 217097
Looks like you are the originator of that thread. In the last message you
promised to post some details on how you've recovered, but it was not done. Can
you please post some details? How did you figure ou
>Suppose that ZFS detects an error in the first
> case. It can't tell
> the storage array "something's wrong, please
> fix it" (since the
> storage array doesn't provide for this with
> checksums and intelligent
> recovery), so all it can do is tell the user
> "this file is corrupt,
> recover it f
> Ask your hardware vendor. The hardware corrupted your
> data, not ZFS.
Right, that's all because of these storage vendors. All problems come from
them! Never from ZFS :-) I have similar answer from them: ask Sun, ZFS is
buggy. Our storage is always fine. That is really ridiculous! People pay hu
> From what I can predict, and *nobody* has provided
> any panic
> essages to confirm, ZFS likely had difficulty
> writing. For Solaris 10u5
Panic stack is looking pretty much the same as panic on imprt, and cannot be
correlated to write failure:
Aug 5 12:01:27 omases11 unix: [ID 836849 kern.no
> As a follow up to the whole story, with the fantastic
> help of Victor,
> the failed pool is now imported and functional thanks
> to the redundancy
> in the meta data.
It would be really useful if you could publish the steps to recover the pools.
This message posted from opensolaris.org
_
A little update on the subject.
After great help of Victor Latushkin the content of the pools is recovered.
The cause of the problem is still under investigation, but what is clear that
both config objects where corrupted.
What has been done to recover data:
Victor has a zfs module which allows
