On Mon, Jan 08, 2007 at 06:01:11PM -0500, Dave Jones wrote:
> 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
--
[email protected]
-
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/
[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]
