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

lvmlockd global lock fencing may be wrong

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

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 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
    • None

      What were you trying to do that didn't work?

      If a host fails while holding the global lock, lvmlockd will fence the host (using PR), but the VG that's fenced will be the VG holding the global lock.  This VG doesn't represent the devices the host was actually writing while holding the global lock.  It seems like this needs to be fixed, but it's not yet clear how this case should be handled.

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?:

      Steps to reproduce

      1.  
      2.  
      3.  

      Expected results

      Actual results

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

                Created:
                Updated: