To resolve this issue, recreate the corrupted files/directoy in vRealize Log Insight.
- Determine which files/directory is corrupt from the /storage/var/loginsight/cassandra.log file.
For example:
In this case, the corruption is in the vimevent_context directory which is available at /storage/core/loginsight/cidata/cassandra/data/logdb/ folder.
- Move the vimevent_context from the location /storage/core/loginsight/cidata/cassandra/data/logdb to a new directory.
Note: If you are not confident using mv command, use copy command to take the backup and then remove the desired directory.
md /storage/core/loginsight/corrupted_files
mv /storage/core/loginsight/cidata/cassandra/data/logdb/vimevent_context /storage/core/loginsight/corrupted_files
- Create a new directory with the same name vimevent_context in the location /storage/core/loginsight/cidata/cassandra/data/logdb.
md /storage/core/loginsight/cidata/cassandra/data/logdb/vimevent_context
- Run this command to start the logInsight service:
service logInsight start
Note: This starts the cassandra service first and then the logInsight daemon.
To fix the File system corruption, perform these steps:
- Run this command to stop the vRealize Log Insight Service:
service loginsight stop
- Run this command to see the mount files:
mount
Note: The output will show /dev/* and mount points.
- Run this command to unmount the /storage/core:
umount /storage/core
- Run this command to check/repair the filesystem:
/sbin/fsck device
Notes:
- Replace device with actual device name.
- It may take hours for a bigger disk, plan the downtime accordingly.