Kostas Georgiou wrote:
On Wed, Apr 11, 2007 at 07:08:53PM +0300, Janne Blomqvist wrote:
On Wed, Apr 11, 2007 at 11:34:42AM -0400, Derek Yuen wrote:
Try changing the --fstype from "physical volume (LVM)" to something like
ext3. This looks like an old anaconda/kickstart bug that still isn't
fixed.
You're right, an fstype like that is nonsensical, and the installation
manual clearly states that ext2, ext3 and swap are the only allowed
values (I guess it's just ignored if it's invalid). It seems that
anaconda is clever enough to set the correct partition id (8e) for LVM
physical volumes without any --fstype option. I changed it, and did
some other minor cleanup ('=' instead of ' ' for options etc.), but
still I have the same problem. Now the partitioning section of my
kickstart looks like
clearpart --all --initlabel
part /boot --fstype=ext3 --size=100 --asprimary
part pv.01 --size=1 --grow
volgroup vg01 pv.01
logvol / --vgname=vg01 --fstype=ext3 --size=15000 --name=rootLV
logvol swap --vgname=vg01 --fstype=swap --recommended --name=swapLV
logvol /tmp --vgname=vg01 --fstype=ext3 --size=5000 --name=tmpLV
logvol /scratch --vgname=vg01 --fstype=ext3 --size=40000 --name=scratchLV
#logvol /scratch --vgname=vg01 --fstype=ext3 --size=1 --grow --name=scratchLV
If I switch the commented line to the other /scratch (the one with
--grow) it doesn't work anymore.
I guess I have to put some lvextend + resize2fs (or whatever the right
incantations were) snippet into the %post section if I can't get it to
work any other way. :(
The following works fine for me, not much of a difference though.
clearpart --all --drives sda
part /boot --fstype ext3 --size=256 --ondisk=sda
part pv.00 --size=15000 --ondisk=sda --grow
volgroup rootvg pv.00
logvol / --fstype ext3 --name=rootvol --vgname=rootvg --size=1024
logvol /var --fstype ext3 --name=varvol --vgname=rootvg --size=4096
logvol /usr --fstype ext3 --name=usrvol --vgname=rootvg --size=6144
logvol /tmp --fstype ext3 --name=tmpvol --vgname=rootvg --size=1024
logvol swap --fstype swap --name=swap0vol --vgname=rootvg --size=2048
logvol /srv/localstage --fstype ext3 --name=lstagevol --vgname=rootvg
--size=128 --grow
Kostas Georgiou
I've had problems with the --grow in combination with --maxsize.
For example, in the kickstart file:
clearpart --all --initlabel
part /boot --fstype="ext3" --size=128
part /tmp --fstype="ext3" --grow --maxsize=1024 --size=512
part / --fstype="ext3" --grow --maxsize=17408 --size=14080
part swap --fstype="swap" --recommended
part /var --fstype="ext3" --grow --size=1536
I have a 25 gig disk and have found that the / partition grows to all
remaining space on the disk and all the other partitions stay at the
value set in --size.
I verified that the syntax was correct by using the installer to
partition the disk and it created the same thing, but the / partition
ended up being about 21g.
This looks broken to me. I've had to resort to only using --grow on one
partition, which is kind of irritating.
Hugh
_______________________________________________
rhelv5-list mailing list
[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/rhelv5-list
