Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod1 / vos_create.pod.in
CommitLineData
805e021f
CE
1=head1 NAME
2
3vos_create - Creates a read/write volume and associated VLDB entry
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<vos create> S<<< B<-server> <I<machine name>> >>>
11 S<<< B<-partition> <I<partition name>> >>>
12 S<<< B<-name> <I<volume name>> >>>
13 S<<< [B<-maxquota> <I<initial quota (KB)>>] >>>
14 S<<< [B<-id> <I<volume id number>>] >>>
15 S<<< [B<-roid> <I<RO volume id number>>] >>>
16 S<<< [B<-cell> <I<cell name>>] >>>
17 [B<-noauth>] [B<-localauth>] [B<-verbose>]
18 [B<-encrypt>] [B<-noresolve>]
19 S<<< [B<-config> <I<config directory>>] >>>
20 [B<-help>]
21
22B<vos cr> S<<< B<-s> <I<machine name>> >>> S<<< B<-p> <I<partition name>> >>>
23 S<<< B<-na> <I<volume name>> >>> S<<< [B<-m> <I<initial quota>>] >>>
24 S<<< [B<-i> <I<volume id number>>] >>>
25 S<<< [B<-r> <I<RO volume id number>>] >>>
26 S<<< [B<-c> <I<cell name>>] >>> [B<-noa>] [B<-l>] [B<-v>]
27 [B<-e>] [B<-nor>]
28 S<<< [B<-co> <I<config directory>>] >>>
29 [B<-h>]
30
31=for html
32</div>
33
34=head1 DESCRIPTION
35
36The B<vos create> command creates a read/write volume with the name
37specified by the B<-name> argument at the site specified by the B<-server>
38and B<-partition> arguments. In addition, the command allocates or sets
39the following:
40
41=over 4
42
43=item *
44
45Volume ID numbers for the read/write volume and its associated read-only
46and backup volumes (this command does not actually create the latter two
47types of volume). A volume ID number is an identification number
48guaranteed to be unique within a cell.
49
50=item *
51
52An access control list (ACL) associated with the volume's root directory,
53which takes the same name as volume's mount point when the volume is
54mounted with the B<fs mkmount> command. An entry that grants all seven
55permissions to the members of the system:administrators group is
56automatically placed on the ACL. (In addition, the File Server by default
57always implicitly grants the C<l> (lookup) and C<a> (administer)
58permissions on every ACL to members of the system:administrators group,
59even when the group does not appear on an ACL; use the B<-implicit>
60argument to the B<fileserver> initialization command to alter the set of
61rights on a server-by-server basis if desired.)
62
63=item *
64
65The volume's space quota, set to 5000 kilobyte blocks by default. Use the
66B<-maxquota> argument to specify a different quota, or use the B<fs
67setquota> command to change the volume's quota after mounting the volume
68with the B<fs mkmount> command.
69
70=back
71
72The volume is empty when created. To access it via the Cache Manager,
73mount it in the file space by using the B<fs mkmount> command.
74
75=head1 CAUTIONS
76
77=include fragments/volsize-caution.pod
78
79=head1 OPTIONS
80
81=over 4
82
83=item B<-server> <I<server name>>
84
85Identifies the file server machine on which to create the read/write
86volume. Provide the machine's IP address or its host name (either fully
87qualified or using an unambiguous abbreviation). For details, see
88L<vos(1)>.
89
90=item B<-partition> <I<partition name>>
91
92Identifies the partition on which to create the read/write volume, on the
93file server machine specified by the B<-server> argument. Provide the
94partition's complete name with preceding slash (for example, C</vicepa>)
95or use one of the three acceptable abbreviated forms. For details, see
96L<vos(1)>.
97
98=item B<-name> <I<volume name>>
99
100Specifies a name for the read/write volume. The maximum length is 22
101characters, which can include any alphanumeric or punctuation
102character. By convention, periods separate the fields in a name. Do not
103apply the C<.backup> or C<.readonly> extension to a read/write volume
104name; they are reserved for the Volume Server to add to the read/write
105name when creating those backup and read-only volumes respectively.
106
107=item B<-maxquota> <I<initial quota>>
108
109Specifies the maximum amount of disk space the volume can use. The size
110should be a positive integer followed by an optional suffix: C<K> for
111kibibytes (1024 bytes, the default), C<M> for mebibytes (1024 kibibytes),
112C<G> for gibibytes (1024 mebibytes), and C<T> for tebibytes (1024
113gibibytes). The value C<0> (zero) grants an unlimited quota, but the size
114of the disk partition that houses the volume places an absolute limit on
115its size. If this argument is omitted, the default value is C<5000K>.
116
117=item B<-id> <I<volume ID>>
118
119Specifies the volume ID for the read/write volume. If this options is not
120specified, or the given volume ID is 0, a volume ID will be allocated for
121the volume automatically. The volume IDs allocated should be fine for
122almost all cases, so you should almost never need to specify this option.
123
124=item B<-roid> <I<readonly volume ID>>
125
126Specifies the volume ID for the readonly volume corresponding to the
127read/write volume that is being created. The readonly volume will not be
128created; this merely specifies what volume ID the readonly volume will use
129when it is created. If a volume ID of 0 is specified here, no readonly
130volume ID will be assigned to the created volume immediately. A readonly
131volume ID can still be assigned later when B<vos addsite> is run; if a
132volume does not have a readonly volume ID associated with it by the time
133B<vos release> is run, a volume ID will be allocated for it.
134
135If this option is not specified, the default readonly volume ID is one
136number higher than the read-write volume ID, whether or not that ID was
137manually specified.
138
139As with the B<-id> option, the default allocated volume IDs should be
140sufficient for almost all cases, so you should almost never need to
141specify them explicitly. This option is available in OpenAFS
142versions 1.5.61 or later.
143
144=include fragments/vos-common.pod
145
146=back
147
148=head1 OUTPUT
149
150The Volume Server produces the following message to confirm that it
151created the volume:
152
153 Volume <volume_ID> created on partition <partition_name> of <machine_name>
154
155=head1 EXAMPLES
156
157The following command creates the read/write volume C<user.pat> on the
158F</vicepf> partition of the file server machine C<fs4.example.com>.
159
160 % vos create -server fs4.example.com -partition /vicepf -name user.pat
161 Volume user.pat created on partition /vicepf of fs4.example.com
162
163=head1 PRIVILEGE REQUIRED
164
165The issuer must be listed in the F</usr/afs/etc/UserList> file on the
166machine specified with the B<-server> argument and on each database server
167machine. If the B<-localauth> flag is included, the issuer must instead be
168logged on to a server machine as the local superuser C<root>.
169
170=head1 SEE ALSO
171
172L<vos(1)>
173
174=head1 COPYRIGHT
175
176IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
177
178This documentation is covered by the IBM Public License Version 1.0. It was
179converted from HTML to POD by software written by Chas Williams and Russ
180Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.