Incorrect alarms from File System Unmount rule when using bind mounts (4375368)

False alarms from File System Unmount rule when using bind mounts.

Bind mounts are used to bind a file location to another mount; example:

• NFS mount (fstab): hostname:/share /nfsmount nfs rw,bg,hard,vers=3,proto=tcp,timeo=600,intr,rsize=65536,wsize=65536,_netdev 0 0
• Bind mount (fstab): /nfsmount/dir /bindmount/dir none defaults,bind 0 0

The mount is active, but alarms are triggered:

File System Unmount

Some file systems, which should be mounted on hostname, are not mounted properly. It might cause an application startup failure or a data loss issue. The following file system should be mounted during system boot. For details, please check:

/nfsmount/dir (mount point:/bindmount/dir).

WORKAROUND

None.

STATUS

Enhancement request FOGGENERAL-I-284 to support monitoring bind mounts has been submitted to development for consideration in a future release of the Foglight Cartridge for Infrastructure.