Security Analytics Appliance has gone into a file system check on the last reboot. The Index filesystem (DSINDEX) is a common file system that is checked. Is there any way to bypass file system check?
You can use tune2fs to see the different interval settings and find out when the next schedule check is supposed to happen.
tune2fs -l /dev/sdX1 will list all the file system parameters on the index partition or any ext formatted partition. If you look for the "Check Interval" you will notice the default is 6 months. This also lists the "Next check after:" which means if the date listed is in the past, then the file system check will occur on next reboot. If the date listed is in the future still, you are OK. This is per device, so if there are multiple index mounts, you will want to check each one.
Also pay attention to the "Mount Count". Maximum Mount Count default is between 20-30 mounts. If Mount Count is higher than the maximum, it will also perform a system check on next boot.
You can use tune2fs to change all of these values, but it is not recommended to permanently change them.
If the mount count is getting close to maximum, set the maximum mount count to 0 using the -c option "tune2fs -c 0 /dev/sdX1". Or if you do not want to disable that, set the maximum to 100. Just change it back when done.
You can also disable the file system check using the command "tune2fs -i 0 /dev/sdX1" Once you are done with reboots, change it back to the default of 6 months, "tune2fs -i 6m /dev/sdX1".
Note: -i is for interval-between-checks, d result in days, m in months, and w in weeks.
You can change the system last check date too using the command "tune2fs -T YYYYMMDD[[HHMM]SS] /dev/sdX1".
Note: -T is for time-last-checked, YYYYMMDD[[HHMM]SS] is the international date format. To make changes to the “Next Check After” parameter, you can make changes to time-last-checked and interval-between-checks to reflect the desired date.
Imported Document ID: 000027228
Subscribing will provide email updates when this Article is updated. Login is required.