> ZFS documentation lists snapshot limits on any single file system in a
> pool at 2**48 snaps, and that seems to logically imply that a snap on
> a file system does not require an update to the poolâs
> currently active uberblock.
All commited changes (including snapshot creation) require a new
ZFS documentation lists snapshot limits on any single file system in a pool at
2**48 snaps, and that seems to logically imply that a snap on a file system
does not require an update to the pool’s currently active uberblock. That is
to say, that if we take a snapshot of a file system in a pool,