Eric Schrock wrote:
On Wed, Jul 19, 2006 at 12:38:01PM +0800, Darren Reed wrote:
Of course this can change (grow) in the future if the ZFS version number
changes?
...
Another possibility is to use the block birth time and some pool-wide
metadata to determine when an upgrade took place, and then decode older
versions appropriately. This avoids the offline data migration, but
adds more complexity elsewhere (and a tax from now and forever whenever
decoding a block pointer).
Can some bits from the block birth time (or elsewhere?) be
sacrificed to represent version or the size of this data?
The size wouldn't be in bytes, but maybe 128byte chunks?
If the bit used for this is currently 0 (as in a reserved bit(s)),
take it to mean 1+n lots of 128?
Darren
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
