> Recreation of the active uberblock would occur, for example, if we > took a snapshot of the pool and changes were then made anywhere in the > pool.
The uberblock is updated quite often, not just on snapshots. > Since a new uberblock is required in this snapshot scenario, > and since it appears that the uberblocks are treated as a kind of > circular list across vdevs, it seems to me that the number of > available snapshots we could have of a pool at any given instant would > be strictly limited to the number of available uberblocks in the vdevs > of the pool (128 uberblocks per vdev, if I have that straight). Is > this truly the case or am I missing something here ? Are you talking about normal ZFS filesystem snapshots or something else? The new uberblock will point to all filesystem snapshots. The old copies would never normally be referenced. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
