LVM2 migration on 2.4.24 troubles - prepare for 2.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

i tried to migrate my system to LVM2 on 2.4 before migration to 2.6
to avoid troubles with LVM. I got the newest device-mapper/LVM2 tools
and installed them alongside with a patched kernel and dm-mod.

When i try to "vgchange -ay" with device-mapper/LVM2 i get all of my lv's
except one! All my snapshots are also corrupt (I use snapshots intensively).

Back to LVM1 was no problem - everything running and Ok. On another
machine without snapshots moving to dm/LVM2 on 2.4.24 was no problem.

Are there incompatibilities regarding snapshots with LVM1/2?

The lvm level 9 log of vgscan/vgchange is attached (bz2 compressed).
Here comes the kernel output while activating with LVM2/dm:

$ rmmod lvm-mod
lvm -- Module successfully deactivated

$ modprobe dm-mod
device-mapper: 4.0.5-ioctl (2003-11-18) initialised: dm@uk.sistina.com

$ vgscan --mknodes
  Reading all physical volumes.  This may take a while...
  Found volume group "vg00" using metadata type lvm1
  Found volume group "vg01" using metadata type lvm1
  9 logical volume(s) in volume group "vg00" now active
  47 logical volume(s) in volume group "vg01" now active

$ vgchange -ay
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Invalid/corrupt snapshot
device-mapper: Could not create kcopyd client
device-mapper: error adding target to table
  0 logical volume(s) in volume group "vg00" now active
  15 logical volume(s) in volume group "vg01" now active

Regards
Axel Reinhold
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFACaOrHQ9JwE2bDw0RArlLAJ46zy1AxFvlwA0CxqCQmAH7HbstwgCgjsQa
ZPW1XYtXcwHsZAXdVE+o12c=
=6d3r
-----END PGP SIGNATURE-----

Attachment: lvm.log.bz2
Description: application/bz2


[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux