From: Axel Reinhold <lvm@freakout.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 migration on 2.4.24 troubles - prepare for 2.6
Date: Mon Jan 19 12:11:02 2004 [thread overview]
Message-ID: <6154.1074373571@bongo.freakout.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
-----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 #2: lvm.log.bz2 --]
[-- Type: application/bz2, Size: 100490 bytes --]
next reply other threads:[~2004-01-19 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 12:11 Axel Reinhold [this message]
2004-01-19 12:19 ` [linux-lvm] LVM2 migration on 2.4.24 troubles - prepare for 2.6 Alasdair G Kergon
2004-01-20 17:06 ` Axel Reinhold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6154.1074373571@bongo.freakout.de \
--to=lvm@freakout.de \
--cc=linux-lvm@redhat.com \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.