1VICETAB(5)                                                          VICETAB(5)
2
3
4

NAME

6       vicetab - information about Coda server data partitions
7

DESCRIPTION

9       vicetab  is a table of Coda data partitions found on individual servers
10       comprising a Coda netowrk server. This includes  partition(s)  used  by
11       the  backup  coordinator  to  store  dump files to placed on a suitable
12       backup media. This file must be shared among all machines comprising  a
13       Coda hub so edits should be done only on the designated SCM.
14
15   EXAMPLE VICETAB FILE
16       tye             /vicepa         ftree  depth=5,width=8
17       tye             /vicepb         ftree  width=8,depth=5
18       taverner        /vicepa         ftree  width=8,depth=5
19       taverner        /usr/vicepb     ftree  depth=4,width=8
20       tallis          /vicepa         ftree  width=8,depth=5
21       tallis          /vicepb         ftree  width=8,depth=5
22       dvorak          /backup1        backup
23       dvorak          /backup2        backup
24       dvorak          /backup3        backup
25
26       Where  column  1  specifies  the  server as returned by the system call
27       gethostbyname().
28
29       Column 2 specifies the directory of the Coda data tree which must be  a
30       local file system partition for optimal performance.  NOTE: if a server
31       serves than more than one Coda data parition, each data partition  must
32       have a seperate entry in vicetab.
33
34       Column 3 specifies the Coda partition type.
35
36       · ftree  an "inode number" directory and file naming system for storing
37         the Coda filesystem into a local file  system  tree  structure:  e.g.
38         inode  4711  in  base  10  with  width  1  and  depth  5 would become
39         0/4/7/1/1. So, using the above example, a width of 4 and a depth of 2
40         would  make  the file name 4/711.  If this storage type is specified,
41         the width and depth must also be given in the 4th column seperated by
42         a comma.
43
44       Column 4 specifies the width and depth of the ftree.
45
46       · width the maximum "width" of an ftree data partition.
47
48       · depth the maximum "depth" of an ftree data partition.
49
50       In the case of the backup coordinator, only the first three columns are
51       used, with a partition type of backup specified in the third column.
52
53       This file should only be edited on the designated SCM machine and  then
54       allowed to propagate.
55

BUGS

57       None we currently are aware of.
58

AUTHOR

60       · Henry M. Pierce, 1997, created
61
62
63
64Coda Distributed File System     25 April 2005                      VICETAB(5)
Impressum