linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Possible Bug vgrename
Date: Mon, 21 Jun 2021 21:00:00 +0100	[thread overview]
Message-ID: <20210621200000.GA21390@agk.fab.redhat.com> (raw)
In-Reply-To: <20210621194823.GA32112@redhat.com>

On Mon, Jun 21, 2021 at 02:48:23PM -0500, David Teigland wrote:
> On Mon, Jun 21, 2021 at 11:32:12AM -0700, N wrote:
> > Is there a way to temporarily rename (without actually renaming) the volume
> > groups (i.e. like setting a mask for the volume group names), or is there a
> > way to force vgrename to actually make the change even if there is an
> > existing conflict (preferably without a reboot)?
> You can set a device filter the vgrename command so it only sees the
> devices with the VG you want to change, and won't see devices with the
> duplicate name.
> vgrename --config 'devices/filter=["a|/dev/...|", "r|.|"]' vg1 vg2

And look at how the 'vgimportclone' shell script uses filters and
other techniques to set up a segregated environment in which to
modify a VG that isn't being used on the machine.

As extra protection sometimes, you can also tell a command not to talk to 
the kernel dm subsystem by using '--driverloaded n'.

Alasdair

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


      reply	other threads:[~2021-06-21 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 18:32 [linux-lvm] Possible Bug vgrename N
2021-06-21 19:48 ` David Teigland
2021-06-21 20:00   ` Alasdair G Kergon [this message]

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=20210621200000.GA21390@agk.fab.redhat.com \
    --to=agk@redhat.com \
    --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).