From: Zdenek Kabelac <firstname.lastname@example.org>
To: LVM general discussion and development <email@example.com>,
Subject: Re: [linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine
Date: Tue, 27 Mar 2018 12:22:28 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Dne 27.3.2018 v 11:12 Xen napsal(a):
> Gang He schreef op 27-03-2018 7:55:
>> I just reproduced a problem from the customer, since they did virtual
>> disk migration from one virtual machineï¿½ to another one.
>> According to your comments, this does not look like a LVM code problem,
>> the problem can be considered as LVM administer misoperation?
> Counterintuitively, you must remove the PV from the VG before you remove the
> (physical) disk from the system.
> Yes that is something you can often forget doing, but as it stands resolving
> the situation often becomes a lot harder when you do it in reverse.
> Ie. removing the disk first and then removing the PV from the VG is a lot harder.
IMO 'vgreduce --removemissing' doesn't look to me like a real rocket science.
Of course if the space on a missing PV has been in-use with some LVs - it gets
a bit more complex - but still as long as you don't care about data adding
'--force' option should usually help (although there can be some room for
improvement - but every coding takes its time - and there are not to many
hands working on this...)
next prev parent reply other threads:[~2018-03-27 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 8:30 [linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine Gang He
2018-03-23 9:04 ` Xen
2018-03-26 6:04 ` Gang He
2018-03-26 10:17 ` Fran Garcia
2018-03-26 10:23 ` Fran Garcia
2018-03-27 5:55 ` Gang He
2018-03-27 8:32 ` Zdenek Kabelac
2018-03-28 2:09 ` Gang He
2018-03-27 9:12 ` Xen
2018-03-27 10:22 ` Zdenek Kabelac [this message]
2018-03-27 10:27 ` Xen
2018-03-27 22:17 ` Zdenek Kabelac
2018-03-28 10:08 ` Xen
2018-03-26 10:46 ` Zdenek Kabelac
2018-05-18 4:56 ` Gang He
2018-03-26 11:33 ` Xen
2018-10-16 20:59 ` [linux-lvm] [lvm-devel] " Nir Soffer
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).