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. :(
--
Janne Blomqvist
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
