From arthur.lutz at logilab.fr Wed Feb 3 11:30:26 2010 From: arthur.lutz at logilab.fr (Arthur Lutz) Date: Wed, 3 Feb 2010 12:30:26 +0100 Subject: --encrypted crashes anaconda on F11 install Message-ID: <20100203113026.GN6260@draco.logilab.fr> Hi, I'm generating an install DVD using pungi. After adding a "--encrypted" flag on a partition :: part /home --fstype=ext4 --label=home --grow --size=1024 --encrypted I get a crash on anaconda : /usr/lib/anaconda/kickstart.py, line 696 in parse if pd.preexist: AttributeError : `F11_PartData` object has no attribute preexist I'm tempted to add a "hasattr(fd, 'preexist') and" but I'm not sure this is the right solution, and wheter or not I should file a bug. Thanks in advance. Arthur Lutz From courchea at net-forces.com Thu Feb 25 15:03:52 2010 From: courchea at net-forces.com (Andre Courchesne) Date: Thu, 25 Feb 2010 10:03:52 -0500 Subject: Pre-install user input confirmation Message-ID: <6A3F612B-4A28-4C1B-9DE7-DB2ADE65D8B5@net-forces.com> Hi all, I got a kickstart automated installation working great, but since this install wipes the entire HDD, for precaution, I would like to add a pre-install user input confirmation screen. How can I do that? Thanks, --- Andre Courchesne - Consultant http://www.net-forces.com MSN: courchea at net-forces.com Skype: VoipForces L'information contenue dans le pr?sent document est la propri?t? de Andre Courchesne. Et est divulgu?e en toute confidentialit?. Cette information ne doit pas ?tre utilis?e, divulgu?e ? d'autres personnes ou reproduite sans le consentement ?crit explicite de Andre Courchesne. The information contained in this document is confidential and property of Andre Courchesne. It shall not be used, disclosed to others or reproduced without the express written consent of Andre Courchesne. From a.roussos at ucl.ac.uk Thu Feb 25 15:39:32 2010 From: a.roussos at ucl.ac.uk (Andreas Roussos) Date: Thu, 25 Feb 2010 15:39:32 +0000 Subject: Pre-install user input confirmation In-Reply-To: <6A3F612B-4A28-4C1B-9DE7-DB2ADE65D8B5@net-forces.com> References: <6A3F612B-4A28-4C1B-9DE7-DB2ADE65D8B5@net-forces.com> Message-ID: <4B8699B4.8070504@ucl.ac.uk> Hi Andre, Andre Courchesne wrote: > Hi all, > > I got a kickstart automated installation working great, but since this install wipes the entire HDD, for precaution, I would like to add a pre-install user input confirmation screen. How can I do that? Does your kickstart file include the 'clearpart' option? If yes, comment it out and it upon the next installation Anaconda will prompt you before doing wiping the disk(s). Regards, Andreas Roussos Systems Administrator UCL Research Computing > > Thanks, > > --- > > Andre Courchesne - Consultant > > http://www.net-forces.com > > MSN: courchea at net-forces.com > > Skype: VoipForces > > > > L'information contenue dans le pr?sent document est la propri?t? de Andre Courchesne. Et est divulgu?e en toute confidentialit?. Cette information ne doit pas ?tre utilis?e, divulgu?e ? d'autres personnes ou reproduite sans le consentement ?crit explicite de Andre Courchesne. > > The information contained in this document is confidential and property of Andre Courchesne. It shall not be used, disclosed to others or reproduced without the express written consent of Andre Courchesne. > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From peter.scheie at visionshareinc.com Thu Feb 25 15:43:56 2010 From: peter.scheie at visionshareinc.com (Peter Scheie) Date: Thu, 25 Feb 2010 09:43:56 -0600 Subject: Pre-install user input confirmation In-Reply-To: <6A3F612B-4A28-4C1B-9DE7-DB2ADE65D8B5@net-forces.com> References: <6A3F612B-4A28-4C1B-9DE7-DB2ADE65D8B5@net-forces.com> Message-ID: <1267112636.7299.18.camel@pscheie-ubuntu910> In your kickstart file, you can put some shell commands into a %pre section that prompt the user. We use something like this: # # Pre-installation section # %pre #!/bin/sh exec < /dev/tty3 > /dev/tty3 2>&1 chvt 3 install="no" while [ "$install" != "yes" ]; do clear echo echo '********************************************************************************' echo '* W A R N I N G *' echo '* *' echo '* You are starting the xxxxxxx xxxxx xxxxxxxxxxxxx Software installation *' echo '* process. This process will install a completely new operating system and *' echo '* software. Any software previously on this system will be irrevocably lost. *' echo '* *' echo '* Do you wish to continue? (Type the entire word "yes" to proceed.) *' echo '* *' echo '********************************************************************************' echo read -p "Proceed with install? " install done clear chvt 1 #%end The chvt commands are needed to make the warning appear on the correct vt on the console. HTH. Peter On Thu, 2010-02-25 at 09:03 -0600, Andre Courchesne wrote: > Hi all, > > I got a kickstart automated installation working great, but since this install wipes the entire HDD, for precaution, I would like to add a pre-install user input confirmation screen. How can I do that? > > Thanks, > > --- > > Andre Courchesne - Consultant > > http://www.net-forces.com > > MSN: courchea at net-forces.com > > Skype: VoipForces > > > > L'information contenue dans le pr?sent document est la propri?t? de Andre Courchesne. Et est divulgu?e en toute confidentialit?. Cette information ne doit pas ?tre utilis?e, divulgu?e ? d'autres personnes ou reproduite sans le consentement ?crit explicite de Andre Courchesne. > > The information contained in this document is confidential and property of Andre Courchesne. It shall not be used, disclosed to others or reproduced without the express written consent of Andre Courchesne. > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From courchea at net-forces.com Thu Feb 25 16:32:50 2010 From: courchea at net-forces.com (Andre Courchesne) Date: Thu, 25 Feb 2010 11:32:50 -0500 Subject: Pre-install user input confirmation In-Reply-To: <1267112636.7299.18.camel@pscheie-ubuntu910> References: <6A3F612B-4A28-4C1B-9DE7-DB2ADE65D8B5@net-forces.com> <1267112636.7299.18.camel@pscheie-ubuntu910> Message-ID: <1866D81B-1065-4DF5-B4B9-01672D6697B2@net-forces.com> Thanks Peter, That was exactly what I was looking for. --- Andre Courchesne - Consultant http://www.net-forces.com MSN: courchea at net-forces.com Skype: VoipForces L'information contenue dans le pr?sent document est la propri?t? de Andre Courchesne. Et est divulgu?e en toute confidentialit?. Cette information ne doit pas ?tre utilis?e, divulgu?e ? d'autres personnes ou reproduite sans le consentement ?crit explicite de Andre Courchesne. The information contained in this document is confidential and property of Andre Courchesne. It shall not be used, disclosed to others or reproduced without the express written consent of Andre Courchesne. On 2010-02-25, at 10:43 AM, Peter Scheie wrote: > In your kickstart file, you can put some shell commands into a %pre > section that prompt the user. We use something like this: > > # > # Pre-installation section > # > %pre > #!/bin/sh > exec < /dev/tty3 > /dev/tty3 2>&1 > chvt 3 > install="no" > while [ "$install" != "yes" ]; do > clear > echo > echo '********************************************************************************' > echo '* W A R N I N G *' > echo '* *' > echo '* You are starting the xxxxxxx xxxxx xxxxxxxxxxxxx Software installation *' > echo '* process. This process will install a completely new operating system and *' > echo '* software. Any software previously on this system will be irrevocably lost. *' > echo '* *' > echo '* Do you wish to continue? (Type the entire word "yes" to proceed.) *' > echo '* *' > echo '********************************************************************************' > echo > read -p "Proceed with install? " install > done > clear > chvt 1 > #%end > > The chvt commands are needed to make the warning appear on the correct vt on the console. HTH. > > Peter > > On Thu, 2010-02-25 at 09:03 -0600, Andre Courchesne wrote: >> Hi all, >> >> I got a kickstart automated installation working great, but since this install wipes the entire HDD, for precaution, I would like to add a pre-install user input confirmation screen. How can I do that? >> >> Thanks, >> >> --- >> >> Andre Courchesne - Consultant >> >> http://www.net-forces.com >> >> MSN: courchea at net-forces.com >> >> Skype: VoipForces >> >> >> >> L'information contenue dans le pr?sent document est la propri?t? de Andre Courchesne. Et est divulgu?e en toute confidentialit?. Cette information ne doit pas ?tre utilis?e, divulgu?e ? d'autres personnes ou reproduite sans le consentement ?crit explicite de Andre Courchesne. >> >> The information contained in this document is confidential and property of Andre Courchesne. It shall not be used, disclosed to others or reproduced without the express written consent of Andre Courchesne. >> >> >> >> >> >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From twelvefortyfive at yahoo.com Thu Feb 25 20:32:14 2010 From: twelvefortyfive at yahoo.com (Arun) Date: Thu, 25 Feb 2010 12:32:14 -0800 (PST) Subject: Using kickstart on large disks Message-ID: <433540.87104.qm@web32104.mail.mud.yahoo.com> Hi - I was wondering if you guys had some thoughts on an issue I'm running into using kickstart to automate installs on intel x86 servers with large disks (~16 TB). What I'm trying to achieve is simple: a root volume of 100GB, and a database volume on all remaining space. It appears however that anaconda is restricting logical volumes to 8TB, even for ext4 partitions. I narrowed the problematic code down to storage/formats/fs.py where the Ext4 file type extends via Ext3 from Ext2, in which I saw this line: _maxSize = 8 * 1024 * 1024 Is there a reason for this limit to be inherited down to Ext4 partitions as well? See my kickstart snippet below - the "/db" partition has the --grow option, but it will not grow beyond 8TB due to the code above, leaving nearly 8TB completely unused on the server. ------------------------------------------------------------------------ clearpart --all bootloader --location=mbr # Create partitions: 200 MB for boot, remaining for everything else. part /boot --size=200 --fstype ext3 part pv.01 --size=1 --grow # Create a single volume group volgroup vg pv.01 # Create a swap volume of "recommended size", a root volume of 100GB # and a database volume on the remaining space logvol swap --fstype swap --name=swap_vol --vgname=vg --recommended logvol / --fstype ext4 --name=root_vol --vgname=vg --size=100000 logvol /db --fstype ext4 --name=db_vol --vgname=vg --size=1 --grow ------------------------------------------------------------------------ Thanks in advance, Arun From chip.shabazian at bankofamerica.com Thu Feb 25 21:09:17 2010 From: chip.shabazian at bankofamerica.com (Shabazian, Chip) Date: Thu, 25 Feb 2010 13:09:17 -0800 Subject: Using kickstart on large disks In-Reply-To: <433540.87104.qm@web32104.mail.mud.yahoo.com> References: <433540.87104.qm@web32104.mail.mud.yahoo.com> Message-ID: Why not just create the /db volume in the %post? -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Arun Sent: Thursday, February 25, 2010 12:32 PM To: kickstart-list at redhat.com Subject: Using kickstart on large disks Hi - I was wondering if you guys had some thoughts on an issue I'm running into using kickstart to automate installs on intel x86 servers with large disks (~16 TB). What I'm trying to achieve is simple: a root volume of 100GB, and a database volume on all remaining space. It appears however that anaconda is restricting logical volumes to 8TB, even for ext4 partitions. I narrowed the problematic code down to storage/formats/fs.py where the Ext4 file type extends via Ext3 from Ext2, in which I saw this line: _maxSize = 8 * 1024 * 1024 Is there a reason for this limit to be inherited down to Ext4 partitions as well? See my kickstart snippet below - the "/db" partition has the --grow option, but it will not grow beyond 8TB due to the code above, leaving nearly 8TB completely unused on the server. ------------------------------------------------------------------------ clearpart --all bootloader --location=mbr # Create partitions: 200 MB for boot, remaining for everything else. part /boot --size=200 --fstype ext3 part pv.01 --size=1 --grow # Create a single volume group volgroup vg pv.01 # Create a swap volume of "recommended size", a root volume of 100GB # and a database volume on the remaining space logvol swap --fstype swap --name=swap_vol --vgname=vg --recommended logvol / --fstype ext4 --name=root_vol --vgname=vg --size=100000 logvol /db --fstype ext4 --name=db_vol --vgname=vg --size=1 --grow ------------------------------------------------------------------------ Thanks in advance, Arun _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From linux at alteeve.com Fri Feb 26 00:11:27 2010 From: linux at alteeve.com (Digimer) Date: Thu, 25 Feb 2010 19:11:27 -0500 Subject: Using kickstart on large disks In-Reply-To: References: <433540.87104.qm@web32104.mail.mud.yahoo.com> Message-ID: <4B8711AF.2070303@alteeve.com> On 10-02-25 04:09 PM, Shabazian, Chip wrote: > Why not just create the /db volume in the %post? > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Arun > Sent: Thursday, February 25, 2010 12:32 PM > To: kickstart-list at redhat.com > Subject: Using kickstart on large disks > > Hi - > > I was wondering if you guys had some thoughts on an issue I'm running > into using kickstart to automate installs on intel x86 servers with > large disks (~16 TB). > > What I'm trying to achieve is simple: a root volume of 100GB, and a > database volume on all remaining space. > It appears however that anaconda is restricting logical volumes to 8TB, > even for ext4 partitions. > > I narrowed the problematic code down to storage/formats/fs.py where the > Ext4 file type extends via Ext3 from Ext2, in which I saw this line: > _maxSize = 8 * 1024 * 1024 > > Is there a reason for this limit to be inherited down to Ext4 partitions > as well? See my kickstart snippet below - the "/db" partition has the > --grow option, but it will not grow beyond 8TB due to the code above, > leaving nearly 8TB completely unused on the server. > > ------------------------------------------------------------------------ > clearpart --all > bootloader --location=mbr > > # Create partitions: 200 MB for boot, remaining for everything else. > part /boot --size=200 --fstype ext3 > part pv.01 --size=1 --grow > > # Create a single volume group > volgroup vg pv.01 > > # Create a swap volume of "recommended size", a root volume of 100GB > # and a database volume on the remaining space > logvol swap --fstype swap --name=swap_vol --vgname=vg --recommended > logvol / --fstype ext4 --name=root_vol --vgname=vg --size=100000 > logvol /db --fstype ext4 --name=db_vol --vgname=vg --size=1 --grow > ------------------------------------------------------------------------ > > Thanks in advance, > Arun That would be a work-around to Arun's problem without addressing the underlying issue. With single drives being 2TB now, it's an issue that deserves direct attention, I would think. Digi From Pablo.Iranzo at redhat.com Fri Feb 26 07:51:26 2010 From: Pablo.Iranzo at redhat.com (=?utf-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Fri, 26 Feb 2010 02:51:26 -0500 (EST) Subject: Using kickstart on large disks In-Reply-To: <19337752.271267170562196.JavaMail.iranzo@iranzo.usersys.redhat.com> Message-ID: <26070619.291267170679357.JavaMail.iranzo@iranzo.usersys.redhat.com> Hi Arun ----- "Arun" escribi?: > Hi - > > I was wondering if you guys had some thoughts on an issue I'm running > into using kickstart to automate installs on intel x86 servers with > large disks (~16 TB). > > What I'm trying to achieve is simple: a root volume of 100GB, and a > database volume on all remaining space. > It appears however that anaconda is restricting logical volumes to > 8TB, even for ext4 partitions. > > I narrowed the problematic code down to storage/formats/fs.py where > the Ext4 file type extends via Ext3 from Ext2, in which I saw this > line: > _maxSize = 8 * 1024 * 1024 > > Is there a reason for this limit to be inherited down to Ext4 > partitions as well? See my kickstart snippet below - the "/db" > partition has the --grow option, but it will not grow beyond 8TB due > to the code above, leaving nearly 8TB completely unused on the > server. http://www.redhat.com/rhel/compare/ See the section related to capabilities/limits, specially when it says that for EL5 limits is 8TB, but for 5.1 is 16TB, for bigger FS you'll need gfs. It's usual to have gfs in 'solo' mode for getting better performance for larger storage capabilities. Regards Pablo -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHC{SP,E,SS,DS,A} Senior Global Profesional Services Consultant Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain From maier at linux.vnet.ibm.com Fri Feb 26 10:35:14 2010 From: maier at linux.vnet.ibm.com (Steffen Maier) Date: Fri, 26 Feb 2010 11:35:14 +0100 Subject: Using kickstart on large disks In-Reply-To: <4B8711AF.2070303@alteeve.com> References: <433540.87104.qm@web32104.mail.mud.yahoo.com> <4B8711AF.2070303@alteeve.com> Message-ID: <4B87A3E2.4010804@linux.vnet.ibm.com> On 02/26/2010 01:11 AM, Digimer wrote: > On 10-02-25 04:09 PM, Shabazian, Chip wrote: >> Why not just create the /db volume in the %post? >> >> -----Original Message----- >> From: kickstart-list-bounces at redhat.com >> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Arun >> Sent: Thursday, February 25, 2010 12:32 PM >> Hi - >> >> I was wondering if you guys had some thoughts on an issue I'm running >> into using kickstart to automate installs on intel x86 servers with >> large disks (~16 TB). >> >> What I'm trying to achieve is simple: a root volume of 100GB, and a >> database volume on all remaining space. >> It appears however that anaconda is restricting logical volumes to 8TB, >> even for ext4 partitions. >> >> I narrowed the problematic code down to storage/formats/fs.py where the >> Ext4 file type extends via Ext3 from Ext2, in which I saw this line: >> _maxSize = 8 * 1024 * 1024 >> >> Is there a reason for this limit to be inherited down to Ext4 partitions >> as well? See my kickstart snippet below - the "/db" partition has the >> --grow option, but it will not grow beyond 8TB due to the code above, >> leaving nearly 8TB completely unused on the server. >> >> ------------------------------------------------------------------------ >> clearpart --all >> bootloader --location=mbr >> >> # Create partitions: 200 MB for boot, remaining for everything else. >> part /boot --size=200 --fstype ext3 >> part pv.01 --size=1 --grow >> >> # Create a single volume group >> volgroup vg pv.01 >> >> # Create a swap volume of "recommended size", a root volume of 100GB >> # and a database volume on the remaining space >> logvol swap --fstype swap --name=swap_vol --vgname=vg --recommended >> logvol / --fstype ext4 --name=root_vol --vgname=vg --size=100000 >> logvol /db --fstype ext4 --name=db_vol --vgname=vg --size=1 --grow >> ------------------------------------------------------------------------ >> >> Thanks in advance, >> Arun > > That would be a work-around to Arun's problem without addressing the > underlying issue. With single drives being 2TB now, it's an issue that > deserves direct attention, I would think. I think a discussion on this has at least started on anaconda-devel: https://www.redhat.com/archives/anaconda-devel-list/2010-January/msg00291.html Steffen Linux on System z Development IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Gesch?ftsf?hrung: Dirk Wittkopp Sitz der Gesellschaft: B?blingen Registergericht: Amtsgericht Stuttgart, HRB 243294 From twelvefortyfive at yahoo.com Sat Feb 27 00:28:30 2010 From: twelvefortyfive at yahoo.com (Arun) Date: Fri, 26 Feb 2010 16:28:30 -0800 (PST) Subject: Using kickstart on large disks In-Reply-To: Message-ID: <389787.2552.qm@web32101.mail.mud.yahoo.com> Thanks everyone for your replies. See my comments below: > (Shabazian, Chip) wrote: >> Why not just create the /db volume in the %post? Well, firstly I wanted to use the "logvol" option because it does a lot of work for you, but the main problem with a %post approach is that one of the RPMs that gets installed puts a lot of stuff into /db. I actually use a hack right now where that RPM uses lvextend & resize2fs to expand the volume to the full 16TB before installing stuff into it. > (Digimer) wrote: >> That would be a work-around to Arun's problem without addressing >> the underlying issue. With single drives being 2TB now, it's an >> issue that deserves direct attention, I would think. Thanks Digi, and agreed. I currently use the ugly workaround I mentioned above and it works fine, but the fix to anaconda seems really easy to me. More importantly, I feel that this is something that other folks will run into and a fix would save them a lot of headache. > (Pablo Iranzo G?mez) wrote: >> http://www.redhat.com/rhel/compare/ >> See the section related to capabilities/limits, specially when it >> says that for EL5 limits is 8TB, but for 5.1 is 16TB, for bigger FS >> you'll need gfs. It's usual to have gfs in 'solo' mode for getting >> better performance for larger storage capabilities. Thanks Pablo. I will look at GFS but my needs are fairly simple and don't really necessitate a cluster file system. With my current lvextend workaround described above, Ext4 is doing a great job with the 16TB partition. I just wish that anaconda/kickstart wouldn't limit Ext4 partitions to 8T. > (Steffen Maier) wrote: >> I think a discussion on this has at least started on anaconda-devel: >> https://www.redhat.com/archives/anaconda-devel-list/2010-January/msg00291.html Yeap that is exactly my problem, except that I'm using Ext4 and not XFS. I just wonder if the current 8TB limit is intentional (I'm no filesystem expert) or just an oversight when the Ext4 FS type was extended from Ext2. Arun