A POSX lock on a gfs2 filesystem is acquired before the cluster node has been fenced and waiting node ignores process signals
Issue
- A POSX lock on a gfs2 filesystem is acquired before the cluster node has been fenced. Shouldn't the POSIX lock be acquired ONLY after the cluster node is fenced?
- The node that is trying to acquire the POSIX lock on a gfs2 filesystem (and is waiting) seems to ignore the signals SIGTERM and SIGINT that are sent to the process.
Environment
- Red Hat Enterprise Linux Server 6, 7, 8 (with the High Availability Add On and Resilient Storage Add Ons)
- A Global Filesystem 2(
gfs2
)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.