我有一个ZFS服务器8个zpools。 每个池都是10 + 2 RAIDZconfiguration中的12个6TB磁盘。 因此，每个池的原始存储空间为12 * 6 = 72 TB，可用空间为10 * 6 = 60 TB。 但是，当我使用zfs list与使用zpool list来查询它时，我看到了不同的结果，如下所示：
# zfs list NAME USED AVAIL REFER MOUNTPOINT intp1 631K 48.0T 219K /intp1 intp2 631K 48.0T 219K /intp2 intp3 631K 48.0T 219K /intp3 jbodp4 631K 48.0T 219K /jbodp4 # zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT intp1 65T 1.02M 65.0T - 0% 0% 1.00x ONLINE - intp2 65T 1020K 65.0T - 0% 0% 1.00x ONLINE - intp3 65T 1.02M 65.0T - 0% 0% 1.00x ONLINE - jbodp4 65T 1.02M 65.0T - 0% 0% 1.00x ONLINE -
有人能帮我理解为什么这种差异？
我很惊讶你有这么大的设置。 你有没有build立这个arrays？ 由于游泳池devise，这可能是一个糟糕的性能安排。
无论哪种方式， zpool手册页解释了这一点。 zfs list将显示您的可用空间。 zpool列表显示奇偶空间作为存储空间。
used Amount of storage space used within the pool. The space usage properties report actual physical space available to the storage pool. The physical space can be different from the total amount of space that any contained datasets can actually use. The amount of space used in a raidz configuration depends on the characteristics of the data being written. In addition, ZFS reserves some space for internal accounting that the zfs(8) command takes into account, but the zpool command does not. For non-full pools of a reasonable size, these effects should be invisible. For small pools, or pools that are close to being completely full, these dis- crepancies may become more noticeable.