A Filesystem cluster resource failed to stop despite no processes using it when Vormetric encryption was enabled

Solution Verified - Updated -

Issue

  • An ocf:heartbeat:Filesystem resource failed to stop even though no processes were using it. Vormetric encryption was enabled for the filesystem.

    Mar 18 09:07:30 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm; trying cleanup with TERM
Mar 18 09:07:30 node2 Filesystem(dataset_pdm)[31768]: INFO: No processes on /opt/datasets01_pdm were signalled. force_unmount is set to 'yes'
Mar 18 09:07:30 node2 Filesystem(dataset_pdm)[31768]: INFO: Running stop for /dev/DATASETvg_pdm/lv0l01 on /opt/datasets01_pdm
Mar 18 09:07:30 node2 Filesystem(dataset_pdm)[31768]: INFO: Trying to unmount /opt/datasets01_pdm
Mar 18 09:07:31 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm; trying cleanup with TERM
Mar 18 09:07:31 node2 Filesystem(dataset_pdm)[31768]: INFO: No processes on /opt/datasets01_pdm were signalled. force_unmount is set to 'yes'
Mar 18 09:07:32 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm; trying cleanup with TERM
Mar 18 09:07:32 node2 Filesystem(dataset_pdm)[31768]: INFO: No processes on /opt/datasets01_pdm were signalled. force_unmount is set to 'yes'
Mar 18 09:07:33 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm; trying cleanup with KILL
Mar 18 09:07:33 node2 Filesystem(dataset_pdm)[31768]: INFO: No processes on /opt/datasets01_pdm were signalled. force_unmount is set to 'yes'
Mar 18 09:07:34 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm; trying cleanup with KILL
Mar 18 09:07:34 node2 Filesystem(dataset_pdm)[31768]: INFO: No processes on /opt/datasets01_pdm were signalled. force_unmount is set to 'yes'nt is set to 'yes'
Mar 18 09:07:35 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm; trying cleanup with KILL
Mar 18 09:07:35 node2 Filesystem(dataset_pdm)[31768]: INFO: No processes on /opt/datasets01_pdm were signalled. force_unmount is set to 'yes'
Mar 18 09:07:36 node2 Filesystem(dataset_pdm)[31768]: ERROR: Couldn't unmount /opt/datasets01_pdm, giving up!
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [         (In some cases useful info about processes that use ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [         (In some cases useful info about processes that use ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [ ocf-exit-reason:Couldn't unmount /opt/datasets01_pdm; trying cleanup with TERM ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [ ocf-exit-reason:Couldn't unmount /opt/datasets01_pdm; trying cleanup with TERM ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [          the device is found by lsof(8) or fuser(1)) ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [          the device is found by lsof(8) or fuser(1)) ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [ umount: /opt/datasets01_pdm: target is busy. ]
Mar 18 09:07:36 node2 lrmd[26719]:  notice: dataset_pdm_stop_0:31768:stderr [ umount: /opt/datasets01_pdm: target is busy. ]
Mar 18 09:07:37 node2 crmd[28679]:  notice: Result of stop operation for dataset_pdm on node2: 1 (unknown error)

Environment

  • Red Hat Enterprise Linux 6, 7, or 8 (with the High Availability Add-on)
  • Pacemaker
  • A Vormetric-encrypted filesystem managed by a Filesystem cluster resource

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