Date: Sat, 29 Sep 2012 16:37:42 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Jason Usher <jusher71@yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS stats output - used, compressed, deduped, etc. Message-ID: <20120929143742.GH1402@garage.freebsd.pl> In-Reply-To: <1348155984.52722.YahooMailClassic@web121204.mail.ne1.yahoo.com> References: <1348155984.52722.YahooMailClassic@web121204.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--GACvPnKyN03uhzyl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 20, 2012 at 08:46:24AM -0700, Jason Usher wrote: > Hi, >=20 > I have a ZFS filesystem with compression turned on. Does the "used" prop= erty show me the actual data size, or the compressed data size ? If it sho= ws me the compressed size, where can I see the actual data size ? To calculate uncompressed data size you multiple 'used' property by 'compressratio' property. > I also wonder about checking status of dedupe - I created my pool without= dedupe, and continue to NOT enable dedupe - from zpool history, we see: >=20 > zpool create -f -O atime=3Doff -O setuid=3Doff -O exec=3Doff -m /mnt/pool= pool raidz3 da0 da1 da2 da3 da4 da5 da6 da7 da8 da9 da10 da11 >=20 > Later, I enabled dedup for just a single filesystem on this pool: >=20 > zfs set dedup=3Don pool/dataset >=20 > and now, I see in 'zpool list' a value for dedupratio: >=20 > pool dedupratio 1.65x - >=20 >=20 > Why do I see a value here ? Isn't dedupe still OFF for the pool as a who= le ? I do NOT want to enable dedupe for the entire pool. >=20 > Also, why do I not see any dedupe stats for the individual filesystem ? = I see compressratio, and I see dedup=3Don, but I don't see any dedupratio f= or the filesystem itself... >=20 > Did turning on dedupe for a single filesystem turn it on for the entire p= ool ? Deduplication is pool-wide property that you enable for each individual file system. The idea here is to share deduped data across separate file systems. Note that only file systems that you enabled dedup for will actually participate in dedup. File systems that have dedup=3Doff won't go through the dedup. Dedup works while you write to file system. Block's checksum is being calculated and search for in dedup table. If we find a match, reference count is bumped and no additional data is written to the pool. This path is skipped for file systems that don't have dedup enabled. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --GACvPnKyN03uhzyl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBnB7UACgkQForvXbEpPzTtiACfWfp9d6CF39EFnyh6rytLf50x BO0AoMkjP5CK/S617zv3++MbQFe4RYhC =RIkf -----END PGP SIGNATURE----- --GACvPnKyN03uhzyl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120929143742.GH1402>