The nfslock="1" option in cluster service results in many /tmp/statd-xxxxxxx files that do not get removed in RHEL 5

Solution Unverified - Updated -

Environment

  • Red Hat Enterprise Linux Server 5 (with the High Availability and Resilient Storage Add Ons)
  • A /etc/cluster/cluster.conf file with a clustered service with the following attribute nfslock="1"

Issue

  • The nfslock="1" option in cluster service results in many /tmp/statd-xxxxxxx files that do not get removed

Resolution

These files are harmless and can be ignored. If they need to be removed, it is recommended they are only removed while the service is not running on that node. This issue is fixed in rgmanager-2.0.52-9.el5 or higher version.

Root Cause

The problem is if we drop into any of the 3 if statements at the beginning of the /usr/share/cluster/svclib_nfslock:nfslock_statd_notify() function, we return without removing $tmpdir.

Diagnostic Steps

If we change to nfslock="1" to nfslock="0" or remove this option then there is no file(s) created.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments