|Mark Schouten||Apr 13, 2012 5:20 am|
|Volodymyr Kostyrko||Apr 13, 2012 6:10 am|
|Mark Schouten||Apr 13, 2012 6:28 am|
|Peter Maloney||Apr 13, 2012 6:32 am|
|Johannes Totz||Apr 13, 2012 8:26 am|
|Tom Evans||Apr 13, 2012 8:44 am|
|Freddie Cash||Apr 13, 2012 8:45 am|
|Freddie Cash||Apr 13, 2012 8:49 am|
|Volodymyr Kostyrko||Apr 13, 2012 9:32 am|
|Ronald Klop||Apr 15, 2012 4:14 am|
|Mark Schouten||Apr 16, 2012 1:35 am|
|Volodymyr Kostyrko||Apr 16, 2012 11:32 pm|
|Mark Schouten||Apr 17, 2012 1:37 am|
|Volodymyr Kostyrko||Apr 17, 2012 2:54 am|
|Mark Schouten||Apr 17, 2012 3:02 am|
|Volodymyr Kostyrko||Apr 17, 2012 3:10 am|
|Mark Schouten||Apr 17, 2012 3:22 am|
|Mark Schouten||May 3, 2012 2:28 am|
|Subject:||Re: ZFS and disk usage|
|From:||Freddie Cash (fjwc...@gmail.com)|
|Date:||Apr 13, 2012 8:49:17 am|
On Fri, Apr 13, 2012 at 8:45 AM, Freddie Cash <fjwc...@gmail.com> wrote:
On Fri, Apr 13, 2012 at 8:27 AM, Johannes Totz <joha...@jo-t.de> wrote:
Without checking the numbers myself... Note that zpool and zfs do not agree on (free) space accounting: zpool shows "raw" space, whereas zfs includes metadata overhead for itself.
Small rant: I dont understand why zpool and zfs show different things. If you have an integrated storage stack then why not show consistent numbers? Is there any use for this extra (mis-)information that zpool-vs-zfs provides?
There's a great posting about the differences in the zfs-discuss mailing list archives, although I can't find a reference to it at the moment. Going from memory, the breakdown is something like:
Here's one of them: http://mail.opensolaris.org/pipermail/zfs-discuss/2010-April/040180.html
Message details: On Sun, Apr 18, 2010 at 20:08, Harry Putnam <reader at newsguy.com> wrote:
Seems like you can get some pretty large discrepancies in sizes of pools. and directories.
They all answer different things, sure, but they're all things that an administrator might want to know.
"How many bytes are in use on the storage device? How many unallocated bytes are there?"
"If I have to ship this filesystem to another box (uncompressed and not deduped) how many bytes is that?"
"How many bytes are used to store the contents of the files in this directory?"
and "ls -l": "How many bytes are addressable in this file?"
Do no other administrators feel the need to know accurate sizes?
It's important to consider what you want this data for. Considering upgrading your storage to get more room? Check out "zpool list". Need to know whether accounting or engineering is using more space? Look at "zfs list". Looking at a sparse or compressed file, and want to know how many bytes are allocated to it? "du" does the trick. Planning to email someone a file, and want to know if it'll fit in their 10MB quota? "ls -l" is the relevant command.
In short, there are many commands because there are many answers, and many questions. No single tool has all the information available to it.
-- Freddie Cash fjwc...@gmail.com
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "free...@freebsd.org"