Date: Mon, 22 Jun 2009 21:28:26 -0700 From: Artem Belevich <fbsdlist@src.cx> To: xorquewasp@googlemail.com Cc: freebsd-hackers@freebsd.org Subject: Re: ZFS filesystem not showing total size? Message-ID: <ed91d4a80906222128y6098bdafk67d67758a36691ec@mail.gmail.com> In-Reply-To: <20090623003117.GA94466@logik.internal.network> References: <20090623003117.GA94466@logik.internal.network>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 22, 2009 at 5:31 PM, <xorquewasp@googlemail.com> wrote: > ad11: 953869MB <WDC WD1001FALS-00J7B1 05.00K05> at ata5-slave SATA300 .. > ad14: 476940MB <WDC WD5001AALS-00L3B2 01.03B01> at ata7-master SATA300 > ad16: 476940MB <WDC WD5001AALS-00L3B2 01.03B01> at ata8-master SATA300 .. ># zpool create storage raidz ad11 ad14 ad16 > I seem to have less storage than I'd expect. Is there something wrong > with this setup? You've created raidz pool from 2x500G hard drives and one 1T hard drive. RAIDZ needs elements of the array to be of the same size, so you're effectively wasting half of your 1T drive (ad11). Total raw capacity of the pool is 476G*3 = ~ 1.36T with 2/3of it (913G) usable for user data -- exactly what zfs shows you. Obvious fix would be to build the pool from the drives of the same size. You may try concatenating or striping ad14+ad16 with geom and create mirrored pool with ad11 -- usable size would be a bit larger than what you have. Resulting pool should be faster than RAIDZ. Another option would be to get another 1T drive and build RAIDZ pool with 2x1T + (striped 2x500G) for a total usable size of ~2T. I'd advise against splitting 1T drive into two partitions and use them as two elements of RAIDZ pool -- this would effectively kill redundancy that RAIDZ is supposed to provide. If your 1T drive dies, your whole pool would go down with it. Performance would also suck as 1T drive will be constantly seeking. --Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ed91d4a80906222128y6098bdafk67d67758a36691ec>