Bug#341452: lvm2: v2.02.00-1: breaks VGs: "device-mapper ioctl cmd 9 failed: Invalid argument"

[Wolfgang Weisselberg]

Alasdair G Kergon wrote 10 lines:
> On Wed, Nov 30, 2005 at 06:47:12PM +0100, Wolfgang Weisselberg wrote:

> > After upgrading to lvm2 2.02.00-1 and the required
> > libdevmapper1.02, the system was unable to complete booting,

> You should find that bug was fixed by libdevmapper 1.02.01 with lvm2 2.02.01.

Unfortunately, no, not with libdevmapper1.02 v2:1.02.02-1 and
                                                      ^
lvm2 v2.02.01-1.


$ vgscan
[OK]
$ vgchange -a y
[repeat many times:]
device-mapper: one of name or uuid must be supplied, cmd(12)
  device-mapper: table ioctl failed: Invalid argument
[finally]
device-mapper: one of name or uuid must be supplied, cmd(12)
  device-mapper: table ioctl failed: Invalid argument
  20 logical volume(s) in volume group "base_vg" now active
$

Of course dmsetup table shows the same old symptoms, the
names are there, but nothing's mapped to them, no
/dev/base_vg/*, ...


Unloading and reloading lvm-mod and dm-mod to start over.

$ /etc/init.d/lvm start
[many repeats of:]
device-mapper: one of name or uuid must be supplied, cmd(11)
  device-mapper: table ioctl failed: Invalid argument
  _deps: task run failed for (254:1)
  Failed to add device (254:1)
[finally]
device-mapper: one of name or uuid must be supplied, cmd(11)
  device-mapper: table ioctl failed: Invalid argument
  _deps: task run failed for (254:19)
  Failed to add device (254:19)
  20 logical volume(s) in volume group "base_vg" now active
$

Of course dmsetup table shows the same old symptoms, the
names are there, but nothing's mapped to them, no
/dev/base_vg/*, ...


Time to reopen the bug report?

-Wolfgang