lvm backwards compatability

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

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: lvm backwards compatability
    • From: Alasdair G Kergon <[email protected]>

• Prev by Date: Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
• Next by Date: Re: D-Link DFE-580TX adapter problems
• Previous by thread: RE: [PATCH] x86_64 ioapic: check_timer_pin Don't add_pin_to_irq if it is already there.
• Next by thread: Re: lvm backwards compatability
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]