From member at linkedin.com Wed Jan 16 06:20:16 2013 From: member at linkedin.com (Nauman yousuf via LinkedIn) Date: Wed, 16 Jan 2013 06:20:16 +0000 (UTC) Subject: Invitation to connect on LinkedIn Message-ID: <378560800.696316.1358317216787.JavaMail.app@ela4-app2308.prod> LinkedIn ------------ Nauman yousuf requested to add you as a connection on LinkedIn: ------------------------------------------ prasad, I'd like to add you to my professional network on LinkedIn. - Nauman Accept invitation from Nauman yousuf http://www.linkedin.com/e/gqo4xa-hc03007d-4f/uDOOeOoBcDnu7cRsgtmHGao4wzLdPX8f936x8gS/blk/I557289395_25/0UcDpKqiRzolZKqiRybmRSrCBvrmRLoORIrmkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYRcBYRejcVe38Tdjl9bS93dQRUjmpMbPwMc3sOejgUc38LrCBxbOYWrSlI/eml-comm_invm-b-in_ac-inv28/?hs=false&tok=2AfatbeToss5A1 View profile of Nauman yousuf http://www.linkedin.com/e/gqo4xa-hc03007d-4f/rso/19421652/gjL9/name/25000459_I557289395_25/?hs=false&tok=3Ijb6nFFUss5A1 ------------------------------------------ You are receiving Invitation emails. This email was intended for prasad thati. Learn why this is included: http://www.linkedin.com/e/gqo4xa-hc03007d-4f/plh/http%3A%2F%2Fhelp%2Elinkedin%2Ecom%2Fapp%2Fanswers%2Fdetail%2Fa_id%2F4788/-GXI/?hs=false&tok=0Dh98tkT0ss5A1 (c) 2012, LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -------------- next part -------------- An HTML attachment was scrubbed... URL: From flloreda at redhat.com Fri Jan 18 11:31:51 2013 From: flloreda at redhat.com (Francisco Javier Lloreda Sanchez) Date: Fri, 18 Jan 2013 12:31:51 +0100 Subject: Crete Volgroup from anaconda ks using the whole disk Message-ID: <50F932A7.4090301@redhat.com> Hi all, Has someone managed to create a volume group from a kickstart that uses the whole disk and not a partition ? I tried to create the pv, vg and lv from a pre script and then use the --useexisting flag for logvol and anaconda complains about the vg is not created and I guess is because I didn't use the volgroup command in the partitioning section. If I use the volgroup tag with --useexisting in the partitioning section I'm forced to use a list of partitions that is what I'm triying to avoid.... So any suggestions? Thanks -- -- Francisco Javier Lloreda Red Hat Consultant ( RHCA , RHCDS , RHCVA ) #110-651-718 flloreda at redhat.com Mobile: 0034 600 48 39 73 c/ Jose Bardasano Baos, No. 9 Edificio Gorbea 3 Madrid, 28016 SPAIN From matthew.m.conley.ctr at navy.mil Fri Jan 18 17:37:12 2013 From: matthew.m.conley.ctr at navy.mil (Conley, Matthew M CTR JXSNM, JSORD) Date: Fri, 18 Jan 2013 12:37:12 -0500 Subject: Crete Volgroup from anaconda ks using the whole disk References: <50F932A7.4090301@redhat.com> Message-ID: <31A1B8DF30D54E478532C692A0A4D3EA034A116F@naeacranez02v.nadsusea.nads.navy.mil> Like this? #Clean install, remove all exisiting partitions clearpart --all --initlabel #create partitions for boot and swap part /boot --fstype ext3 --size=100 --ondisk=sda #This is a cheat to allow the partition for the logical volume to grow and consume the rest of the disk part pv.0 --size=1 --encrypted --passphrase=PASSPHRASE --grow --ondisk=sda part pv.1 --size=1 --encrypted --passphrase=PASSPHRASE --grow --ondisk=sdb #create volume group vg0 #then create logical volumes for root, home, and log volgroup vg0 pv.0 logvol / --fstype=ext4 --name=lv_root --vgname=vg0 --size=10000 logvol swap --fstype=swap --name=lv_swap --vgname=vg0 --size=4096 logvol /home --fstype=ext4 --name=lv_home --vgname=vg0 --size=1000 --grow logvol /var/log --fstype=ext4 --name=lv_log --vgname=vg0 --size=5000 volgroup vg1 pv.1 logvol /var/lib/mysql --fstype=ext4 --name=lv_lib --vgname=vg1 --size=85000 logvol /var/files --fstype=ext4 --name=lv_data --vgname=vg1 --size=20000 --grow Regards Matthew M. Conley Linux+, A+, Net+, LPIC1 Systems Engineer Next Wave Systems 912.398.6704 -----Original Message----- From: Francisco Javier Lloreda Sanchez [mailto:flloreda at redhat.com] Sent: Fri 1/18/2013 6:31 AM To: kickstart-list at redhat.com Subject: Crete Volgroup from anaconda ks using the whole disk Hi all, Has someone managed to create a volume group from a kickstart that uses the whole disk and not a partition ? I tried to create the pv, vg and lv from a pre script and then use the --useexisting flag for logvol and anaconda complains about the vg is not created and I guess is because I didn't use the volgroup command in the partitioning section. If I use the volgroup tag with --useexisting in the partitioning section I'm forced to use a list of partitions that is what I'm triying to avoid.... So any suggestions? Thanks -- -- Francisco Javier Lloreda Red Hat Consultant ( RHCA , RHCDS , RHCVA ) #110-651-718 flloreda at redhat.com Mobile: 0034 600 48 39 73 c/ Jose Bardasano Baos, No. 9 Edificio Gorbea 3 Madrid, 28016 SPAIN From flloreda at redhat.com Fri Jan 18 18:03:25 2013 From: flloreda at redhat.com (Francisco Javier Lloreda Sanchez) Date: Fri, 18 Jan 2013 19:03:25 +0100 Subject: Crete Volgroup from anaconda ks using the whole disk In-Reply-To: <31A1B8DF30D54E478532C692A0A4D3EA034A116F@naeacranez02v.nadsusea.nads.navy.mil> References: <50F932A7.4090301@redhat.com> <31A1B8DF30D54E478532C692A0A4D3EA034A116F@naeacranez02v.nadsusea.nads.navy.mil> Message-ID: <50F98E6D.1080300@redhat.com> Thanks MAtthew for your answer but this is exactly what I'm triying to avoid... :) I would like to have the equivalent to : pvcreate /dev/vdb vgcreate test /dev/vdb lvcreate -n lv_test -L 10G test So at the end of the installation I would have a vg over no partition (not the whole disk but over the disk device). Thanks -- Francisco Javier Lloreda Red Hat Consultant ( RHCA , RHCDS , RHCVA ) #110-651-718 flloreda at redhat.com Mobile: 0034 600 48 39 73 c/ Jose Bardasano Baos, No. 9 Edificio Gorbea 3 Madrid, 28016 SPAIN El 18/01/13 18:37, Conley, Matthew M CTR JXSNM, JSORD escribi?: > Like this? > > #Clean install, remove all exisiting partitions > clearpart --all --initlabel > > #create partitions for boot and swap > part /boot --fstype ext3 --size=100 --ondisk=sda > > #This is a cheat to allow the partition for the logical volume to grow and consume the rest of the disk > > part pv.0 --size=1 --encrypted --passphrase=PASSPHRASE --grow --ondisk=sda > > part pv.1 --size=1 --encrypted --passphrase=PASSPHRASE --grow --ondisk=sdb > > #create volume group vg0 > #then create logical volumes for root, home, and log > volgroup vg0 pv.0 > logvol / --fstype=ext4 --name=lv_root --vgname=vg0 --size=10000 > logvol swap --fstype=swap --name=lv_swap --vgname=vg0 --size=4096 > logvol /home --fstype=ext4 --name=lv_home --vgname=vg0 --size=1000 --grow > logvol /var/log --fstype=ext4 --name=lv_log --vgname=vg0 --size=5000 > > volgroup vg1 pv.1 > logvol /var/lib/mysql --fstype=ext4 --name=lv_lib --vgname=vg1 --size=85000 > logvol /var/files --fstype=ext4 --name=lv_data --vgname=vg1 --size=20000 --grow > > > Regards > Matthew M. Conley Linux+, A+, Net+, LPIC1 > Systems Engineer > Next Wave Systems > 912.398.6704 > > > > -----Original Message----- > From: Francisco Javier Lloreda Sanchez [mailto:flloreda at redhat.com] > Sent: Fri 1/18/2013 6:31 AM > To: kickstart-list at redhat.com > Subject: Crete Volgroup from anaconda ks using the whole disk > > Hi all, > > Has someone managed to create a volume group from a kickstart that uses > the whole disk and not a partition ? > > I tried to create the pv, vg and lv from a pre script and then use the > --useexisting flag for logvol and anaconda complains about the vg is not > created and I guess is because I didn't use the volgroup command in the > partitioning section. > If I use the volgroup tag with --useexisting in the partitioning section > I'm forced to use a list of partitions that is what I'm triying to > avoid.... > > So any suggestions? > > Thanks > From david at graniteweb.com Fri Jan 18 22:59:14 2013 From: david at graniteweb.com (David Rock) Date: Fri, 18 Jan 2013 16:59:14 -0600 Subject: Crete Volgroup from anaconda ks using the whole disk In-Reply-To: <50F98E6D.1080300@redhat.com> References: <50F932A7.4090301@redhat.com> <31A1B8DF30D54E478532C692A0A4D3EA034A116F@naeacranez02v.nadsusea.nads.navy.mil> <50F98E6D.1080300@redhat.com> Message-ID: <20130118225914.GB5821@wdfs.bad> * Francisco Javier Lloreda Sanchez [2013-01-18 19:03]: > Thanks MAtthew for your answer but this is exactly what I'm triying to > avoid... :) > > I would like to have the equivalent to : > pvcreate /dev/vdb > vgcreate test /dev/vdb > lvcreate -n lv_test -L 10G test > > So at the end of the installation I would have a vg over no partition > (not the whole disk but over the disk device). One question I have is: Besides the academic exercise of being able to do it, is there a requirement to do it? I understand wanting to know if something is possible just for the sake of knowing, but do you have a functional reason that you _need_ to write to the disk rather than a partition? -- David Rock david at graniteweb.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 190 bytes Desc: not available URL: From flloreda at redhat.com Mon Jan 21 06:22:53 2013 From: flloreda at redhat.com (Francisco Javier Lloreda Sanchez) Date: Mon, 21 Jan 2013 07:22:53 +0100 Subject: Crete Volgroup from anaconda ks using the whole disk In-Reply-To: <20130118225914.GB5821@wdfs.bad> References: <50F932A7.4090301@redhat.com> <31A1B8DF30D54E478532C692A0A4D3EA034A116F@naeacranez02v.nadsusea.nads.navy.mil> <50F98E6D.1080300@redhat.com> <20130118225914.GB5821@wdfs.bad> Message-ID: <50FCDEBD.10003@redhat.com> Hi David, The reason behind this question is I want to install a Virtual Server. This server will have 2 disks, the first one for /boot and mapped to a lv in the physical server, the second disk will be for system and /home and will be mapped to a lv in the physical server also. I know /home will grow quickly due to the use of the server. So if I create the PV and VG on a partition (vdb1) when I need extend the disk I need to add new partitions, in a few extends I will have many partitions on the disk or many new disks in the virtual server. In the other hand If I create the PV and VG on the device (vdb) I just need to extend the LV in the physical server, ensure the virtual server recognizes the new space on the disk and pvextend, vgextend and lvextend. Am I wrong ? Thanks for your time :) -- Francisco Javier Lloreda Red Hat Consultant ( RHCA , RHCDS , RHCVA ) #110-651-718 flloreda at redhat.com Mobile: 0034 600 48 39 73 c/ Jose Bardasano Baos, No. 9 Edificio Gorbea 3 Madrid, 28016 SPAIN El 18/01/13 23:59, David Rock escribi?: > * Francisco Javier Lloreda Sanchez [2013-01-18 19:03]: >> Thanks MAtthew for your answer but this is exactly what I'm triying to >> avoid... :) >> >> I would like to have the equivalent to : >> pvcreate /dev/vdb >> vgcreate test /dev/vdb >> lvcreate -n lv_test -L 10G test >> >> So at the end of the installation I would have a vg over no partition >> (not the whole disk but over the disk device). > One question I have is: Besides the academic exercise of being able to > do it, is there a requirement to do it? I understand wanting to know if > something is possible just for the sake of knowing, but do you have a > functional reason that you _need_ to write to the disk rather than a > partition? > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From fvzwieten at vxcompany.com Mon Jan 21 07:29:38 2013 From: fvzwieten at vxcompany.com (Fred van Zwieten) Date: Mon, 21 Jan 2013 08:29:38 +0100 Subject: Conditional partitioning/formatting of device possible Message-ID: Hi there, Is there a possibility in the kickstart syntax to partition/format a device, but only if it's not already partitioned/formatted. Use case: I have a server with a data disk. First time deployment it should be partitioned and formatted. Second time, the data partition must be left as is and only mounted. I now about --noformat, but how to make that conditional? If not possible, I must use %post. Any examples on how to do this there using bash or python? Regards, Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: From flloreda at redhat.com Mon Jan 21 08:10:57 2013 From: flloreda at redhat.com (Francisco Javier Lloreda Sanchez) Date: Mon, 21 Jan 2013 09:10:57 +0100 Subject: Conditional partitioning/formatting of device possible In-Reply-To: References: Message-ID: <50FCF811.7020106@redhat.com> You can use a pre script to detect if is previously partitioned or not and then use something similar to: %pre #!/bin/sh Discover condition if condition; then echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" >> /tmp/part-include echo "part pv.100000 --size=1 --grow --ondisk=$DISCO" >> /tmp/part-include echo "volgroup Merca --pesize=32768 pv.100000" >> /tmp/part-include echo "logvol swap --fstype swap --name=Swap --vgname=Merca --size=2047" >> /tmp/part-include echo "logvol / --fstype ext4 --name=root --vgname=Merca --size=2048" >> /tmp/part-include echo "logvol /home --fstype ext4 --size=1000 --name=home --vgname=Merca" >> /tmp/part-include else echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" >> /tmp/part-include echo "volgroup Merca --pesize=32768 --useexisting --noformat" >> /tmp/part-include echo "logvol swap --fstype swap --name=Swap --vgname=Merca --size=2047 --useexisting --noformat" >> /tmp/part-include echo "logvol / --fstype ext4 --name=root --vgname=Merca --size=2048 --useexisting --noformat" >> /tmp/part-include echo "logvol /home --fstype ext4 --size=1000 --name=home --vgname=Merca --useexisting --noformat" >> /tmp/part-include fi Later in the partitioning section use %include /tmp/part-include Hope this helps to you :) -- Francisco Javier Lloreda Red Hat Consultant ( RHCA , RHCDS , RHCVA ) #110-651-718 flloreda at redhat.com Mobile: 0034 600 48 39 73 c/ Jose Bardasano Baos, No. 9 Edificio Gorbea 3 Madrid, 28016 SPAIN El 21/01/13 08:29, Fred van Zwieten escribi?: > Hi there, > > Is there a possibility in the kickstart syntax to partition/format a > device, but only if it's not already partitioned/formatted. > > Use case: I have a server with a data disk. First time deployment it > should be partitioned and formatted. Second time, the data partition > must be left as is and only mounted. > > I now about --noformat, but how to make that conditional? > > If not possible, I must use %post. Any examples on how to do this > there using bash or python? > > Regards, > > Fred > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jack.Allen at mckesson.com Thu Jan 24 18:41:58 2013 From: Jack.Allen at mckesson.com (Allen, Jack) Date: Thu, 24 Jan 2013 18:41:58 +0000 Subject: Disable automatic enabling of multipathd Message-ID: <4A8A2A3D96DD154BAD2EE08C0FFFBE5A46AF0636@NDHEP50002.na.corp.mckesson.com> First some history; we have a customer that will be implementing Clustering between 2 physical system that will share some storage on a SAN. One system was already running RHEL 5.8 32-bit and they are upgrading to RHEL 6.3 64-bit over all. So on the second system a RHEL 6.3 64-bit KickStart provided by us was installed. Our instructions stated to disconnect the system from the SAN before doing the KickStart, but they did not. The system has local storage for the OS and the OS was installed on it as it should have been. But because the SAN was connected and the LUNs zoned to the system, the KickStart identified the multiple paths to the LUNs and enabled multipathd, ran pvcreate on the /dev/mapper/mpath* names which over wrote the existing header/labels on each LUN and put new uuid on each and cleared the LVM label information. On the system running RHEL 5.8 the VG and the LV could still be access but all command such as lvs, pvs and vgs would not show information because of the missing LVM labels. We had to reboot the active system and then run pvcreate with the -uuid option to put the correct uuid back in place on each LUN, there were 16 of them. And then run vgcfgrestore on the VG and everything is fine now. Once the RHEL 6.3 64-bit system is working properly the RHEL 5.8 32-bit system will be brought down and the SAN storage will be accessed from the RHEL 6.3 64-bit system. Then the RHEL 6.3 64-bit KickStart will be run on the old RHEL 5.8 32-bit system to upgrade it, which means both systems will be running RHEL 6.3 64-bit and the Cluster software will be activated. So what option or whatever can be specified in the KickStart to not automatically scan for SAN storage and enable multipathd and run pvcreate? ------------------------- Jackson C. Allen McKesson Provider Technologies 5995 Windward Parkway Alpharetta, GA 30005 (404) 338-2023 Jack.Allen at McKesson.com Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Floydsmith at aol.com Fri Jan 25 13:20:09 2013 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Fri, 25 Jan 2013 08:20:09 -0500 (EST) Subject: need grub2 cfg file more memory stick ks install Message-ID: <2f960.331faa2f.3e33e089@aol.com> Hello all, I am trying to build and install a customized f18 install image and /ks.cfg file. I have created my install image f18.iso but do its size I can not put on a DVD. I have installed grub2 on an ext3 formated memory stick which is my third disk /dev/sdc and it will be the third disk durring installation. I have copied the image to /sdc1 and copied from the isoimage dir vmlinuz and initrd.iso to /sdc1/boot. I have no familarity with grub2. My question is what should be the stanza lines in the grub2 grub.cfg file for method=hd:sdc1:/ ks=hd:sdc1:/ks.cfg install. Floyd Smith, -------------- next part -------------- An HTML attachment was scrubbed... URL: From cjk at techma.com Fri Jan 25 14:08:35 2013 From: cjk at techma.com (Kovacs, Corey J.) Date: Fri, 25 Jan 2013 14:08:35 +0000 Subject: Disable automatic enabling of multipathd In-Reply-To: <4A8A2A3D96DD154BAD2EE08C0FFFBE5A46AF0636@NDHEP50002.na.corp.mckesson.com> References: <4A8A2A3D96DD154BAD2EE08C0FFFBE5A46AF0636@NDHEP50002.na.corp.mckesson.com> Message-ID: Jackson, This isn't a problem with multipathd, rather that the SAN volumes are visible during the kickstart I'd say. I was bitten by this long ago... once... and it sucked :) Now I am very careful to say the least. You have a couple of options right off the bat. 1. I think the "nostorage" flag still works, put that on the kernel line and then in the kickstart specify which device drivers you need loaded in the kickstart. On a newer HP box running rhel6 I add the "hpsa" driver via a "device" flag. On an older rhel5 install, it's still "cciss" for the smart array. This has worked for me. 2. In the %pre section, you can remove/unload the fibre channel card drivers, then those volumes will not get scanned since they will not be seen. Your description doesn't indicate (to me anyway) if you are booting from the san devices so I am assuming you are booting from local storage, and then accessing the san after the fact. You also didn't include the partition layout so I am suspecting that you might be using autopart. If that is the case, and your primary storage is local, then one of the two options above should work. If you aren't using autopart, then you might think about being a bit more specific in the partition information when designing the setup. I hope this helps, I certainly know the feeling when a system blows away all of the cluster data when this happens :) Corey Corey Kovacs Sr. System Architect Technology Management Associates RHCA: 110-541-489 ________________________________ From: kickstart-list-bounces at redhat.com [kickstart-list-bounces at redhat.com] on behalf of Allen, Jack [Jack.Allen at mckesson.com] Sent: Thursday, January 24, 2013 1:41 PM To: kickstart-list at redhat.com Subject: Disable automatic enabling of multipathd First some history; we have a customer that will be implementing Clustering between 2 physical system that will share some storage on a SAN. One system was already running RHEL 5.8 32-bit and they are upgrading to RHEL 6.3 64-bit over all. So on the second system a RHEL 6.3 64-bit KickStart provided by us was installed. Our instructions stated to disconnect the system from the SAN before doing the KickStart, but they did not. The system has local storage for the OS and the OS was installed on it as it should have been. But because the SAN was connected and the LUNs zoned to the system, the KickStart identified the multiple paths to the LUNs and enabled multipathd, ran pvcreate on the /dev/mapper/mpath* names which over wrote the existing header/labels on each LUN and put new uuid on each and cleared the LVM label information. On the system running RHEL 5.8 the VG and the LV could still be access but all command such as lvs, pvs and vgs would not show information because of the missing LVM labels. We had to reboot the active system and then run pvcreate with the ?uuid option to put the correct uuid back in place on each LUN, there were 16 of them. And then run vgcfgrestore on the VG and everything is fine now. Once the RHEL 6.3 64-bit system is working properly the RHEL 5.8 32-bit system will be brought down and the SAN storage will be accessed from the RHEL 6.3 64-bit system. Then the RHEL 6.3 64-bit KickStart will be run on the old RHEL 5.8 32-bit system to upgrade it, which means both systems will be running RHEL 6.3 64-bit and the Cluster software will be activated. So what option or whatever can be specified in the KickStart to not automatically scan for SAN storage and enable multipathd and run pvcreate? ------------------------- Jackson C. Allen McKesson Provider Technologies 5995 Windward Parkway Alpharetta, GA 30005 (404) 338-2023 Jack.Allen at McKesson.com Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jack.Allen at mckesson.com Fri Jan 25 15:08:17 2013 From: Jack.Allen at mckesson.com (Allen, Jack) Date: Fri, 25 Jan 2013 15:08:17 +0000 Subject: Disable automatic enabling of multipathd In-Reply-To: References: <4A8A2A3D96DD154BAD2EE08C0FFFBE5A46AF0636@NDHEP50002.na.corp.mckesson.com> Message-ID: <4A8A2A3D96DD154BAD2EE08C0FFFBE5A46AF1625@NDHEP50002.na.corp.mckesson.com> Corey: Thanks for the reply and information. See comments below. ------------------------- Jackson C. Allen McKesson Provider Technologies 5995 Windward Parkway Alpharetta, GA 30005 (404) 338-2023 Jack.Allen at McKesson.com Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Kovacs, Corey J. Sent: Friday, January 25, 2013 9:09 AM To: Discussion list about Kickstart Subject: RE: Disable automatic enabling of multipathd Jackson, This isn't a problem with multipathd, rather that the SAN volumes are visible during the kickstart I'd say. I was bitten by this long ago... once... and it sucked :) Now I am very careful to say the least. [JCA] I agree the problem itself is not multipath, but that anaconda found SAN devices accessible and decided to enable multipath and then run pvcreate on the LUNs it mapped to /dev/mapper/mpath*. This is the part that I feel is somewhat of a bug. You have a couple of options right off the bat. 1. I think the "nostorage" flag still works, put that on the kernel line and then in the kickstart specify which device drivers you need loaded in the kickstart. On a newer HP box running rhel6 I add the "hpsa" driver via a "device" flag. On an older rhel5 install, it's still "cciss" for the smart array. This has worked for me. [JCA] This could be a problem because the same KickStart is used on several vendors' hardware, Dell, HP, IBM and ESX/VMs. The vendors tend to change the local storage HBA from time to time. But this is something we can investigate. 2. In the %pre section, you can remove/unload the fibre channel card drivers, then those volumes will not get scanned since they will not be seen. [JCA] Again this could be problematic in making sure we remove all possible FC HBAs the vendors may have installed. We try to standardize on specific local and FC HBAs, but the vendors sometime install newer models that could have a different name. Your description doesn't indicate (to me anyway) if you are booting from the san devices so I am assuming you are booting from local storage, and then accessing the san after the fact. [JCA] I did state the system has local storage and the OS is/was loaded on it. You also didn't include the partition layout so I am suspecting that you might be using autopart. If that is the case, and your primary storage is local, then one of the two options above should work. If you aren't using autopart, then you might think about being a bit more specific in the partition information when designing the setup. [JCA] We are only partitioning the local storage via the KickStart and had assumed nothing would be done to any other storage found. Our instructions state the SAN should not be connected when kick starting the system, but our customer did not follow the instructions. So I am looking for a way to keep our customers from shooting themselves in the foot so to speak when they don't follow the instructions. I hope this helps, I certainly know the feeling when a system blows away all of the cluster data when this happens :) [JCA] Yes, this gives me some things to think about. Maybe some others will suggest some other options as well. Corey Corey Kovacs Sr. System Architect Technology Management Associates RHCA: 110-541-489 ________________________________ From: kickstart-list-bounces at redhat.com [kickstart-list-bounces at redhat.com] on behalf of Allen, Jack [Jack.Allen at mckesson.com] Sent: Thursday, January 24, 2013 1:41 PM To: kickstart-list at redhat.com Subject: Disable automatic enabling of multipathd First some history; we have a customer that will be implementing Clustering between 2 physical system that will share some storage on a SAN. One system was already running RHEL 5.8 32-bit and they are upgrading to RHEL 6.3 64-bit over all. So on the second system a RHEL 6.3 64-bit KickStart provided by us was installed. Our instructions stated to disconnect the system from the SAN before doing the KickStart, but they did not. The system has local storage for the OS and the OS was installed on it as it should have been. But because the SAN was connected and the LUNs zoned to the system, the KickStart identified the multiple paths to the LUNs and enabled multipathd, ran pvcreate on the /dev/mapper/mpath* names which over wrote the existing header/labels on each LUN and put new uuid on each and cleared the LVM label information. On the system running RHEL 5.8 the VG and the LV could still be access but all command such as lvs, pvs and vgs would not show information because of the missing LVM labels. We had to reboot the active system and then run pvcreate with the -uuid option to put the correct uuid back in place on each LUN, there were 16 of them. And then run vgcfgrestore on the VG and everything is fine now. Once the RHEL 6.3 64-bit system is working properly the RHEL 5.8 32-bit system will be brought down and the SAN storage will be accessed from the RHEL 6.3 64-bit system. Then the RHEL 6.3 64-bit KickStart will be run on the old RHEL 5.8 32-bit system to upgrade it, which means both systems will be running RHEL 6.3 64-bit and the Cluster software will be activated. So what option or whatever can be specified in the KickStart to not automatically scan for SAN storage and enable multipathd and run pvcreate? ------------------------- Jackson C. Allen McKesson Provider Technologies 5995 Windward Parkway Alpharetta, GA 30005 (404) 338-2023 Jack.Allen at McKesson.com Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at graniteweb.com Sat Jan 26 03:42:09 2013 From: david at graniteweb.com (David Rock) Date: Fri, 25 Jan 2013 21:42:09 -0600 Subject: Crete Volgroup from anaconda ks using the whole disk In-Reply-To: <50FCDEBD.10003@redhat.com> References: <50F932A7.4090301@redhat.com> <31A1B8DF30D54E478532C692A0A4D3EA034A116F@naeacranez02v.nadsusea.nads.navy.mil> <50F98E6D.1080300@redhat.com> <20130118225914.GB5821@wdfs.bad> <50FCDEBD.10003@redhat.com> Message-ID: <20130126034209.GD22620@wdfs.bad> * Francisco Javier Lloreda Sanchez [2013-01-21 07:22]: > Hi David, > The reason behind this question is I want to install a Virtual Server. > This server will have 2 disks, the first one for /boot and mapped to a > lv in the physical server, the second disk will be for system and /home > and will be mapped to a lv in the physical server also. > I know /home will grow quickly due to the use of the server. So if I > create the PV and VG on a partition (vdb1) when I need extend the disk I > need to add new partitions, in a few extends I will have many partitions > on the disk or many new disks in the virtual server. In the other hand > If I create the PV and VG on the device (vdb) I just need to extend the > LV in the physical server, ensure the virtual server recognizes the new > space on the disk and pvextend, vgextend and lvextend. > > Am I wrong ? Ok, that's a valid reason, although not completely correct that it's the only way to do it. Doing it that way should make it easier, but it is possible to extend the size of a partition rather than create a new one. The caveat is that the partition you are extending has to be the last one on the disk, which shouldn't be a problem since I'm assuming partition 1 is /boot and partition 2 is the rest of the disk as LVM. A very good walkthru can be found here: http://theducks.org/2009/11/expanding-lvm-partitions-in-vmware-on-the-fly/ This is what I've done in the past, and it works just fine. It is a bit unnerving to delete and recreate a partition in fdisk, but it actually works well. Having said all that, I do like the idea of cutting out the middleman, as it were. I would assume that should work, and would be cleaner (and a little less scary). :-) I don't know, offhand, if kickstart allows it or not. Maybe a pre-script to create the disk layout, but nothing I'm finding is very hopeful. Looking at this BZ suggests a pre-script might work for RHEL6: https://bugzilla.redhat.com/show_bug.cgi?id=703161 -- David Rock david at graniteweb.com