Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
Subject: application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
Subject: X Windows problem (xauth)
Subject: Upgrading openoffice 1 1 rpm
Subject: FTP: connection refused
Subject: FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
Subject: broadcom network interface
make mrproper
Couldn 't open PID file /var/run/named/named pid Permission denied
sendmail configuration on redhat
kernel 2 6 and /dev/sound/mixer not found
Subject: Promise 378 controller
Subject: Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
Subject: Lotus Notes under Wine
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
/etc/security/limits conf question
Intel E/1000 driver
rpm database corrupt
Command stream end of file while reading
qla2300 modules
 
Cannot create an LVM disk layout on top of SW RAID in kickstart

Cannot create an LVM disk layout on top of SW RAID in kickstart

2007-06-06       - By Paul Krizak

 Back
Reply:     1     2     3     4     5     6     7  

On a related note, I'm also bumping into the 256GB logical volume size
limit...and I don't see a way to create a volume group with 16MB extents
in anaconda.  Anybody else figured out a way to do this?

At this point I'd actually be fine doing all the partitioning in %pre
and then just instructing anaconda to use the partitions I create, but I
don't know what LVM/partitioning commands are available in BusyBox
inside anaconda.

Paul Krizak                         5900 E. Ben White Blvd. MS 625
Advanced Micro Devices              Austin, TX  78741
Linux/Unix Systems Engineering      Phone: (512) 602-8775
Silicon Design Division             Cell:  (512) 791-0686


Paul Krizak wrote:
> Using a partition layout like this in our kickstart file:
>
> zerombr yes
> clearpart --all --initlabel
> part raid.01 --size 512 --asprimary --ondisk sda
> part raid.11 --size 1 --grow --ondisk sda
> part raid.02 --size 512 --asprimary --ondisk sdb
> part raid.12 --size 1 --grow --ondisk sdb
> raid /boot --level 1 --fstype=ext3 --device=md0 raid.01 raid.02
> raid pv.01 --level 1 --device=md1 --spares 0 raid.11 raid.12
> volgroup privg pv.01
> logvol / --vgname=privg --name=lv_root --fstype=ext3 --size=16384
> logvol /tmp --vgname=privg --name=lv_tmp --fstype=ext3 --size=1024 --grow
> logvol swap --vgname=privg --name=lv_swap --fstype=ext3 --size=32768
>
> I get the following crash/stack trace:
>
> Traceback (most recent call last):
>  File "/usr/bin/anaconda", line 1089, in ?
>    intf.run(id, dispatch, configFileData)
>  File "/usr/lib/anaconda/text.py", line 471, in run
>    dispatch.gotoNext()
>  File "/usr/lib/anaconda/dispatch.py", line 157, in gotoNext
>    self.moveStep()
>  File "/usr/lib/anaconda/dispatch.py", line 225, in moveStep
>    rc = apply(func, self.bindArgs(args))
>  File "/usr/lib/anaconda/packages.py", line 488, in turnOnFilesystems
>    thefsset.createLogicalVolumes(instPath)
>  File "/usr/lib/anaconda/fsset.py", line 1293, in createLogicalVolumes
>    entry.device.setupDevice(chroot)
>  File "/usr/lib/anaconda/fsset.py", line 1861, in setupDevice
>    raise SystemError, "lvcreate failed for %s" %(self.name,)
> SystemError: lvcreate failed for lv_tmp
>
> I've tried reordering the logvol statements, tried different sizes, etc.
> to no avail.  Suspecting that the --grow was at fault, I removed it and
> found that it works fine!
>
> ::sigh::
>
> I'd imagine that other people out there have had a similar problem.  How
>  have you worked around anaconda's bug that it crashes when specifying
> --grow in this fashion?
>
> My first knee-jerk reaction is to set /tmp artificially small (say 1GB)
> and then have the %post install detect this, expand the logvol to full
> size, then resize2fs the /tmp filesystem.  But this is clunky and not
> really something I want to do.
>


--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list