The ccm fs_check command is responsible for checking that the metadata, cache, and archive portions of a database are consistent.
In Release 7.1 and later, the ccm fs_check command performs an additional check on the existence of archives for static versioned objects.
- If a versioned object was recently checked in, but does not have an archive, the archiver has not yet processed the object. This is normal behavior and is not an error.
- If an object was checked in without an archive for a longer time than specified by a user, it is a possible problem because the archiver might not be running. You receive a warning.
- The ccm fs_check command has a new -c|-cutoff cutofftime option. Any object versions checked in before the cutoff time but not yet archived produce a warning. The default cutoff is two days, -2:0:0:0. You receive a warning for any files that were checked in earlier than the day before yesterday but have not yet been archived.
- After the archive is checked, the check for unused archive files now uses less memory than in Release 7.0 and earlier.