> From: Per Jorgensen <p...@combox.dk>
> Date: Fri, 06 Aug 2010 04:29:08 PDT
> To: <zfs-discuss@opensolaris.org>
> Subject: [zfs-discuss] Disk space on Raidz1 configuration
>
> I have 7 * 1,5TB disk in a raidz1 configuration, then the system (how i
> understanding it) uses 1,5TB ( 1 disk ) for parity, but when i uses "df" the
> available space in my newly created pool it says
>
> Filesystem Size Used Avail Use% Mounted on
> bf 8.0T 36K 8.0T 1% /bf
>
> when I uses zpool list it says
>
> NAME SIZE USED AVAIL CAP HEALTH ALTROOT
> bf 9.50T 292K 9.50T 0% ONLINE -
>
> the pool is created with the following command, and compression is set to off
>
> zpool create -f bf raidz1 c9t0d0 c9t1d0 c9t2d0 c9t3d0 c9t4d0 c9t5d0 c9t6d0
>
> and when I do some calculation
>
> 7 x 1,5TB = 10,5TB - 1,5TB for parity = 9,5 TB , so to my questions
>
> 1. why do I only have 8TB in my bf pool ?
> 2. why do "zpool list" and "df" reports diffrents disk space avaibable
You only have 8 TB in your pool because your drives are 1.5 TB using 1000 *
1000 as a MB. Df uses 1024*1024 as a MB.
Zpool list shows raw pool space, not usable space. RAIDZ1 takes the space
for one disk out to store error checking data so that is not "usable" space.
--
Terry Hull
Network Resource Group, Inc.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
