package: lvm2-lockd version: 2.03.09-3
Hi. This is a relatively brief bug report, I'm tossing off in the middle of trying to get something working, and I apologize for not including a lot of details. The system where I can reproduce is several tunnels away from anything with email so I definitely cannot run reportbug. What appears to be happening is that if the volume group has an extent size greater than 256m (which appears to be the default initial size for lvmlock), it fails to create a lock space. My guess is that it's rounding down rather than up trying to create the volume or something. But I can consistently create a volume group with 256m extents and not with 1g extents. root@storage-a:~# vgcreate --shared --pvmetadatacopies=1 -s 1g raidvg /dev/sdb Enabling sanlock global lock Skipping global lock: lockspace not found or started Internal error: Unable to create new logical volume with no extents. Failed to create sanlock lv lvmlock in vg raidvg Failed to create internal lv. Failed to initialize lock args for lock type sanlock Volume group "raidvg" successfully removed root@storage-a:~# vgcreate --shared --pvmetadatacopies=1 -s 256m raidvg /dev/sd b Enabling sanlock global lock Skipping global lock: lockspace not found or started Logical volume "lvmlock" created. Volume group "raidvg" successfully created VG raidvg starting sanlock lockspace Starting locking. Waiting until locks are ready... If my guess is wrong and this is not obvious from code inspection, let me know what additional details would be useful. If I can get it without disrupting a production system I'll do that, but I don't have a lot of environments where sanlock is set up. --Sam
