lkml.org 
[lkml]   [2007]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectlvm 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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-01-09 01:37    [W:0.554 / U:0.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site