Purpose
Records output from the fms command
Description
The fms.log file records the output generated by the fms command. The output includes two numbers that can appear in a tape device's entry in the /usr/afs/backup/tapeconfig file on the Tape Coordinator machine to which the tape device is attached:
When transferring the numbers recorded in this file to the tapeconfig file, adjust them as specified on the reference page for the tapeconfig file, to improve Tape Coordinator performance during dump operations.
If the fms.log file does not already exist in the current working directory, the fms command interpreter creates it. In this case, the directory's mode bits must grant the rwx (read, write, and execute) permissions to the issuer of the command. If there is an existing file, the command interpreter overwrites it, so the file's mode bits need to grant only the w permission to the issuer of the fms command. The fms command interpreter also writes similar information to the standard output stream as it runs.
The file is in ASCII format. To display its contents, log onto the client machine and use a text editor or a file display command such as the UNIX cat command. By default, the mode bits on the fms.log file grant the required r permission only to the owner (which is the local superuser root by default).
Output
The first few lines of the file provide a simple trace of the fms command interpreter's actions, specifying (for example) how many blocks it wrote on the tape. The final two lines in the file specify tape capacity and filemark size in bytes, using the following format:
Tape capacity is tape_size bytes File marks are filemark_size bytes
Examples
The following example of the fms.log file specifies that the tape used during the execution of the fms command had a capacity of 2,136,604,672 bytes, and that the tape device writes filemarks of size 1,910,220 bytes.
fms test started wrote 130408 blocks Tape capacity is 2136604672 bytes File marks are 1910220 bytes
Related Information