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 #1095943 +++
Description of problem:
The Filesystem resource agent uses fuser to kill processes accessing the mount point during the stop operation. fuser is known to block when unresponsive nfs mounts are present on the system. This will cause completely unrelated Filesystem resources to fail during their stop operation (which in turn causes the node to be fenced).
We can avoid this by adopting similar logic used in the rgmanager fs-lib.sh based agents found in this issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1014298
How reproducible:
100%
Steps to Reproduce:
1. mount a nfs share
2. kill the nfs server
3. attempt to use the Filesystem resource to manage a completely unrelated mount point. Have a process like 'tail' open a file on the mount point before stopping the resource so the mountpoint will be busy.
Actual results:
Filesystem agent blocks for the entire duration of the nfs timeout period during the fuser detection of the pids accessing the mount point
Expected results:
Filesystem should not block because of the unresponsive nfs mount. The agent should be able to kill the 'tail' pid allowing the filesystem to unmount properly.
Created attachment 893797[details]
unit test
This script tests the new force_unmount=safe option the patch adds.
unit-test by running the following.
./bind-test.sh /usr/lib/ocf/resource.d/heartbeat/Filesystem
-- Vossel
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, 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://rhn.redhat.com/errata/RHBA-2015-0351.html