From: Spelic <spelic@shiftmail.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Losing one of various PVs in VG
Date: Thu, 25 Nov 2010 19:39:57 +0100 [thread overview]
Message-ID: <4CEEAD7D.5040506@shiftmail.org> (raw)
Hi all,
I am planning our new storage system.
I would like the ability to migrate LVs between the various RAID arrays
we have.
This would require we have a PV per array and all PVs under the same VG.
Now I'm wondering what happens if we lose an array: all data on all
arrays will be lost because the VG is lost?
I did spot one way to prevent this:
I could create one VG per PV, then just before the migration I would do
vgmerge between the two VGs source and destination, then perform
migration of the LV with pvmove, then wait for it to complete (by not
sending it to background probably), then do vgsplit to return to initial
condition.
It's quite complex and unconvenient though. Also if I forget to wait
completion for pvmove and/or I forget to do vgsplit, and then one of the
two array fails, I would probably lose data from both.
What do you suggest?
Thanks for your help
next reply other threads:[~2010-11-25 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 18:39 Spelic [this message]
2010-12-03 16:43 ` [linux-lvm] Losing one of various PVs in VG Stuart D. Gathman
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=4CEEAD7D.5040506@shiftmail.org \
--to=spelic@shiftmail.org \
--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).