Hi Max,
Thanks, that's what I was looking for.
So, after reading it I come to the conclusion that it's actually the fact I've
lost my MOS that makes it 'impossible' to retrieve the data.
My understanding of it all (growing yet still meager ;-):
Uberblocks do not point to different MOS-es but
Hi Richard, thanks for your time, I really appreciate it, but I'm still unclear
on how this works.
So uberblocks point to the MOS. Why do you then require multiple uberblocks? Or
are there actually multiple MOS'es?
Or is there one MOS and multiple delta's to it (and its predecessors) and do
th
Hi Richard,
Hm, I guess I misunderstand the function of uberblocks. I thought uberblocks
contained pointers (to...?) which the system then uses to retrieve the files.
If I'm incorrect in thinking that I could use an older uberblock to retrieve
the data, what am I missing?
I've tried to find so
I have a similar problem that differs in a subtle way. I moved a zpool (single
disk) from one system to another. Due to my inexperience I did not import the
zpool but (doh!) 'zpool create'-ed it (I may also have used a -f somewhere in
there...)
Interestingly the script still gives me the old u
