1 <?xml version="1.0" encoding="UTF-8"?>
2 <refentry id="fms_log5">
4 <refentrytitle>fms.log</refentrytitle>
5 <manvolnum>5</manvolnum>
8 <refname>fms.log</refname>
9 <refpurpose>Records output from the fms command</refpurpose>
12 <title>Description</title>
13 <para>The <replaceable>fms.log</replaceable> file records the output generated by the <emphasis role="bold">fms</emphasis>
14 command. The output includes two numbers that can appear in a tape
15 device's entry in the <replaceable>/usr/afs/backup/tapeconfig</replaceable> file on the Tape
16 Coordinator machine to which the tape device is attached:</para>
20 <para>The capacity in bytes of the tape in the device.</para>
24 <para>The size in bytes of the end-of-file (EOF) marks (often referred to simply
25 as <emphasis>filemarks</emphasis>) that the tape device writes.</para>
29 <para>When transferring the numbers recorded in this file to the <replaceable>tapeconfig</replaceable>
30 file, adjust them as specified in <link linkend="tapeconfig5">tapeconfig(5)</link>, to improve Tape
31 Coordinator performance during dump operations.</para>
33 <para>If the <replaceable>fms.log</replaceable> file does not already exist in the current working
34 directory, the <emphasis role="bold">fms</emphasis> command interpreter creates it. In this case, the
35 directory's mode bits must grant the <computeroutput>rwx</computeroutput> (read, write, and execute)
36 permissions to the issuer of the command. If there is an existing file,
37 the command interpreter overwrites it, so the file's mode bits need to
38 grant only the <emphasis role="bold">w</emphasis> permission to the issuer of the <emphasis role="bold">fms</emphasis> command. The
39 <emphasis role="bold">fms</emphasis> command interpreter also writes similar information to the standard
40 output stream as it runs.</para>
42 <para>The file is in ASCII format. To display its contents, log onto the client
43 machine and use a text editor or a file display command such as the UNIX
44 <emphasis role="bold">cat</emphasis> command. By default, the mode bits on the <replaceable>fms.log</replaceable> file grant the
45 required <computeroutput>r</computeroutput> permission only to the owner (which is the local superuser
46 <computeroutput>root</computeroutput> by default).</para>
51 <para>The first few lines of the file provide a simple trace of the <emphasis role="bold">fms</emphasis>
52 command interpreter's actions, specifying (for example) how many blocks it
53 wrote on the tape. The final two lines in the file specify tape capacity
54 and filemark size in bytes, using the following format:</para>
57 Tape capacity is &lt;tape_size&gt; bytes
58 File marks are &lt;filemark_size&gt; bytes
63 <title>Examples</title>
64 <para>The following example of the fms.log file specifies that the tape used
65 during the execution of the <emphasis role="bold">fms</emphasis> command had a capacity of 2,136,604,672
66 bytes, and that the tape device writes filemarks of size 1,910,220 bytes.</para>
71 Tape capacity is 2136604672 bytes
72 File marks are 1910220 bytes
77 <title>See Also</title>
78 <para><link linkend="tapeconfig5">tapeconfig(5)</link>,
79 <link linkend="fms8">fms(8)</link></para>
83 <title>Copyright</title>
84 <para>IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.</para>
86 <para>This documentation is covered by the IBM Public License Version 1.0. It was
87 converted from HTML to POD by software written by Chas Williams and Russ
88 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.</para>