Hi Ron, Any reason why you want to use slices except for the root pool?
I would recommend a 4-disk configuration like this: mirrored root pool on c1t0d0s0 and c2t0d0s0 mirrored app pool on c1t1d0 and c2t1d0 Let the install use one big slice for each disk in the mirrored root pool, which is required for booting and whole disks for the app pool. Other than for the root pool, slices are not required. In the future, you can attach/add more disks to the app pool and/or replace with larger disks in either pool. Any additional administration, such as trying to expand a slice (you can't expand an existing slice under a live pool) or reconfiguration is much easier without having to muck with slices. Cindy On 09/27/09 18:41, Ron Watkins wrote:
I have a box with 4 disks. It was my intent to place a mirrored root partition on 2 disks on different controllers, then use the remaining space and the other 2 disks to create a raid-5 configuration from which to export iscsi luns for use by other hosts. The problem im having is that when I try to install OS, it either takes the entire disk or a partition the same size as the entire disk. I tried creating 2 slices, but the install won't allow it and if I make the solaris partition smaller, then the OS no longer sees the rest of the disk, only the small piece. I found references on how to mirror the root disk pool, but the grub piece doesn't seem to work as when I disconnect the first disk all I get at reboot is a grub prompt.
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
