Skip to contentSkip to conversation

lvm backwards compatability

DISCUSSION Dave Jones 2 participants 3 messages Jan 8, 2007 – Jan 9, 2007

lore
Share & tools
lore

Dave Jones

author
#0 lore raw

Did backwards compatability with old LVM metadata break intentionally in 2.6.19 ? I have a volume that mounts just fine in 2.6.18, but moving to 2.6.19 gets me this..

Huge memory allocation (size 2392064020) rejected - metadata corruption? Out of memory. Requested 2392064020 bytes.
Failed to read extents from /dev/sdb
Huge memory allocation (size 2392064020) rejected - metadata corruption? Out of memory. Requested 2392064020 bytes.
Failed to read extents from /dev/sdb
Huge memory allocation (size 2392064020) rejected - metadata corruption? Out of memory. Requested 2392064020 bytes.
Failed to read extents from /dev/sdb
Huge memory allocation (size 2392064020) rejected - metadata corruption? Out of memory. Requested 2392064020 bytes.
Failed to read extents from /dev/sdb
Volume group "vg01" not found
2 logical volume(s) in volume group "VolGroup00" now active

This volume was created a few years ago, (circa Fedora Core 2).

Dave

Signature · 1 line
http://www.codemonkey.org.uk
#1 lore raw
Quoted 3 lines · Dave Jones

Did backwards compatability with old LVM metadata break intentionally in 2.6.19 ? I have a volume that mounts just fine in 2.6.18, but moving to 2.6.19 gets me this..

No - and at first sight that's not a kernel device-mapper problem.

Please grab some diagnostics:
run the lvmdump script (present in the newest packages) or from here:

http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/LVM2/scripts/lvm_dump.sh?content-type=text/plain&cvsroot=lvm2

with the -a and -m flags.

[NB If you use dm-crypt and have userspace device-mapper < 1.02.13 you need to remove the encryption keys from the 'dmsetup' output by hand.]

Alasdair

Signature · 1 line
[email protected]
author
#2 lore raw
Quoted 11 lines · Alasdair G Kergon
Quoted 3 lines · Dave Jones

Did backwards compatability with old LVM metadata break intentionally in 2.6.19 ? I have a volume that mounts just fine in 2.6.18, but moving to 2.6.19 gets me this..

No - and at first sight that's not a kernel device-mapper problem.

Please grab some diagnostics:
run the lvmdump script (present in the newest packages) or from here:

http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/LVM2/scripts/lvm_dump.sh?content-type=text/plain&cvsroot=lvm2

pilot error. got this working now.

thanks,

Dave

Signature · 1 line
http://www.codemonkey.org.uk