> On Nov 16, 2016, at 3:44 AM, Len Weincier <[email protected]> wrote: > > It does not make sense to me then how compression increases capacity as the > pool seems to be showing a lot of free space compared to the file system ? >
Those commands show two different metrics, and they're both right. If you're interested in space available vs. in use, "zfs list" on a dataset that doesn't have a quota set on it (zones is fine) will tell you that and be close to "df" output. Note that "used" includes the sum of the children too; no doubt you have almost all of your 6.93T of space being used in children of zones, not in zones itself. I am almost positive that "zfs list" shows actual space committed on the media, not what it expands to, which is to say that du(1) may give you a different number if compression is enabled and you have crunchy data. Someone please correct me if I've got it wrong here. If you're interested in the total space allocated and available across your zpool, without taking into account space used for parity (you're using two drives for parity since you set up raidz2), then "zpool list" will give you the info that you're looking for. Does this help? -r ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
