2012-09-26 2:52, Richard Elling wrote:
I am not sure if there is a simple way to get exact
byte-counts instead of roundings like "422M"...
zfs get -p
-- richard
Thanks to all who corrected me, never too old to learn ;)
# zfs get referenced rpool/export/home
NAME PROPERTY
On Sep 25, 2012, at 1:46 PM, Jim Klimov wrote:
> 2012-09-24 21:08, Jason Usher wrote:
>>> Ok, thank you. The problem with this is, the
>>> compressratio only goes to two significant digits, which
>>> means if I do the math, I'm only getting an
>>> approximation. Since we may use these numbers
2012-09-24 21:08, Jason Usher wrote:
Ok, thank you. The problem with this is, the
compressratio only goes to two significant digits, which
means if I do the math, I'm only getting an
approximation. Since we may use these numbers to
compute billing, it is important to get it right.
Is there any
On Sep 25, 2012, at 11:17 AM, Jason Usher wrote:
>
> Ok - but from a performance point of view, I am only using
> ram/cpu resources for the deduping of just the individual
> filesystems I enabled dedupe on, right ? I hope that
> turning on dedupe for just one filesystem did not incur
> ram/cpu c
--- On Tue, 9/25/12, Volker A. Brandt wrote:
> Well, he is telling you to run the dtrace program as root in
> one
> window, and run the "zfs get all" command on a dataset in
> your pool
> in another window, to trigger the dataset_stats variable to
> be filled.
>
> > none can hide from dtrace
> I'm hoping the answer is yes - I've been looking but do not see it
> ...
Well, he is telling you to run the dtrace program as root in one
window, and run the "zfs get all" command on a dataset in your pool
in another window, to trigger the dataset_stats variable to be filled.
> none can hide f
--- On Mon, 9/24/12, Richard Elling wrote:
I'm hoping the answer is yes - I've been looking but do not see it ...
none can hide from dtrace!# dtrace -qn 'dsl_dataset_stats:entry {this->ds =
(dsl_dataset_t *)arg0;printf("%s\tcompressed size = %d\tuncompressed
size=%d\n", this->ds->ds_dir->dd_m
On Sep 24, 2012, at 10:08 AM, Jason Usher wrote:
> Oh, and one other thing ...
>
>
> --- On Fri, 9/21/12, Jason Usher wrote:
>
>>> It shows the allocated number of bytes used by the
>>> filesystem, i.e.
>>> after compression. To get the uncompressed size,
>> multiply
>>> "used" by
>>> "compre
Oh, and one other thing ...
--- On Fri, 9/21/12, Jason Usher wrote:
> > It shows the allocated number of bytes used by the
> > filesystem, i.e.
> > after compression. To get the uncompressed size,
> multiply
> > "used" by
> > "compressratio" (so for example if used=65G and
> > compressratio=2.
--- On Fri, 9/21/12, Sašo Kiselkov wrote:
> > I have a ZFS filesystem with compression turned
> on. Does the "used" property show me the actual data
> size, or the compressed data size ? If it shows me the
> compressed size, where can I see the actual data size ?
>
> It shows the allocated n
On 09/21/2012 01:34 AM, Jason Usher wrote:
> Hi,
>
> I have a ZFS filesystem with compression turned on. Does the "used" property
> show me the actual data size, or the compressed data size ? If it shows me
> the compressed size, where can I see the actual data size ?
It shows the allocated n
11 matches
Mail list logo
