Start the dafs process. The dafs process consists of the Demand-Attach File Server, Volume Server, Salvage Server, and Salvager (dafileserver, davolserver, salvageserver, and dasalvager processes). Most sites should run the Demand-Attach File Server, but the traditional/legacy File Server remains an option. If you are uncertain whether to run the legacy File Server, see Appendix C, The Demand-Attach File Server.
Issue the bos create command to start the dafs process. The commands appear here on multiple lines only for legibility.
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 -localauth
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 dafs process has started
successfully by issuing the bos status command. Its output mentions two
# ./bos status <
machine name> dafs -long -localauth
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.
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 \ -localauth
The Volume Server produces a message confirming that it created the volume on the specified partition.