DescriptionOyvind Albrigtsen
2023-05-16 10:06:41 UTC
+++ This bug was initially created as a clone of Bug #2189243 +++
+++ This bug was initially created as a clone of Bug #2189242 +++
Description of problem:
On high-end production workload systems with huge amount of (write-cache) RAM and big XFS file systems >= 8 TiB the unmount operation itself may take longer then 10 minutes on each attempt (even if it fails as processes are still utilizing it). In case login shells of users sit on the Filesystem resource then these do no respond to SIGTERM, just to SIGHUP so when resource is stopping it deliberately fails to unmount and causes stop operation to fail/timeout.
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-61.el7_9.15.x86_64
How reproducible:
repeatedly
Steps to Reproduce:
1. Create large filesystem resource with potentially long dirty unmount cycles (+- 30 minutes) with login shells on it
2. re-login during the long stop operation (login shells on any HA FS RA managed file system does not fail all standard FS RA stop operation)
Actual results:
unmount fails resulting stop operation to fail
Expected results:
unmount succeeds
Additional info:
https://github.com/ClusterLabs/resource-agents/pull/1868
Comment 2Oyvind Albrigtsen
2023-07-12 10:43:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6312