AW: AW: AW: AW: ZFS: Corrupted pool metadata after adding vdev to a pool - no opportunity to rescue data from healthy vdevs? Remove a vdev? Rewrite metadata?

Volodymyr Kostyrko c.kworr at gmail.com
Sun Sep 16 09:33:19 UTC 2012


15.09.2012 22:25, Thomas Göllner (Newsletter) wrote:
>>>>> I also think there is no way to write new or edit the lables of the discs?
>>>>
>>>> This idea is called Block Pointer Rewrite and is not implemented yet. I have found no code to do that.
>>>
>>> I thought it may come to this -.- Because during my last reading I had to learn, that I have to find the "root block pointer" to recover the maybe overwritten labels... As it changes place and content with each copy on write process (each txg?) it will be a search for the needle in the haystack...
>>
>> Not at all, what are you referring to is MOS and the one is contained in each UberBlock.
>
> So as this thing is so far beyond my skills, I am sad to point out that I have to give up here. Without someone who will take me by the hand and say what to do step by step I think recovering/rewriting the right labels of my discs is something I will not be able to do within one year or so. It's a pity that ZFS still has no tools for recovering metadata built in. This would be a task to think of in future.
>
> Thanks again for your help Volodymyr. It is a bit of consolation that at least I know now that I have done everything I could.

If you can afford putting your drives aside you can try to wait before 
some tool occasionally emerges. I will not promise anything but I'm 
slowly making some progress with my script. I'm motivated about that as 
I have broken pool with photos. Trying to import that pool is causing a 
core dump on any system I tested like OpenSolaris, Illumos or 
SystemRescueCD.

-- 
Sphinx of black quartz judge my vow.


More information about the freebsd-fs mailing list