Cannot create an LVM disk layout on top of SW RAID in kickstart
"Paul Krizak" <[email protected]> Tue, 05 Jun 2007 14:24:01 -0500
| Newsgroups | gmane.linux.redhat.release.taroon.general |
|---|---|
| Message-ID | <[email protected]> |
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.
--
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
--
Taroon-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/taroon-list