Bug#458833: lvm2: vgrename behaves badly with /dev/vg_name when having conflicting vg names

[Mike Hommey]

Package: lvm2
Version: 2.02.26-1+b1
Severity: normal

This happened to me today because I was trying to access a virtual
machine's volume group. It had the same name as the one on the host
system, so any lvm command would issue a warning saying it would take
into account the one it created, which is just fine as a behaviour.

The problem is that at this point, I tried to rename the conflicting vg
with vgrename its-UUID a_new_name.

That worked fine, except that it just renamed /dev/vg_old_name to
/dev/vg_new_name, which means all lvs in the other vg named vg_old_name
are now in /dev/vg_new_name.

Note that when it can't rename the vg (it happened the first time
because the virtual machine's disk was read-only), it still renames the
/dev/vg_old_name directory.

Mike

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lvm2 depends on:
ii  libc6                     2.7-5          GNU C Library: Shared libraries
ii  libdevmapper1.02.1        2:1.02.20-2    The Linux Kernel Device Mapper use
ii  libncurses5               5.6+20071215-1 Shared libraries for terminal hand
ii  libreadline5              5.2-3          GNU readline and history libraries
ii  libselinux1               2.0.15-2+b1    SELinux shared libraries
ii  libsepol1                 2.0.3-1+b1     Security Enhanced Linux policy lib

lvm2 recommends no packages.

-- debconf information excluded