#3515 New lvm2-2.02.62-1.fc13 available to test minimum memory requirements for install
Closed: Fixed None Opened 14 years ago by jlaska.

[https://bugzilla.redhat.com/show_bug.cgi?id=559290 bug#559290] identified that LVM may be using more memory than expected during install. The result was that 512M system (common in virt) was no longer sufficient. A new [http://koji.fedoraproject.org/koji/buildinfo?buildID=161973 lvm2-2.02.62-1.fc13] is available that attempts to address some memory issues.

I believe install images are needed with this updated lvm2 to fully test the fix? This ticket is intended to track creation of one-off x86_64 install images containing the lvm2 package noted below.

{{{
--- Comment #36 from Alasdair Kergon agk@redhat.com 2010-03-15 15:06:57 EDT ---
Try:

Package: lvm2-2.02.62-1.fc13
Tag: dist-f13-updates-candidate
Status: complete
Built by: agk
ID: 161973
}}}


http://alt.fedoraproject.org/pub/alt/stage/13-Beta.TC0/Fedora/ Should sync over to serverbeach1 soon as well.

This is Branched as of 20100315 + anaconda-13.35-1.fc13 + lvm2-2.02.62-1.fc13

From inside the installer, if I run {{{lvm lvs --version}}} I get the following output:

{{{
LVM version: 2.02.61(1) (2010-02-15)
Library version: 1.02.44 (2010-02-15)
Driver version: 4.16.0
}}}

Does that mean the newer lvm2 isn't included? Or was the version string in the package not updated?

How did you initiate the installer and what steps did you take up until you ran the above command? I checked the compose logs and it does appear to have used the newer lvm2 rpm. I have not yet ran strings on it to see if the version didn't change.

sudo mount /srv/pungi/13-Alpha.TC0/13-Beta/Fedora/x86_64/os/images/install.img /mnt/ -o loop
[jkeating@compose-x86-01 lvm]$ strings /mnt/usr/sbin/lvm |grep 2.02
2.02.62(1) (2010-03-09)

It would appear that the lvm in the install.img file is 2.02.62 as it should be. So I'm now really curious how you started the installation.

Problem solved, pilot error. While testing, I forgot to add stage2= to point to the new install.img. Testing with the proper install.img yields the expected result

{{{
sh-4.1# lvm lvs --version
LVM version: 2.02.62(1) (2010-03-09)
Library version: 1.02.45 (2010-03-09)
Driver version: 4.16.0
}}}

Login to comment on this ticket.

Metadata