Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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

New PR based on suggestions by QE: https://github.com/ClusterLabs/resource-agents/pull/1878

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