Sorry a few corrections, and inserts..
>
> which is not the behavior I am seeing.. 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). 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
s/during/purging/
> usage to snaps it makes this impossible (without blindly deleting snaps,
> waiting an unspecified period until zfs list is updated and repeat). Is
> this really the behavior that is expected, am I missing some more
specific
> usage data, or is this some sort of bug?
>
> Also another thing that is not really specified in the documentation is
> where this delta space usage would be listed -- what makes sense to me
> would be to have the oldest snap that owns the blocks take the usage hit
> for them and move the usage hit up to the next snap as the oldest is
> deleted.
I guess the more I think about it the more it makes sence to show usage
charges on the newest snap that references the blocks as delta -- this way
you show the most specific snap that is reserving the space (which snap
you need to delete all snaps before and including to free said space).
> > WSfc> Hola folks,
> >
> > WSfc> I am new to the list, please redirect me if I am posting
> > to the wrong
> > WSfc> location. I am starting to use ZFS in production (Solaris x86
10U3
> --
> > WSfc> 11/06) and I seem to be seeing unexpected behavior for zfs list
and
> > WSfc> snapshots. I create a filesystem (lets call it a/b where a isthe
> pool).
> > WSfc> Now, if I store 100 gb of files on a/b and then snapshot a/[EMAIL
> > PROTECTED]
> then
> > WSfc> delete about 50 gb of files from a/b -- I expect to see ~50
> gb"USED" on
> > WSfc> both a/b and a/[EMAIL PROTECTED] via zfs list output -- instead I only
> > seem to see the
> > WSfc> delta block adds as "USED" (~20mb) on a/[EMAIL PROTECTED] Is this
> > correct behavior?
> > WSfc> how do you track the total delta blocks the snap is using vs
other
> snaps
> > WSfc> and live fs?
> >
> > This is almost[1] ok. When you delete a file from a file system you
> > definitely expect to see that the file system allocated space reduced
> > by about the same size.
> >
> > [1] the problem is that space consumed by snapshot isn't entirely
> > correct and once you delete snapshot you'll actually get some more
> > space than zfs list reported for that snapshot as used space. It's not
> > a big deal but still it makes it harder to determine exactly how much
> > space is allocated for snapshots for a given file system.
> >
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
