I would look at the LVM metadata found in /etc/lvm/backup, or /etc/lvm/
archive to find out more about the pvmove volume. You can of course
edit the metadata by hand to achieve the result you want. Why the
initial problem occurred, I don't know... and it may be too late to
know. :(
brassow
On Nov 14, 2008, at 2:21 AM, Christian Völker wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
meanhwhile I did a "vgsplit" and the pvmove0 LV went together with one
LV to the new VG while the old VG seems to be ok now.
Looks like it is attached to this particular LV. Unfortunately, this
is
the largest LV and it would be hard to move the data over...
Any further ideas?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFJHTTz0XNIYlAXmzsRAqAPAJ9GZh5sto3GAg4qqmkEPVipA8TLUQCeODdZ
HvE8ErHDUJtI2MFROONaCt8=
=NGly
-----END PGP SIGNATURE-----
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
