On Tue, Dec 16, 2008 at 11:39 AM, Ross <myxi...@googlemail.com> wrote:
> I know Eric mentioned the possibility of zpool import doing more of this > kind of thing, and he said that it's current inability to do this will be > fixed, but I don't know if it's an official project, RFE or bug. Can > anybody shed some light on this? > > See Jeff's post on Oct 10, and Eric's follow up later that day in this > thread: > http://opensolaris.org/jive/thread.jspa?messageID=289537񆬁 > -- > > 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? -- 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
