Where is the link to the script, and does it work with RAIDZ arrays? Thanks so
much.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
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
Hi Fred,
Have you read the ZFS On Disk Format Specification paper
at:
http://hub.opensolaris.org/bin/download/Community+Group+zfs/docs/ondiskformat0822.pdf?
Ifred pam wrote:
Hi Richard, thanks for your time, I really appreciate it, but I'm still unclear
on how this works.
So uberblocks
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
On Apr 15, 2010, at 12:39 PM, fred pam wrote:
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.
uberblocks are the trunk of the tree.
If I'm incorrect in thinking that I
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
On Apr 14, 2010, at 5:13 AM, fred pam wrote:
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...)
I have written an python script that enables to get back already deleted files
and pools/partitions. This is highly experimental, but I managed to get back a
moths work when all the partitions were deleted by accident(and of course
backups are for the weak ;-)
I hope someone can pass this
I forgot to add the script
--
This message posted from opensolaris.org
zfs_revert.py
Description: Binary data
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
The links work fine if you take the * off from the end...sorry bout that
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I have no idea why this forum just makes files dissapear??? I will put a link
tomorrow...a file was attached before...
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
12 matches
Mail list logo
