From: "Christian Völker" <chrischan@knebb.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove --abort does nothing
Date: Fri, 14 Nov 2008 09:21:07 +0100 [thread overview]
Message-ID: <491D34F3.7030108@knebb.de> (raw)
In-Reply-To: <361513C7-BBE2-45D0-A6BA-F42E6219706A@redhat.com>
-----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-----
next prev parent reply other threads:[~2008-11-14 8:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 9:30 [linux-lvm] pvmove --abort does nothing Christian Völker
2008-11-13 10:24 ` Jonathan Brassow
2008-11-13 10:29 ` Christian Völker
2008-11-13 10:37 ` Jonathan Brassow
2008-11-13 10:49 ` Christian Völker
2008-11-13 13:44 ` Christian Völker
2008-11-14 8:21 ` Christian Völker [this message]
2008-11-14 14:53 ` [linux-lvm] Moving Xen LV to image and mounting the image Chris Edwards
2008-11-14 15:27 ` Jonathan Brassow
2008-11-14 15:35 ` Greg Freemyer
2008-11-14 15:44 ` Chris Edwards
2008-11-14 15:48 ` Jonathan Brassow
2008-11-14 16:02 ` Chris Edwards
2008-11-14 16:19 ` Greg Freemyer
2008-11-14 16:24 ` Chris Edwards
2008-11-14 16:37 ` Jonathan Brassow
2008-11-14 16:52 ` Chris Edwards
2008-11-14 17:26 ` Jonathan Brassow
2008-11-14 18:35 ` Chris Edwards
2008-11-14 21:19 ` Jonathan Brassow
2008-11-14 15:48 ` Stuart D. Gathman
2008-11-14 15:25 ` [linux-lvm] pvmove --abort does nothing Jonathan Brassow
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=491D34F3.7030108@knebb.de \
--to=chrischan@knebb.de \
--cc=linux-lvm@redhat.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.