ccm fs_check

This topic contains information about the ccm fs_check command.
ccm fs_check   [-d|-dir directory_path] [-f|-fix] [object_spec...]
               [-t|-type type][-v|-verbose]
               [-e|-empty_skip] [-u|-unused_skip]
               [-nd|-no_duplicates] [-w|-windows]
               [-nb|-null_byte][-z|-zero_counts]

Description and uses

Use the ccm fs_check command to check the consistency of a Rational® Synergy database file system. By default, the ccm fs_check command checks that:

Checking all the files in the cache and archive areas takes time and memory resources, and might be suppressed using the -u|-unused option.

Run ccm fs_check to check your entire database. This command can be used regularly to reduce the disk space taken up by cache files. However, as the check can take a long time on large databases, you can perform a quicker check by checking only specific types of objects. Use the -t option to check only objects of the specified type. Or you can check a list of objects using object_specs (for example, using query results). You cannot use both the -t option and a list of objects. If you check only objects of the specified type, checking for unused cache and archive entries are suppressed.

Direct the output to a file so that you can examine the results.

If unexpected or extra files or archive entries are found, they are reported individually and summarized at the end. However, such cases are not counted as errors and do not cause ccm fs_check to fail with a non-zero exit status. The -fix option to ccm fs_check does not remove these extra entries. Doing so might lead to data loss in cases where you have created such files manually for your own purposes. Or where you have restored a file system and metadata backup taken at slightly different times. Contact IBM® Rational Software Support for assistance in removing unwanted extra cache and archive entries.

All users can perform this operation. However, they must be in the ccm_admin role to perform the -fix option.

Options and arguments

-d|-dir directory_path

Specifies the directory into which inconsistent archive entries are written. By default, these files are written to database_path/st_root/tmp/check.

-e|-empty_skip

Suppresses warnings about empty files for static object versions.

This warning might also be suppressed for individual object versions, by creating a Boolean attribute deliberately_empty with the value TRUE on the object versions for which you want to suppress the warnings.

-f|-fix

Fixes some simple errors, including the following errors:

-nd|-noduplicates

Specifies to skip checks for duplicate archive entries. Use this option to reduce the memory resources used when checking large databases that might otherwise fail due to lack of memory. Since it reduces the strength of archive checking, only use when necessary.

-nb|-null_byte

Checks in the source attribute for null (0x00) bytes. Generates a warning message when objects of type ascii and subtypes of ascii contain null bytes.

-t|-type type

Specifies the type of objects to check.

You cannot use this option with object_spec. Using this option implies the -u|-unused_skip option.

-u|-unused_skip

Specifies to skip checks for extra files and entries in the cache and archive files. This option does not remove or delete files or entries.

-v|-verbose   

Generates more detailed information about each error. The errors report:

-w|-windows

Suppresses a warning message given when files differ only in carriage return characters.

-z|-zero_counts

Causes all counts to be printed, including those counts with zero values. This information can be useful when another program is analyzing the output of fs_check.

object_spec

Provides a list of objects to check. You can use query results for this argument.

You cannot use this argument with the -t option. Using this option implies the -u|-unused_skip option.

Example

Check the file system consistency of the database and provide detailed output information.

$ ccm fs_check -v


Feedback