OM VERSION: 8.0 SP5
It doesn't seem possible to write compliance rule that verifies mount points in /etc/fstab. When I view /etc/fstab in a live server browse, I see the
Name = storage device path (i.e. /dev/sda or hostname:/some/path)
Value 1 = local mount point (i.e. /opt/bladelogic/storage)
Value 2 = filesystem type (i.e. nfs)
Value 3 = mount options
Value 4 = dump frequency
Value 5 = pass num
This is what I would expect to see for the /etc/fstab file.
When I tried to create a compliance rule, I am unable to check the storage device path. The fstab.gm grammar file saves each entry record identified by the local mount point, so even though it displays properly in a live browse, the value of the storage device path is lost. The local mount point assumes the value of "Name" and "Value 1", and the "Path" value in a compliance rule is the configuration object path (i.e. /etc/fstab//\/opt\/bladelogic\/storage). All of the other values correspond to their column in /etc/fstab. The only value missing is the storage device path.
When I add one of the config file lines to a BLPackage, the storage device path is stored as "Value 0". This is not a value that can be referenced in a compliance rule.
the fstab.gm grammar file provided by BMC looks like:
--- BEGIN fstab.gm ---
# JBoland, 4/21/03 - Written to parse the /etc/fstab file on HPUX and Linux
# Sekhar, 12/9/05 - The format is as follows
# fs_spec fs_file fs_vfstype fs_mntops fs_freq fs_passno
# Using fs_file (mount point) as the key
VAL [^\t\n ]*
WS [\n\t ]*
comment COMMENT $save_as_comment $0
record VAL WS VAL WS VAL WS VAL WS VAL WS VAL \
$new_field $0 $new_field $2 $new_field $4 \
$new_field $6 $new_field $8 $new_field $10 \
add $write_record $TAB
--- END fstab.gm ---
The problem is the line "$save_record $2" in the record. This is what is causing the local mount point to be the reference name in the compliance template. I can obviously change the file to read "$save_record $0" and fix my problem, but what would that do to snapshots and BSARA ETLs? I can't imagine that the change WOULD NOT break those functions.
This obviously isn't limited to NFS devices, as local devices (i.e. /dev/sda) would be defined in the first column of /etc/fstab.
Has anyone else run into this problem? Has anyone figured out how to write a compliance rule for /etc/fstab to verify a local mount point and its storage device?