Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-47253

global lockspace isn't being properly started/created

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • rhel-10.0
    • sanlock
    • lvm2-2.03.24-4.el10
    • None
    • None
    • sst_logical_storage
    • ssg_filesystems_storage_and_HA
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Requested
    • None
    • x86_64
    • None

      # RHEL10.0  (BROKEN)
       
      kernel-6.10.0-0.rc5.12.el10    BUILT: Wed Jun 26 07:38:37 AM CEST 2024
      lvm2-2.03.23-1.el10    BUILT: Wed Feb 21 06:12:28 AM CET 2024
      lvm2-libs-2.03.23-1.el10    BUILT: Wed Feb 21 06:12:28 AM CET 2024
      sanlock-3.9.0-3.el10    BUILT: Tue Jun 25 01:02:49 AM CEST 2024
      sanlock-lib-3.9.0-3.el10    BUILT: Tue Jun 25 01:02:49 AM CEST 2024
       
      [root@virt-241 ~]# systemctl start sanlock
      [root@virt-241 ~]# systemctl start lvmlockd
       
      [root@virt-241 ~]# systemctl status sanlock
      â sanlock.service - Shared Storage Lease Manager
           Loaded: loaded (/usr/lib/systemd/system/sanlock.service; disabled; preset: disabled)
          Drop-In: /usr/lib/systemd/system/service.d
                   ââ10-timeout-abort.conf
           Active: active (running) since Thu 2024-07-11 23:39:36 CEST; 33s ago
          Process: 12726 ExecStart=/usr/sbin/sanlock daemon (code=exited, status=0/SUCCESS)
         Main PID: 12728 (sanlock)
            Tasks: 6 (limit: 4708)
           Memory: 13.6M (peak: 14.0M)
              CPU: 32ms
           CGroup: /system.slice/sanlock.service
                   ââ12728 /usr/sbin/sanlock daemon
                   ââ12729 /usr/sbin/sanlock daemon
       
      Jul 11 23:39:36 virt-241.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting sanlock.service - Shared Storage Lease Manager...
      Jul 11 23:39:36 virt-241.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started sanlock.service - Shared Storage Lease Manager.
       
      [root@virt-241 ~]# systemctl status lvmlockd
      â lvmlockd.service - LVM lock daemon
           Loaded: loaded (/usr/lib/systemd/system/lvmlockd.service; disabled; preset: disabled)
          Drop-In: /usr/lib/systemd/system/service.d
                   ââ10-timeout-abort.conf
           Active: active (running) since Thu 2024-07-11 23:39:45 CEST; 9s ago
             Docs: man:lvmlockd(8)
         Main PID: 12740 (lvmlockd)
            Tasks: 3 (limit: 4708)
           Memory: 5.1M (peak: 5.1M)
              CPU: 24ms
           CGroup: /system.slice/lvmlockd.service
                   ââ12740 /usr/sbin/lvmlockd --foreground
       
      Jul 11 23:39:45 virt-241.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting lvmlockd.service - LVM lock daemon...
      Jul 11 23:39:45 virt-241.cluster-qe.lab.eng.brq.redhat.com lvmlockd[12740]: [D] creating /run/lvm/lvmlockd.socket
      Jul 11 23:39:45 virt-241.cluster-qe.lab.eng.brq.redhat.com lvmlockd[12740]: 1720733985 lvmlockd started
      Jul 11 23:39:45 virt-241.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started lvmlockd.service - LVM lock daemon.
       
      [root@virt-241 ~]# /usr/tests/sts-rhel10.0/lvm2/bin/qe_lvmconf2 -Ke
      Setting use_lvmlockd to enable
      Setting lvmlocal.conf host_id to 1811
      [root@virt-241 ~]# vgcreate --shared   devfile_VG /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh
        Enabling sanlock global lock
        Logical volume "lvmlock" created.
        Volume group "devfile_VG" successfully created
        VG devfile_VG starting sanlock lockspace
        Starting locking.  Waiting until locks are ready...
       
      [root@virt-241 ~]# vgs devfile_VG
        Reading VG devfile_VG without a lock.
        VG         #PV #LV #SN Attr   VSize    VFree   
        devfile_VG   8   0   0 wz--ns <479.97g <479.72g
       
      [root@virt-241 ~]# dmsetup ls
      devfile_VG-lvmlock      (253:2)
       
      [root@virt-241 ~]# sanlock gets -h 1
      [root@virt-241 ~]# sanlock status
      daemon ce4b4d6d-3262-4706-9d70-ecfc288e970c.virt-241.cl
      p -1 helper
      p -1 listener
      p -1 status
       
      [root@virt-241 ~]# vgremove devfile_VG
        Global lock failed: check that global lockspace is started
       
       
       
      # RHEL9.4  (WORKS)
       
      kernel-5.14.0-472.el9    BUILT: Thu Jun 27 11:01:32 PM CEST 2024
      lvm2-2.03.23-2.el9    BUILT: Sat Feb  3 01:10:34 AM CET 2024
      lvm2-libs-2.03.23-2.el9    BUILT: Sat Feb  3 01:10:34 AM CET 2024
      sanlock-3.9.1-1.el9    BUILT: Mon Jan 22 10:12:36 PM CET 2024
      sanlock-lib-3.9.1-1.el9    BUILT: Mon Jan 22 10:12:36 PM CET 2024
       
      [root@virt-009 ~]# systemctl start sanlock
      [root@virt-009 ~]# systemctl start lvmlockd
      [root@virt-009 ~]# systemctl status sanlock
      â sanlock.service - Shared Storage Lease Manager
           Loaded: loaded (/usr/lib/systemd/system/sanlock.service; disabled; preset: disabled)
           Active: active (running) since Thu 2024-07-11 23:48:39 CEST; 8s ago
          Process: 36686 ExecStart=/usr/sbin/sanlock daemon (code=exited, status=0/SUCCESS)
         Main PID: 36687 (sanlock)
            Tasks: 6 (limit: 25002)
           Memory: 16.2M
              CPU: 29ms
           CGroup: /system.slice/sanlock.service
                   ââ36687 /usr/sbin/sanlock daemon
                   ââ36688 /usr/sbin/sanlock daemon
       
      Jul 11 23:48:39 virt-009.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting Shared Storage Lease Manager...
      Jul 11 23:48:39 virt-009.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started Shared Storage Lease Manager.
      Jul 11 23:48:39 virt-009.cluster-qe.lab.eng.brq.redhat.com sanlock[36687]: sanlock daemon started 3.9.1 host 4e629918-07b0-4bd5-865c-2e6c59c55692.virt-009.cl (>
       
      [root@virt-009 ~]# 
      [root@virt-009 ~]# 
      [root@virt-009 ~]# systemctl status lvmlockd
      â lvmlockd.service - LVM lock daemon
           Loaded: loaded (/usr/lib/systemd/system/lvmlockd.service; disabled; preset: disabled)
           Active: active (running) since Thu 2024-07-11 23:48:43 CEST; 21s ago
             Docs: man:lvmlockd(8)
         Main PID: 36695 (lvmlockd)
            Tasks: 3 (limit: 25002)
           Memory: 2.4M
              CPU: 37ms
           CGroup: /system.slice/lvmlockd.service
                   ââ36695 /usr/sbin/lvmlockd --foreground
       
      Jul 11 23:48:43 virt-009.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting LVM lock daemon...
      Jul 11 23:48:43 virt-009.cluster-qe.lab.eng.brq.redhat.com lvmlockd[36695]: [D] creating /run/lvm/lvmlockd.socket
      Jul 11 23:48:43 virt-009.cluster-qe.lab.eng.brq.redhat.com lvmlockd[36695]: 1720734523 lvmlockd started
      Jul 11 23:48:43 virt-009.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started LVM lock daemon.
      [root@virt-009 ~]# /usr/tests/sts-rhel10.0/lvm2/bin/qe_lvmconf2 -Ke
      -bash: /usr/tests/sts-rhel10.0/lvm2/bin/qe_lvmconf2: No such file or directory
      [root@virt-009 ~]# /usr/tests/sts-rhel9.4/lvm2/bin/qe_lvmconf2 -Ke
      Setting use_lvmlockd to enable
      Setting lvmlocal.conf host_id to 126
      [root@virt-009 ~]# vgcreate --shared   devfile_VG /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh
        Enabling sanlock global lock
        Physical volume "/dev/sda" successfully created.
        Physical volume "/dev/sdb" successfully created.
        Physical volume "/dev/sdc" successfully created.
        Physical volume "/dev/sdd" successfully created.
        Physical volume "/dev/sde" successfully created.
        Physical volume "/dev/sdf" successfully created.
        Physical volume "/dev/sdg" successfully created.
        Physical volume "/dev/sdh" successfully created.
        Logical volume "lvmlock" created.
        Volume group "devfile_VG" successfully created
        VG devfile_VG starting sanlock lockspace
        Starting locking.  Waiting until locks are ready...
      [root@virt-009 ~]# vgs devfile_VG
        VG         #PV #LV #SN Attr   VSize    VFree   
        devfile_VG   8   0   0 wz--ns <479.97g <479.72g
       
      [root@virt-009 ~]# dmsetup ls
      devfile_VG-lvmlock      (253:2)
       
      [root@virt-009 ~]# sanlock gets -h 1
      s lvm_devfile_VG:126:/dev/mapper/devfile_VG-lvmlock:0 
      h 126 gen 1 timestamp 9676 LIVE
       
      [root@virt-009 ~]# sanlock status
      daemon 4e629918-07b0-4bd5-865c-2e6c59c55692.virt-009.cl
      p -1 helper
      p -1 listener
      p 36695 36695
      p -1 status
      s lvm_devfile_VG:126:/dev/mapper/devfile_VG-lvmlock:0
       
      [root@virt-009 ~]# vgremove devfile_VG
        Volume group "devfile_VG" successfully removed
      
      

            teigland@redhat.com David Teigland
            cmarthal@redhat.com Corey Marthaler
            David Teigland David Teigland
            Cluster QE Cluster QE
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: