posix lock fcntl calls failing against GFS2 file system with ENOSYS and "dlm_controld lockspace <lockspace> plock disabled" in logs in a RHEL 6 Resilient Storage cluster

Solution Unverified - Updated -

Issue

  • dlm_controld.log shows "dlm_controld lockspace plock disabled"
Jul 22 02:55:57 dlm_controld lockspace mqm_log plock disabled our sig 54100 nodeid 2 sig 40023
  • An application is failing to get posix locks against a GFS2 file system, with ENOSYS being returned, and the logs show plocks being disabled
  • Sometimes AM-Q stops working, and we see an error in the IO error in the logs complaining about Function not implemented when trying lock the lockfile on the shared storage, this cause neither of the AM-Q instances to start.
  • An strace of our application shows fcntl against a file on GFS2 returning ENOSYS (Function not implemented)
fcntl(93, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=1}) = -1 ENOSYS (Function not implemented)

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the Resilient Storage Add On
  • Using POSIX locking (fcntl) within a DLM lockspace or GFS2 filesystem

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.