-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.5
-
None
-
resource-agents-4.10.0-65.el9
-
No
-
None
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
13
-
26
-
8
-
False
-
-
None
-
None
-
Requested
-
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
- Create a network filesystem.
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.
- is depended on by
-
RHEL-59576 Filesystem: try umount first during stop-action, and avoid potential "Argument list too long" for force_unmount=safe
- In Progress