Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Feb 2008 21:55:37 +0100 (CET)
From:      Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>
To:        Mel <fbsd.questions@rachie.is-a-geek.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Looking for a Text on ZFS
Message-ID:  <20080202215029.X4066@wojtek.tensor.gdynia.pl>
In-Reply-To: <200802022111.21862.fbsd.questions@rachie.is-a-geek.net>
References:  <fo2f26$1l2q$1@nermal.rz1.convenimus.net> <200802022111.21862.fbsd.questions@rachie.is-a-geek.net>

next in thread | previous in thread | raw e-mail | index | archive | help
> If you review the "Not done" items @ http://wiki.freebsd.org/ZFS and still are
> doubting, then http://www.opensolaris.org/os/community/zfs/whatis/ describes
> what the features *can* be. I got a good impression from that text what the
> advantages are, but I'm too conservative to migrate myself. YMMV.
very good.

"CAN be" isn't very useful. while ZFS provide "virtual partitions" (which 
may LOOK good), it doesn't work well with 2 or more pools created out of 
partitions not full drives.

my common config on machines with >1 drive is to make gmirror (or 
gmirror+gstripe) from first partitions of each drive, to store most common 
data, usually EXCEPT huge files, and gconcat from other partitions to 
store mostly big files, other rarely used things, copies of other things 
etc.

then drives seeks mostly within first partition so it's much faster, and i 
have unmirrored larger space on second.

with ZFS it is not possible, while it CLAIMED to completely and definitely 
remove all these burder about planning disk layouts.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080202215029.X4066>