First off I have never had an SD card failure in using many Pi systems run 24/7. One for almost a year.
That being said this morning I found one system giving read/write errors and read only errors with lots of errors in the log. I figured I had lost an SD card but after a reboot all was fine. Not sure what happened but I had to pull the power as commands would not execute.
Anyhow when it came back up fine I decided to do a file check at the next boot so I put the /forcefsck file in and rebooted. I don't seem to see anywhere that it actually does this. I assume it does it before mounting R/W on the next boot. Here are the pertinent parts of dmesg
2.240976] mmc0: read SD Status register (SSR) after 3 attempts
[ 2.261965] mmc0: new high speed SDHC card at address aaaa
[ 2.269523] mmcblk0: mmc0:aaaa SU16G 14.8 GiB
[ 2.277019] mmcblk0: p1 p2
[ 2.351249] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.362156] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 2.370781] devtmpfs: mounted
[ 12.288007] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 34.161759] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 42.907205] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I don't see any mention of the file check being done. I also assume the FAT error can be ignored.
So how can I determine if the file check is actaully happening?
Also is there any downside to put a touch /forcefsck in rc.local to force a file check at each reboot?