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.
I don't, it's a development box with not alot happening.
My two cents,
thanks
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
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
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
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Nomen Nescio
Hi ladies and gents, I've got a new Solaris 10 development box with ZFS
mirror root using 500G drives. I've got several extra 320G drives and I'm
wondering if there's any way I
On Mar 24, 2011, at 5:42 AM, Edward Ned Harvey wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Nomen Nescio
Hi ladies and gents, I've got a new Solaris 10 development box with ZFS
mirror root using 500G drives. I've got several
Hi ladies and gents, I've got a new Solaris 10 development box with ZFS
mirror root using 500G drives. I've got several extra 320G drives and I'm
wondering if there's any way I can use these to good advantage in this
box. I've got enough storage for my needs with the 500G pool. At this point
I
