So to start out with, I'm going to write everything here explicitly in TiB so I don't confuse myself.
I have 24 ~3.64TiB drives, in a RaidZ3 array. This in total is ~87.3TiB of space, before parity drives (and confirmed by zpool list). Minus parity drives, that puts us at around 76.4 TiB or so. TrueNAS itself, when creating the vdev, estimates about 76.37TiB. So that's all fine and good.
But when when I actually create the array, it shows up with ~67.5TiB available.
So presumably that space is being eaten up by space for checksums and what not.... but what exactly? I feel like this is something I should have come across while researching, and I still haven't found anything immediately obvious.
I have 24 ~3.64TiB drives, in a RaidZ3 array. This in total is ~87.3TiB of space, before parity drives (and confirmed by zpool list). Minus parity drives, that puts us at around 76.4 TiB or so. TrueNAS itself, when creating the vdev, estimates about 76.37TiB. So that's all fine and good.
But when when I actually create the array, it shows up with ~67.5TiB available.
So presumably that space is being eaten up by space for checksums and what not.... but what exactly? I feel like this is something I should have come across while researching, and I still haven't found anything immediately obvious.