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

can 'vgchange --setpersist' fail more gracefully when run on node w/o WE PR

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

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • rhel-10.2
    • lvm2
    • None
    • None
    • None
    • 1
    • rhel-storage-lvm
    • 2
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • LVM Sprint 8
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      Can we have the persist cmd attempts warn about PR not being started or started on another node, like the other examples given.

      kernel-6.12.0-165.el10    BUILT: Fri Nov 28 09:08:39 AM CET 2025
      lvm2-2.03.36-1.el10    BUILT: Sat Oct 25 04:42:32 AM CEST 2025
      lvm2-libs-2.03.36-1.el10    BUILT: Sat Oct 25 04:42:32 AM CEST 2025
      
      # This is the other node's WE PR key
      [root@virt-499 ~]# vgchange --persist read persist_VG
      Device /dev/sda: registered keys: 0x8fac11130e680d3d
      Device /dev/sdb: registered keys: 0x8fac11130e680d3d
      Device /dev/sdc: registered keys: 0x8fac11130e680d3d
      Device /dev/sdd: registered keys: 0x8fac11130e680d3d
      Device /dev/sde: registered keys: 0x8fac11130e680d3d
      Device /dev/sda: reservation: WE holder 0x8fac11130e680d3d
      Device /dev/sdb: reservation: WE holder 0x8fac11130e680d3d
      Device /dev/sdc: reservation: WE holder 0x8fac11130e680d3d
      Device /dev/sdd: reservation: WE holder 0x8fac11130e680d3d
      Device /dev/sde: reservation: WE holder 0x8fac11130e680d3d
      
      # More graceful VG metadata altering cmd attempts:
      [root@virt-499 ~]# vgchange --yes -ay persist_VG
        persistent reservation is not started.
        Cannot access VG persist_VG without persistent reservation.
      
      [root@virt-499 ~]# vgchange --persist start persist_VG
       persistent reservation is started by another key (0xbbbde59275afc630)
      
      [root@virt-499 ~]# vgreduce persist_VG /dev/sde
       persistent reservation is not started.
      
      
      # Less graceful VG metadata altering cmd attempts
      [root@virt-499 ~]# vgchange --setpersist n persist_VG
       Error writing device /dev/sda at 11264 length 2560.
       WARNING: bcache_invalidate: block (1, 0) still dirty.
       Failed to write metadata to /dev/sda.
       Failed to write VG persist_VG.
      
      [root@virt-499 ~]# vgchange --setpersist y persist_VG
       Error writing device /dev/sda at 11264 length 2560.
       WARNING: bcache_invalidate: block (0, 0) still dirty.
       Failed to write metadata to /dev/sda.
       Failed to write VG persist_VG.
      

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

                Created:
                Updated:
                Resolved: