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

Filesystem: dont sleep during stop-action when there are no processes to kill, and only use force argument for network filesystems after sending kill_signals

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhel-9.6
    • rhel-9.5
    • resource-agents
    • None
    • resource-agents-4.10.0-65.el9
    • No
    • None
    • sst_high_availability
    • ssg_filesystems_storage_and_HA
    • 13
    • 26
    • 8
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None

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

      Stop Pacemaker cluster with 10 filesystem resources. It takes 23s when no processeses are using the filesystems, while it only took 2-3s for RHEL9.2.

       

      QE suggested that -f might be used for term_signals for network filesystems.

      What is the impact of this issue to you?

      Slower stop of Pacemaker cluster, and possibly too early forced unmounts of network filesystems.

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

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1. Create a network filesystem.
      2.  
      3.  

      Expected results

      No sleep during the stop-action when no processes are accessing the filesystem, and only trying to umount the filesystem with the force-parameter after sending kill_signals.

      Actual results

      Sleep a couple of seconds even when no processes are using the filesystem, and uses umount -f for all tries to unmount the device.

            rhn-engineering-oalbrigt Oyvind Albrigtsen
            rhn-engineering-oalbrigt Oyvind Albrigtsen
            Oyvind Albrigtsen Oyvind Albrigtsen
            Cluster QE Cluster QE
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: