Start the fs process, which consists of the File Server, Volume Server, and Salvager (fileserver, volserver and salvager processes).
Issue the bos create command to start the fs process. The command appears here on multiple lines only for legibility.
# ./bos create <machine name
> fs fs /usr/afs/bin/fileserver \ /usr/afs/bin/volserver /usr/afs/bin/salvager \ -cell <cell name
> -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 process has started successfully by issuing the
bos status command. Its output mentions two proc
starts
.
# ./bos status <machine name
> fs -long -noauth
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 \ -cell <cell name
> -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
> -cell <cell name
> -verbose -noauth # ./vos syncserv <machine name
> -cell <cell name
> -verbose -noauth
You can ignore error messages indicating that tokens are missing, or that authentication failed.