On Sun, Oct 09, 2011 at 01:08:20AM +0400, [email protected] wrote: > Dear all, > > I have a strange Problem on a two node cluster, with an DRBD volume. > Each time I try to create a new logical volume I see this error: > > c-r0212034:~# lvcreate -L 2G --name foo rep > device-mapper: reload ioctl failed: Invalid argument > Aborting. Failed to activate new LV to wipe the start of it. > > I red a lot about this in the internet, but unfortunately it was not > possible to fix it till yet. > > Please find some helpful output below: > # pvcreate /dev/drbd0 > Physical volume "/dev/drbd0" successfully created > # vgcreate rep /dev/drbd0 > Volume group "rep" successfully created > # pvscan > PV /dev/sda2 VG pve lvm2 [930.82 GB / 836.00 MB free] > PV /dev/drbd0 VG rep lvm2 [699.98 GB / 699.98 GB free] > # pvs > PV VG Fmt Attr PSize PFree > /dev/dm-3 rep lvm2 a- 699.98G 699.98G > /dev/sda2 pve lvm2 a- 930.82G 836.00M > > LVM-Filter in lvm.conf: filter = ["a|sd.*|", "a|drbd.*|", "r|.*|"]
.... > #device/dev-io.c:439 Opened /dev/dm-3 RW O_DIRECT > #device/dev-io.c:134 /dev/dm-3: block size is 4096 bytes > #label/label.c:160 /dev/dm-3: lvm2 label detected > #cache/lvmcache.c:1133 Duplicate PV ayC0bjchgYw0zf2ye3nTDIYbn3qjLwge on > /dev/drbd0 - using dm /dev/dm-3 Ooops. It's not using drbd0, but dm-3 :-( Either your filter is not what you think it is (maybe you have an other filter line in the config, and for some reason that one is active, and not the one you'd like). Or you simply have to remove the LVM cache and re-scan. vgscan -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
