RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1833837 - sanlock global vg creation can fail " init_vg_san write_resource gl error -28"
Summary: sanlock global vg creation can fail " init_vg_san write_resource gl error -28"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sanlock
Version: 8.2
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: 8.0
Assignee: David Teigland
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-11 00:33 UTC by Corey Marthaler
Modified: 2021-10-21 19:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 19:22:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)

Description Corey Marthaler 2020-05-11 00:33:20 UTC 
Description of problem:
[root@hayes-03 ~]# pvscan
  Skipping global lock: lockspace not found or started
  No matching physical volumes found
[root@hayes-03 ~]# dmsetup ls
No devices found

[root@hayes-03 ~]# vgcreate  --shared global /dev/sdb2
  Enabling sanlock global lock
  Skipping global lock: lockspace not found or started
  Physical volume "/dev/sdb2" successfully created.
  Logical volume "lvmlock" created.
  VG global init failed: -28
  Failed to initialize lock args for lock type sanlock
  Volume group "global" successfully removed

May 10 19:26:35 hayes-03 lvmlockd[2787]: 1589156795 WARNING: mixed block sizes physical 4096 logical 512 (using 4096) for /dev/mapper/global-lvmlock
May 10 19:26:35 hayes-03 lvmlockd[2787]: 1589156795 S lvm_global init_vg_san write_resource gl error -28 /dev/mapper/global-lvmlock

[root@hayes-03 ~]# pvscan
  Skipping global lock: lockspace not found or started
  PV /dev/sdb2                      lvm2 [223.31 GiB]
  Total: 1 [223.31 GiB] / in use: 0 [0   ] / in no VG: 1 [223.31 GiB]

[root@hayes-03 ~]# dmsetup ls
No devices found


Version-Release number of selected component (if applicable):
4.18.0-193.2.1.el8_2.x86_64

kernel-4.18.0-193.2.1.el8_2    BUILT: Mon May  4 09:57:10 CDT 2020
lvm2-2.03.08-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
lvm2-libs-2.03.08-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
lvm2-dbusd-2.03.08-3.el8    BUILT: Wed Mar 18 08:40:15 CDT 2020
lvm2-lockd-2.03.08-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
boom-boot-1.0-1.el8    BUILT: Fri Nov 29 05:18:30 CST 2019
device-mapper-1.02.169-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
device-mapper-libs-1.02.169-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
device-mapper-event-1.02.169-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
device-mapper-event-libs-1.02.169-3.el8    BUILT: Wed Mar 18 08:37:57 CDT 2020
device-mapper-persistent-data-0.8.5-3.el8    BUILT: Wed Nov 27 07:05:21 CST 2019
sanlock-3.8.0-2.el8    BUILT: Wed Jun 12 15:50:27 CDT 2019
sanlock-lib-3.8.0-2.el8    BUILT: Wed Jun 12 15:50:27 CDT 2019
Comment 1 Corey Marthaler 2020-05-11 00:44:20 UTC 
[root@hayes-03 ~]# systemctl status sanlock
â— sanlock.service - Shared Storage Lease Manager
   Loaded: loaded (/usr/lib/systemd/system/sanlock.service; disabled; vendor preset: disabled)
   Active: active (running) since Sun 2020-05-10 18:21:17 CDT; 1h 12min ago
 Main PID: 2768 (sanlock)
    Tasks: 6 (limit: 1647406)
   Memory: 41.4M
   CGroup: /system.slice/sanlock.service
           ├─2768 /usr/sbin/sanlock daemon
           └─2769 /usr/sbin/sanlock daemon

May 10 18:21:17 hayes-03.lab.msp.redhat.com systemd[1]: Starting Shared Storage Lease Manager...
May 10 18:21:17 hayes-03.lab.msp.redhat.com systemd[1]: Started Shared Storage Lease Manager.
Comment 2 David Teigland 2020-05-11 18:17:44 UTC 
Caused by mixed block sizes, and a difference between lvmlockd daemon and lvm client side in handling the mixed sizes.

fix in master
https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87
Comment 7 Corey Marthaler 2021-10-21 19:22:50 UTC 
Closing (CURRENTRELEASE). QA will reopen this if seen again.
Note You need to log in before you can comment on or make changes to this bug.