> Hi There,
>
> Is there any chance you could go into a little more
> detail, perhaps even document the procedure, for the
> benefit of others experiencing a similar problem?
I have some spare time this weekend and will try to give more details.
This message posted from opensolaris.org
___
Hi There,
Is there any chance you could go into a little more detail, perhaps even
document the procedure, for the benefit of others experiencing a similar
problem?
We had a mirrored array, which after a powercut shows the zpool as faulted, and
are keen to find a way to recover the zpool.
Hi Lukas,
I've encountered a problem similar to yours where a zfs pool became
unaccessible after a reboot with the error "The pool metadata is corrupted."
In my case I'm running on Solaris 10 8/07 127112-11. Can you explain how you
determined the offsets for modifying vdev_uberblock_compare,
I managed to recover my data after 3 days fighting.
Few system changes:
- disable ZIL
- enable readonly mode
- disable zil_replay during mount
- change function that chooses uberblock
On snv_78
#mdb -kw
> zil_disable/W 1
zil_disable:0 = 0x1
> spa_mode/W 1
spa_mode:
As described in the 'status' section, ZFS was able to recover from the
error and applications are unaffected. To be sure, can you
'fmdump -e' output? You can also do a 'zpool scrub' and see if that
produces an error.
>From the ZFS perspective, you had one disk return a single failure, but
we we
