On 15 Mar 2010, at 23:03, Tonmaus wrote:
Hi Cindy,
trying to reproduce this
For a RAIDZ pool, the zpool list command identifies
the "inflated" space
for the storage pool, which is the physical available
space without an
accounting for redundancy overhead.
The zfs list command identifies how much actual pool
space is available
to the file systems.
I am lacking 1 TB on my pool:
u...@filemeister:~$ zpool list daten
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
daten 10T 3,71T 6,29T 37% 1.00x ONLINE -
u...@filemeister:~$ zpool status daten
pool: daten
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
daten ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
c10t2d0 ONLINE 0 0 0
c10t3d0 ONLINE 0 0 0
c10t4d0 ONLINE 0 0 0
c10t5d0 ONLINE 0 0 0
c10t6d0 ONLINE 0 0 0
c10t7d0 ONLINE 0 0 0
c10t8d0 ONLINE 0 0 0
c10t9d0 ONLINE 0 0 0
c11t18d0 ONLINE 0 0 0
c11t19d0 ONLINE 0 0 0
c11t20d0 ONLINE 0 0 0
spares
c11t21d0 AVAIL
errors: No known data errors
u...@filemeister:~$ zfs list daten
NAME USED AVAIL REFER MOUNTPOINT
daten 3,01T 4,98T 110M /daten
I am counting 11 disks 1 TB each in a raidz2 pool. This is 11 TB
gross capacity, and 9 TB net. Zpool is however stating 10 TB and zfs
is stating 8TB. The difference between net and gross is correct, but
where is the capacity from the 11th disk going?
Regards,
Tonmaus
This is because 1TB is not 1TB. The 1TB on your disk label means 10^12
bytes, while 1TB in the OS means (2^10)^4 = 1024^4 bytes.
11*(1000**4)/(1024.0**4)
=> 10.0044417195022
So your 11 "disk label" TB are 10 "OS" TB. Fun, isn't it?
Best regards,
Stefan
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
