Starting the File Server processes

Start either the fs process or, if you want to run the Demand-Attach File Server, the dafs process. The fs process consists of the File Server, Volume Server, and Salvager (fileserver, volserver and salvager processes). The dafs process consists of the Demand-Attach File Server, Volume Server, Salvage Server, and Salvager (dafileserver, davolserver, salvageserver, and dasalvager processes). For information about the Demand-Attach File Server and to see whether or not you should run it, see Appendix C, The Demand-Attach File Server.

  1. Issue the bos create command to start the fs process or the dafs process. The commands appear here on multiple lines only for legibility.

    • If you are not planning on running the Demand-Attach File Server, create the fs process:

         # ./bos create  <machine name> fs fs /usr/afs/bin/fileserver   \
                         /usr/afs/bin/volserver /usr/afs/bin/salvager  \
                         -noauth   
      
    • If you are planning on running the Demand-Attach File Server, create the dafs process:

         # ./bos create  <machine name> dafs dafs /usr/afs/bin/dafileserver   \
                         /usr/afs/bin/davolserver /usr/afs/bin/salvageserver \
                         /usr/afs/bin/dasalvager -noauth   
      

    Sometimes a message about Volume Location Database (VLDB) initialization appears, along with one or more instances of an error message similar to the following:

       FSYNC_clientInit temporary failure (will retry)   
    

    This message appears when the volserver process tries to start before the fileserver process has completed its initialization. Wait a few minutes after the last such message before continuing, to guarantee that both processes have started successfully.

    You can verify that the fs or dafs process has started successfully by issuing the bos status command. Its output mentions two proc starts.

    • If you are not running the Demand-Attach File Server:

         # ./bos status <machine name> fs -long -noauth
      
    • If you are running the Demand-Attach File Server:

         # ./bos status <machine name> dafs -long -noauth
      
  2. Your next action depends on whether you have ever run AFS file server machines in the cell:

    • If you are installing the first AFS server machine ever in the cell (that is, you are not upgrading the AFS software from a previous version), create the first AFS volume, root.afs.

      For the partition name argument, substitute the name of one of the machine's AFS server partitions (such as /vicepa).

         # ./vos create  <machine name> <partition name> root.afs   \
                         -noauth   
      

      The Volume Server produces a message confirming that it created the volume on the specified partition. You can ignore error messages indicating that tokens are missing, or that authentication failed.

    • If there are existing AFS file server machines and volumes in the cell, issue the vos syncvldb and vos syncserv commands to synchronize the VLDB with the actual state of volumes on the local machine. To follow the progress of the synchronization operation, which can take several minutes, use the -verbose flag.

         # ./vos syncvldb <machine name> -verbose  -noauth
         # ./vos syncserv <machine name> -verbose  -noauth   
      

      You can ignore error messages indicating that tokens are missing, or that authentication failed.