The time is the creation time of the snapshots.
Yes. That is true.
Thanks.
Fred
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
The size accounted for by the userused@ and groupused@ properties is the
referenced space, which is used as the basis for many other space
accounting values in ZFS (e.g. du / ls -s / stat(2), and the zfs accounting
properties referenced, refquota, refreservation, refcompressratio,
written). It
On Wed, May 2, 2012 at 3:28 PM, Fred Liu fred_...@issi.com wrote:
The size accounted for by the userused@ and groupused@ properties is the
referenced space, which is used as the basis for many other space
accounting values in ZFS (e.g. du / ls -s / stat(2), and the zfs
accounting
properties
What problem are you trying to solve? How would you want referenced or
userused@... to work?
To be more clear: space shared between a clone and its origin is
referenced by both the clone and the origin, so it is charged to both the
clone's and origin's userused@... properties. The additional
2012-05-03 3:07, Fred Liu wrote:
There is no specific problem to resolve. Just want to get sort of accurate
equation between
the raw storage size and the usable storage size although the *meta file*
size is trivial.
If you do mass storage budget, this equation is meaningful.
I don't think
I don't think accurate equations are applicable in this case.
You can have estimates like no more/no less than X based on,
basically, level of redundancy and its overhead. ZFS metadata
overhead can also be smaller or bigger, depending on your data's
typical block size (fixed for zvols at
On Apr 26, 2012, at 12:27 AM, Fred Liu wrote:
zfs 'userused@' properties and 'zfs userspace' command are good enough to
gather usage statistics.
I think I mix that with NetApp. If my memory is correct, we have to set quotas
to get usage statistics under DataOnTAP.
Further, if we can add an
On Apr 29, 2012, at 7:59 PM, Fred Liu wrote:
On Apr 26, 2012, at 12:27 AM, Fred Liu wrote:
“zfs 'userused@' properties” and “'zfs userspace' command” are good enough
to gather usage statistics.
I think I mix that with NetApp. If my memory is correct, we have to set
quotas to get
2012/4/25 Richard Elling richard.ell...@gmail.com:
On Apr 25, 2012, at 8:14 AM, Eric Schrock wrote:
ZFS will always track per-user usage information even in the absence of
quotas. See the the zfs 'userused@' properties and 'zfs userspace' command.
tip: zfs get -H -o value -p
期四, 四月 26, 2012 0:48
To: Eric Schrock
Cc: zfs-discuss@opensolaris.org; develo...@lists.illumos.org
Subject: Re: [zfs-discuss] [developer] Setting default user/group quotas[usage
accounting]?
On Apr 25, 2012, at 8:14 AM, Eric Schrock wrote:
ZFS will always track per-user usage information even
On 2012-04-26 11:27, Fred Liu wrote:
“zfs 'userused@' properties” and “'zfs userspace' command” are good
enough to gather usage statistics.
...
Since no one is focusing on enabling default user/group quota now, the
temporarily remedy could be a script which traverse all the users/groups
in the
2012/4/26 Fred Liu fred_...@issi.com
** **
Currently, dedup/compression is pool-based right now, they don’t have the
granularity on file system or user or group level. There is also a lot of
improving space in this aspect.
Compression is not pool-based, you can control it with the
2012/4/26 Fred Liu fred_...@issi.com
Currently, dedup/compression is pool-based right now, they don't have the
granularity on file system or user or group level. There is also a lot of
improving space in this aspect.
Compression is not pool-based, you can control it with the 'compression'
On 2012-04-26 11:27, Fred Liu wrote:
zfs 'userused@' properties and 'zfs userspace' command are good
enough to gather usage statistics.
...
Since no one is focusing on enabling default user/group quota now, the
temporarily remedy could be a script which traverse all the
users/groups in the
On Apr 26, 2012, at 12:27 AM, Fred Liu wrote:
“zfs 'userused@' properties” and “'zfs userspace' command” are good enough to
gather usage statistics.
I think I mix that with NetApp. If my memory is correct, we have to set
quotas to get usage statistics under DataOnTAP.
Further, if we can
On Apr 24, 2012, at 2:50 PM, Fred Liu wrote:
Yes.
Thanks.
I am not aware of anyone looking into this.
I don't think it is very hard, per se. But such quotas don't fit well with the
notion of many file systems. There might be some restricted use cases
where it makes good sense, but I'm not
Missing an important ‘NOT’:
OK. I see. And I agree such quotas will **NOT** scale well. From users' side,
they always
ask for more space or even no quotas at all. One of the main purposes behind
such quotas
is that we can account usage and get the statistics. Is it possible to do it
ZFS will always track per-user usage information even in the absence of
quotas. See the the zfs 'userused@' properties and 'zfs userspace' command.
- Eric
2012/4/25 Fred Liu fred_...@issi.com
Missing an important ‘NOT’:
OK. I see. And I agree such quotas will **NOT** scale well. From users'
On Apr 25, 2012, at 8:14 AM, Eric Schrock wrote:
ZFS will always track per-user usage information even in the absence of
quotas. See the the zfs 'userused@' properties and 'zfs userspace' command.
tip: zfs get -H -o value -p userused@username filesystem
Yes, and this is the logical size, not
19 matches
Mail list logo
