From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] removing a PV to split a volume group
Date: Sun, 24 Sep 2006 13:44:34 -0400 [thread overview]
Message-ID: <1159119874.5445.4.camel@pc.ilinx> (raw)
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
I had to do some maintenance on my VG so added a new PV. I now have two
PVs in my VG with several LVs each of which is wholly on single PV (i.e.
no LV has PEs from both disks.
I now want to separate the PVs into self-contained VGs such that the VG
on each does not reference the other PV.
How can I go about this? It seems that as soon as I remove an "unused"
PV from a VG it fails to start up again, probably because I need the
--partial switch. But how do I fix up the VG so that I don't need the
--partial switch without destroying the PV that I want to remove?
Thanx,
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2006-09-24 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1159119874.5445.4.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).