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

if two hosts end up with the same host_id being set, should 'persist read|check|start|stop' behave?

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Undefined Undefined
    • None
    • rhel-10.2
    • lvm2
    • None
    • None
    • None
    • rhel-storage-lvm
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      Obviously, this is an invalid and unsupported configuration, in fact I stumbled on this randomly and it took me a bit to figure out why this was failing. Both nodes ended up with the same host_id, if that happens how should these commands behave? Could they be more informative?

      kernel-6.12.0-184.el10    BUILT: Thu Jan 15 06:39:19 AM EST 2026
      lvm2-2.03.36-2.el10    BUILT: Wed Jan  7 09:47:23 AM EST 2026
      lvm2-libs-2.03.36-2.el10    BUILT: Wed Jan  7 09:47:23 AM EST 2026
      lvm2-lockd-2.03.36-2.el10    BUILT: Wed Jan  7 09:47:23 AM EST 2026
      
      
      [root@megatest-03 ~]# vgchange --persist read persist_VG
      Device /dev/sdc: registered keys: 0x1000000000000524
      Device /dev/sda: registered keys: 0x1000000000000524
      Device /dev/sde: registered keys: 0x1000000000000524
      Device /dev/sdb: registered keys: 0x1000000000000524
      Device /dev/sdd: registered keys: 0x1000000000000524
      Device /dev/sdc: reservation: WE holder 0x1000000000000524
      Device /dev/sda: reservation: WE holder 0x1000000000000524
      Device /dev/sde: reservation: WE holder 0x1000000000000524
      Device /dev/sdb: reservation: WE holder 0x1000000000000524
      Device /dev/sdd: reservation: WE holder 0x1000000000000524
      [root@megatest-03 ~]# echo $?
      0
      
      [root@megatest-03 ~]# vgchange --persist check persist_VG
        key for local host is registered: 0x1000000000000524
        reservation WE for local host
        PR is started.
      [root@megatest-03 ~]# echo $?
      0
      
      [root@megatest-03 ~]# vgchange --persist stop persist_VG
        lvmpersist: stop persist_VG failed to unregister our key 0x1000000000000524 from /dev/sdc.
        lvmpersist: stop persist_VG failed to unregister our key 0x1000000000000524 from /dev/sda.
        lvmpersist: stop persist_VG failed to unregister our key 0x1000000000000524 from /dev/sde.
        lvmpersist: stop persist_VG failed to unregister our key 0x1000000000000524 from /dev/sdb.
        lvmpersist: stop persist_VG failed to unregister our key 0x1000000000000524 from /dev/sdd.
        persistent reservation stop failed: lvmpersist command error
      [root@megatest-03 ~]# echo $?
      5
      [root@megatest-03 ~]# vgchange --persist start persist_VG
        lvmpersist: start persist_VG failed to reserve /dev/sdc.
        persistent reservation start failed: lvmpersist command error.
      [root@megatest-03 ~]# echo $?
      5
      
      
      # This is what a what a check should look like, with proper host_ids:
      #  "key for local host is not registered"
      [root@megatest-03 ~]# vgchange --persist check persist_VG
        key for local host is not registered (host_id 990)
        key for other host is registered: 0x10000000000003ff
        reservation WE for other host
        PR is not started.
      [root@megatest-03 ~]# echo $?
      5
      

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

                Created:
                Updated:
                Resolved: