Usually when there is a problem, the filesystem mounts itself read-only:
[449551.919049] EXT3-fs (dm-2): error: ext3_journal_start_sb: Detected aborted journal [449551.919056] EXT3-fs (dm-2): error: remounting filesystem read-only
Now I tried to catch that using monitoring via SNMP that we have in place anyway, but it didn't:
# snmpwalk -c public -v 2c localhost HOST-RESOURCES-MIB::hrFSTable SNMP table: HOST-RESOURCES-MIB::hrFSTable ... HOST-RESOURCES-MIB::hrFSAccess.11 = INTEGER: readWrite(1) HOST-RESOURCES-MIB::hrFSAccess.12 = INTEGER: readWrite(1) ***
It seems to show the configured, not the current state.
Is there any other way to catch this, preferably using SNMP, without resorting to actually having to write a file and check the outcome?
- OS: SLES11-SP3
- Kernel 3.0.101