Quantcast
Channel: ZFS, raidz1: Why is the volume size (42T) so much smaller than the pool size (50T)? - Server Fault
Browsing all 4 articles
Browse latest View live

Answer by Shane Madden for ZFS, raidz1: Why is the volume size (42T) so much...

To clarify the discrepancy in output between the commands: The zpool command counts the disks that are being used for redundancy as space, while the zfs command does not; thus, the 50.5 TB number is...

View Article



Answer by Chris S for ZFS, raidz1: Why is the volume size (42T) so much...

Hard drive manufactures measure disk size in Base 10. Computers measure bytes in Base 2. It should say 42 TiB to clarify the SI use of the tera- prefix.

View Article

Answer by adaptr for ZFS, raidz1: Why is the volume size (42T) so much...

A 2TB disk is not 2 TiBi in size - it's only 2*10^12 / 2^30 ~ 1862 GiBi. 4 arrays of 6 effective disks each would be 24 * 1862 = 44703 GiBI, or 43.6 TiBi of real, usable storage. I reckon it has some...

View Article

ZFS, raidz1: Why is the volume size (42T) so much smaller than the pool size...

I have a pool of 28 2TB-disks (56T) in 4 arrays of 7 disks. Since it's raidz1 (~RAID5), I'd expect 1 disk to be used for parity in each array, so the resulting volume should be 2TB*4*(7-1)=48TB,...

View Article
Browsing all 4 articles
Browse latest View live




Latest Images