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 could use an older uberblock to retrieve > the data, what am I missing? uberblocks point to the meta-object set (MOS) which describes the configuration of the pool and ultimately the datasets and files. What you've done is plant another tree over the previous tree and it is unlikely that the previous tree remains intact. > I've tried to find some basic zpool<->uberblock relation info without much > success (eh... well, Wiki wasn't helpful and I try to avoid reading RFC/IEEE > documents since I still value my sanity ;-) This is a design detail. In practical terms, you clobbered the previous ZFS pool by creating a new one on top of it. -- richard ZFS storage and performance consulting at http://www.RichardElling.com ZFS training on deduplication, NexentaStor, and NAS performance Las Vegas, April 29-30, 2010 http://nexenta-vegas.eventbrite.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
