3 vos_create - Creates a read/write volume and associated VLDB entry
10 B<vos create> S<<< B<-server> <I<machine name>> >>> S<<< B<-partition> <I<partition name>> >>>
11 S<<< B<-name> <I<volume name>> >>> S<<< [B<-maxquota> <I<initial quota (KB)>>] >>>
12 S<<< [B<-id> <I<volume ID>>] >>> S<<< [B<-roid> <I<readonly volume ID>>] >>>
13 S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>] [B<-verbose>]
16 B<vos cr> S<<< B<-s> <I<machine name>> >>> S<<< B<-p> <I<partition name>> >>>
17 S<<< B<-na> <I<volume name>> >>> S<<< [B<-m> <I<initial quota (KB)>>] >>>
18 S<<< [B<-i> <I<volume ID>>] >>> S<<< [B<-r> <I<readonly volume ID>>] >>>
19 S<<< [B<-c> <I<cell name>>] >>> [B<-no>] [B<-l>] [B<-v>] [B<-h>]
26 The B<vos create> command creates a read/write volume with the name
27 specified by the B<-name> argument at the site specified by the B<-server>
28 and B<-partition> arguments. In addition, the command allocates or sets
35 Volume ID numbers for the read/write volume and its associated read-only
36 and backup volumes (this command does not actually create the latter two
37 types of volume). A volume ID number is an identification number
38 guaranteed to be unique within a cell.
42 An access control list (ACL) associated with the volume's root directory,
43 which takes the same name as volume's mount point when the volume is
44 mounted with the B<fs mkmount> command. An entry that grants all seven
45 permissions to the members of the system:administrators group is
46 automatically placed on the ACL. (In addition, the File Server by default
47 always implicitly grants the C<l> (lookup) and C<a> (administer)
48 permissions on every ACL to members of the system:administrators group,
49 even when the group does not appear on an ACL; use the B<-implicit>
50 argument to the B<fileserver> initialization command to alter the set of
51 rights on a server-by-server basis if desired.)
55 The volume's space quota, set to 5000 kilobyte blocks by default. Use the
56 B<-maxquota> argument to specify a different quota, or use the B<fs
57 setquota> command to change the volume's quota after mounting the volume
58 with the B<fs mkmount> command.
62 The volume is empty when created. To access it via the Cache Manager,
63 mount it in the file space by using the B<fs mkmount> command.
67 Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
73 =item B<-server> <I<server name>>
75 Identifies the file server machine on which to create the read/write
76 volume. Provide the machine's IP address or its host name (either fully
77 qualified or using an unambiguous abbreviation). For details, see
80 =item B<-partition> <I<partition name>>
82 Identifies the partition on which to create the read/write volume, on the
83 file server machine specified by the B<-server> argument. Provide the
84 partition's complete name with preceding slash (for example, C</vicepa>)
85 or use one of the three acceptable abbreviated forms. For details, see
88 =item B<-name> <I<volume name>>
90 Specifies a name for the read/write volume. The maximum length is 22
91 characters, which can include any alphanumeric or punctuation
92 character. By convention, periods separate the fields in a name. Do not
93 apply the C<.backup> or C<.readonly> extension to a read/write volume
94 name; they are reserved for the Volume Server to add to the read/write
95 name when creating those backup and read-only volumes respectively.
97 =item B<-maxquota> <I<volume quota>>
99 Specifies the maximum amount of disk space the volume can use, as a number
100 of kilobyte blocks (a value of C<1024> is one megabyte). The value C<0>
101 (zero) grants an unlimited quota, but the size of the disk partition that
102 houses the volume places an absolute limit on its size. If this argument
103 is omitted, the default value is C<5000>.
105 =item B<-id> <I<volume ID>>
107 Specifies the volume ID for the read/write volume. If this options is not
108 specified, or the given volume ID is 0, a volume ID will be allocated for
109 the volume automatically. The volume IDs allocated should be fine for
110 almost all cases, so you should almost never need to specify this option.
112 =item B<-roid> <I<readonly volume ID>>
114 Specifies the volume ID for the readonly volume corresponding to the
115 read/write volume that is being created. The readonly volume will not be
116 created; this merely specifies what volume ID the readonly volume will use
117 when it is created. If a volume ID of 0 is specified here, no readonly
118 volume ID will be assigned to the created volume immediately. A readonly
119 volume ID can still be assigned later when B<vos addsite> is run; if a
120 volume does not have a readonly volume ID associated with it by the time
121 B<vos release> is run, a volume ID will be allocated for it.
123 If this option is not specified, the default readonly volume ID is one
124 number higher than the read-write volume ID, whether or not that ID was
127 As with the B<-id> option, the default allocated volume IDs should be
128 sufficient for almost all cases, so you should almost never need to
131 =item B<-cell> <I<cell name>>
133 Names the cell in which to run the command. Do not combine this argument
134 with the B<-localauth> flag. For more details, see L<vos(1)>.
138 Assigns the unprivileged identity C<anonymous> to the issuer. Do not
139 combine this flag with the B<-localauth> flag. For more details, see
144 Constructs a server ticket using a key from the local
145 F</usr/afs/etc/KeyFile> file. The B<vos> command interpreter presents it
146 to the Volume Server and Volume Location Server during mutual
147 authentication. Do not combine this flag with the B<-cell> argument or
148 B<-noauth> flag. For more details, see L<vos(1)>.
152 Produces on the standard output stream a detailed trace of the command's
153 execution. If this argument is omitted, only warnings and error messages
158 Prints the online help for this command. All other valid options are
165 The Volume Server produces the following message to confirm that it
168 Volume <volume_ID> created on partition <partition_name> of <machine_name>
172 The following command creates the read/write volume C<user.pat> on the
173 F</vicepf> partition of the file server machine C<fs4.abc.com>.
175 % vos create -server fs4.abc.com -partition /vicepf -name user.pat
176 Volume user.pat created on partition /vicepf of fs4.abc.com
178 =head1 PRIVILEGE REQUIRED
180 The issuer must be listed in the F</usr/afs/etc/UserList> file on the
181 machine specified with the B<-server> argument and on each database server
182 machine. If the B<-localauth> flag is included, the issuer must instead be
183 logged on to a server machine as the local superuser C<root>.
191 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
193 This documentation is covered by the IBM Public License Version 1.0. It was
194 converted from HTML to POD by software written by Chas Williams and Russ
195 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.