[EMAIL PROTECTED] wrote:
which is not the behavior I am seeing..
Show me the output, and I can try to explain what you are seeing.
AFAIK, the manpage is accurate. The space "used" by a snapshot is exactly
the amount of space that will be freed up when you run 'zfs destroy
<snapshot>'. Once that operation completes, 'zfs list' will show that the
space "used" by adjacent snapshots has changed as a result.
Unfortunately, at this time there is no way to answer the question "how
much space would be freed up if I were to delete these N snapshots". We
have some ideas on how to express this, but it will probably be some time
before we are able to implement it.
If I have 100 snaps of a
filesystem that are relatively low delta churn and then delete half of the
data out there I would expect to see that space go up in the used column
for one of the snaps (in my tests cases I am deleting 50gb out of 100gb
filesystem and showing no usage increase on any of the snaps).
That's probably because the 50GB that you deleted from the fs is shared
among the snapshots, so it is still the case that deleting any one snapshot
will not free up much space.
I am
planning on having many many snaps on our filesystems and programmatically
during old snaps as space is needed -- when zfs list does not attach delta
usage to snaps it makes this impossible (without blindly deleting snaps,
waiting an unspecified period until zfs list is updated and repeat).
As I mentioned, you need only wait until 'zfs destroy' finishes to see the
updated accounting from 'zfs list'.
Also another thing that is not really specified in the documentation is
where this delta space usage would be listed
What do you mean by "delta space usage"? AFAIK, ZFS does not use that term
anywhere, which is why it is not documented :-)
--matt
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
