On Tue, Dec 16, 2008 at 1:43 PM, <casper....@sun.com> wrote: > > > >When current uber-block A is detected to point to a corrupted on-disk > data, > >how would "zpool import" (or any other tool for that matter) quickly and > >safely know that, once it found an older uber-block "B" that it points to > a > >set of blocks which does not include any blocks that has since been freed > >and re-allocated and, thus, corrupted? Eg, without scanning the entire > >on-disk structure? > > Without a scrub, you mean? > > Not possible, except the first few uberblocks (blocks aren't used until a > few uberblocks later) > > Casper >
Does that mean that each of the last "few-minus-1" uberblocks point to a consistent version of the file system? Does "few" have a definition? -- Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke My blog: http://initialprogramload.blogspot.com
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
