On Sun, Apr 18, 2010 at 20:08, Harry Putnam <rea...@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.
> zpool list "How many bytes are in use on the storage device? How many unallocated bytes are there?" > zfs list "If I have to ship this filesystem to another box (uncompressed and not deduped) how many bytes is that?" > du "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. Will _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
