-
Title
File System Unmount rule is firing for mounted file systems -
Description
Getting false alarms from the File System Unmount rule.
Some file systems, which should be mounted on hostname.fqdn.local, are not mounted properly. It might cause the application startup failure or data loss issue. The following file system should be mounted during system boot.
The list includes an LVM filesystem that is currently mounted. -
Cause
The rule will trigger an alarm if entries in FSTAB and MTAB are not an exact match; examples:- LVM logical volumes not defined with /dev/mapper/* format in FSTAB.
- Mount point includes a trailing slash in FSTAB.
-
Resolution
Unix FileSystem Mounting – This type of monitoring would ensure FSTAB and MTAB have exact same entries.
FSTAB lists out filesystems which are to be mounted at boot-time.
MTAB list the actual/current filesystems which are mounted. If MTAB is missing entries, this means that a filesystem is not currently mounted causing an application to not start up or a potential data loss.
The fstab configuration file needs to be updated to match.
For LVM devices, please use the filesystem entry from /dev/mapper/your-vg-lvm instead of the LV Path from lvdisplay command for the fstab.
-
Defect ID
FOGGENERAL-I-8 -
Additional Information
Enhancement/Idea FOGGENERAL-I-8 was logged for the following request:
Modify how the UnixAgentPlus compares mount points so a trailing slash doesn't cause a file system to be falsely reported as unmounted.