From: Jason Heiss <jheiss-lvm@ofb.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Export an LV?
Date: Mon, 27 Jun 2005 16:59:04 -0700 [thread overview]
Message-ID: <20050627235904.GA16989@ofb.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
OK, having looked through the code for vgreduce it's clear that the
important parts of the --removemissing code aren't getting called for
some reason. Probably some sort of bug, I'll try to look at it later if
I get a chance.
In the meantime, I've put the two drives for the LV I'm trying to move
back into my server. Now I'd like to find out if there is a right way
to move an LV to another machine. As before I've got a VG with two
LVs. One LV is on one physical drive, the other LV is spread over two
drives. I'd like to move the second LV to another system. I don't see
an obvious way to do that. vgexport/vgimport would allow me to move the
entire VG, but I don't want to do that. I could use vgreduce to kick
the two associated physical volumes out of the VG, but I don't see any
way to reconstruct the volume on the new machine with my data intact.
Is there a way to do this? (I'm guessing no, but thought I'd check.)
Jason
--
Jason Heiss
PGP key: http://ofb.net/~jheiss/jheiss.pgp.txt
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-06-27 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 23:59 Jason Heiss [this message]
2005-06-28 13:48 ` [linux-lvm] Export an LV? Stefan Paletta
2005-06-28 14:47 ` Alasdair G Kergon
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 16:16 Jason Heiss
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=20050627235904.GA16989@ofb.net \
--to=jheiss-lvm@ofb.net \
--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.