Ron, my box reports the same rough number of “errors” as yours.
But one can’t count on that report being accurate anyway unless the filesystem is unmounted first… The inode / block count can change WHILE the e2fsck program is running, hence the discrepency.
If you want some peace of mind, you can force an FSCK to run at next boot by executing the command
tune2fs -C 31 /dev/md3
This will tell the file system that it has been mounted 31 times since the last check.
By default, the /dev/md3 count has the mandatory mount check counter set at 30.
After you set it to 31, the next reboot will force fsck to run.
MAKE SURE YOU USE CAPITAL C. Lower-case C does the opposite… it sets the max-mount-count to 31. :)
