Right, put some small (30GB or something trivial) disks in for root and
then make a nice fast multi-spindle pool for your data. If your 320s
are around the same performance as your 500s, you could stripe and
mirror them all into a big pool. ZFS will waste the extra 180 on the
bigger disks but that's fine because your pool will bigger and faster
anyway.
On 03/25/11 09:18, Mark Sandrock wrote:
On Mar 24, 2011, at 7:23 AM, Anonymous wrote:
Generally, you choose your data pool config based on data size,
redundancy, and performance requirements. If those are all satisfied with
your single mirror, the only thing left for you to do is think about
splitting your data off onto a separate pool due to better performance
etc. (Because there are things you can't do with the root pool, such as
striping and raidz)
That's all there is to it. To split, or not to split.
Thanks for the update. I guess there's not much to do for this box since
it's a development machine and doesn't have much need for extra redundancy
although if I would have had some extra 500s I would have liked to stripe
the root pool. I see from your answer that's not possible anyway. Cheers.
If you plan to generate a lot of data, why use the root pool? You can put the
/home
and /proj filesystems (/export/...) on a separate pool, thus off-loading the
root pool.
My two cents,
Mark
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
