Pacemaker cluster resources are unable to mount EFS with EFS Mount helper

Solution Verified - Updated -

Issue

  • Unable to use efs filesystem type with ocf:heartbeat:Filesystem resource agent.
  • Creating a Filesystem resource with efs fstype in Pacmeaker triggers a failure to start the resource.

Example:

When starting as a cloned resource:

$ pcs resource create efs_fs Filesystem device='nfsshare:/' directory='/mnt/efs_fs' fstype='efs' clone interleave=true
$ cat /var/log/messages
------------------------------------->8--------------------------------
Dec  9 12:08:02 nodea Filesystem(efs_fs)[928948]: INFO: Running start for nfsshare:/ on /mnt/efs_fs
Dec  9 12:08:02 nodea Filesystem(efs_fs)[928948]: ERROR: DANGER! efs on nfsshare:/ is NOT cluster-aware!
Dec  9 12:08:02 nodea Filesystem(efs_fs)[928948]: ERROR: DO NOT RUN IT AS A CLONE!
Dec  9 12:08:02 nodea Filesystem(efs_fs)[928948]: ERROR: Politely refusing to proceed to avoid data corruption.
Dec  9 12:08:02 nodea pacemaker-execd[6845]: notice: efs_fs_start_0[928948] error output [ ocf-exit-reason:DANGER! efs on nfsshare:/ is NOT cluster-aware! ]
Dec  9 12:08:02 nodea pacemaker-execd[6845]: info: efs_fs start (call 83, PID 928948) exited with status 6 (execution time 114ms, queue time 0ms)
Dec  9 12:08:02 nodea pacemaker-controld[6848]: notice: Result of start operation for efs_fs on nodea: not configured
Dec  9 12:08:02 nodea pacemaker-controld[6848]: notice: nodea-efs_fs_start_0:83 [ ocf-exit-reason:DANGER! efs on nfsshare:/ is NOT cluster-aware!\n ]

When starting as a standalone resource:

$ pcs resource create efs_fs Filesystem device='nfsshare:/' directory='/mnt/efs_fs' fstype='efs'
Dec  9 12:10:49 nodea Filesystem(efs_fs)[930163]: INFO: Running start for nfsshare:/ on /mnt/efs_fs
Dec  9 12:10:49 nodea Filesystem(efs_fs)[930163]: ERROR: Couldn't find device [nfsshare:/]. Expected /dev/??? to exist
Dec  9 12:10:49 nodea pacemaker-execd[6845]: notice: efs_fs_start_0[930163] error output [ ocf-exit-reason:Couldn't find device [nfsshare:/]. Expected /dev/??? to exist ]
Dec  9 12:10:49 nodea pacemaker-execd[6845]: info: efs_fs start (call 102, PID 930163) exited with status 5 (execution time 274ms, queue time 0ms)
Dec  9 12:10:49 nodea pacemaker-controld[6848]: notice: Result of start operation for efs_fs on nodea: not installed

Environment

  • Red Hat Enterprise Linux Server 7, 8, 9 (with the High Availability Add On)- Pacemaker
  • AWS Virtual Machines
  • nfs
  • efs

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content