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. -- This message posted from opensolaris.org
On Sep 27, 2009, at 8:41 PM, Ron Watkins <rwatki at gmail.com> 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.You can''t have a raidz (raid5) with 2 disks, it''s a 3 disk minimum. You can have a mirror of the two. Get 2 good large disks and make a mirror.> 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.On the install it will ask you for the size you want to use, pick a smaller size. It will still create a partition filling the whole disk, but you can use format to create additional slices. I usually make mine slightly smaller then the disk, allows you to replace with a smaller disk in the future if need be and leaves a little room for utility slices, like a meta-data slice for SVM.> 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.Try zero''ing out the first sector (or 63 to get rid of any junk in the first cylinder), then use format and duplicate the layout of the first disk, add slice zero, then run installgrub. -Ross
My goal is to have a mirrored root on c1t0d0s0/c2t0d0s0, another mirrored app fs on c1t0d0s1/c2t0d0s1 and then a 3+1 Raid-5 accross c1t0d0s7/c1t1d0s7/c2t0d0s7/c2t1d0s7. I want to play with creating ISCSI target luns on the Raid-5 partition, so I am trying out opensolaris for the first time. In the past, I would use Solaris 10 with the SVM do create what I need, but without ISCSI target support. -- This message posted from opensolaris.org
Ron That should work it''s no real different to SVM. BTW: I did you mean? mirrored root on c1t0d0s0/c2t0d0s0 mirrored app on c1t1d0s0/c2t1d0s0 RaidZ accross c1t0d0s7/c1t1d0s7/c2t0d0s7/c2t1d0s7 I would then make slices 0 and 7 the same on all disks using fmthard (BTW:I would not use 7, I would use 1 - but that''s just preference) Remember you don''t need spare slices with ZFS root for Live Upgrade like you did with SVM. Ron Watkins wrote: My goal is to have a mirrored root on c1t0d0s0/c2t0d0s0, another mirrored app fs on c1t0d0s1/c2t0d0s1 and then a 3+1 Raid-5 accross c1t0d0s7/c1t1d0s7/c2t0d0s7/c2t1d0s7. I want to play with creating ISCSI target luns on the Raid-5 partition, so I am trying out opensolaris for the first time. In the past, I would use Solaris 10 with the SVM do create what I need, but without ISCSI target support. www.eagle.co.nz This email is confidential and may be legally privileged. If received in error please destroy and immediately notify us. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Yes, you are correct about the layout. However, I don''t appear to be able to control how the root pool is configured when I install from the live-CD. It either takes: a) The entire physical disk b) A slice the same size as the physical disk c) A smaller slice, but no way to get at the remaining space. Thus, im at a loss as to how to get the root pool setup as a 20Gb slice from the first disk. If I could somehow partition the disk first, then get the root pool on s0, then I can use the prtvtoc/fmthard to get c1t0 to look just like c0t0. I read some best practices guides, and they recommend keeping the root pool and the application pool seperate, but I cant'' figure out how to get to that point where I can split c0t0 into 2 parts BEFORE creating the root pool. -- This message posted from opensolaris.org
On Sep 27, 2009, at 10:05 PM, Ron Watkins <rwatki at gmail.com> wrote:> My goal is to have a mirrored root on c1t0d0s0/c2t0d0s0, another > mirrored app fs on c1t0d0s1/c2t0d0s1 and then a 3+1 Raid-5 accross > c1t0d0s7/c1t1d0s7/c2t0d0s7/c2t1d0s7.There is no need for the 2 mirrors both on c1t0 and c2t0 one mirrored rpool with multiple zfs datasets will provide the same performance with easier admin. As for overlapping zpools, well it can be done, but I''m not sure how well it''ll perform, or if there are any issues with zpools sharing disks. -Ross
On 09/28/09 12:40 AM, Ron Watkins wrote:> > Thus, im at a loss as to how to get the root pool setup as a 20Gb > slice20GB is too small. You''ll be fighting for space every time you use pkg. From my considerable experience installing to a 20GB mirrored rpool, I would go for 32GB if you can. Assuming this is X86, couldn''t you simply use fdisk to create whatever partitions you want and then install to one of them? Than you should be able to create the data pool using another partition. You might need to use a weird partition type temporarily. On SPARC there doesn''t seem to be a problem using slices for different zpools, in fact it insists on using a slice for the root pool. Cheers -- Frank
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.
On Mon, September 28, 2009 07:56, Frank Middleton wrote:> On 09/28/09 12:40 AM, Ron Watkins wrote: >> >> Thus, im at a loss as to how to get the root pool setup as a 20Gb >> slice > > 20GB is too small. You''ll be fighting for space every time > you use pkg. From my considerable experience installing to a > 20GB mirrored rpool, I would go for 32GB if you can.That seems truly bizarre. Virtualbox recommends 16GB, and after doing an install there''s about 12GB free. -- David Dyer-Bennet, dd-b at dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info
On 09/28/09 01:22 PM, David Dyer-Bennet wrote:> That seems truly bizarre. Virtualbox recommends 16GB, and after doing an > install there''s about 12GB free.There''s no way Solaris will install in 4GB if I understand what you are saying. Maybe fresh off a CD when it doesn''t have to download a copy first, but the reality is 16GB is not possible unless you don''t want ever to to an image update. What version are you running? Have you ever tried pkg image-update? # uname -a SunOS host8 5.11 snv_111b i86pc i386 i86pc Solaris # df -h Filesystem Size Used Avail Use% Mounted on rpool/ROOT/opensolaris-2 34G 13G 22G 37% / .... # du -sh /var/pkg/download/ 762M /var/pkg/download/ this after deleting all old BEs and all snapshots but not emptying /var/pkg/download; swap/boot are on different slices. SPARC is similar; snv122 takes 11Gb after deleting old BEs, all snapshots, *and* /var/pkg/downloads; *without* /opt, swap, /var/crash, /var/dump, /var/tmp, /var/run and /export... AFAIK It is absolutely impossible to do a pkg image-update (say) from snv111b to snv122 without at least 9GB free (it says 8GB in the documentation). If the baseline is 11GB, you need 20GB for an install, and that leaves you zip to spare. Obvious reasons include before and after snaps, download before install, and total rollback capability. This is all going to cost some space. I believe there is a CR about this, but IMO when you can get 2TB of disk for $200 it''s hard to complain. 32GB of SSD is not unreasonable and 16GB simply won''t hack it. All the above is based on actual and sometimes painful experience. You *really* don''t want to run out of space during an update. You''ll almost certainly end up restoring your boot disk if you do and if you don''t, you''ll never get back all the space. Been there, done that... Cheers -- Frank