vos_create - Creates a read/write volume listed with the Location Service
vos create -server <machine name> -partition <partition name> -name <volume name> [-maxquota <initial quota (KB)>] [-id <volume id number>] [-roid <RO volume id number>] [-cell <cell name>] [-noauth] [-auth] [-localauth] [-encrypt [<yes|no>]] [-verbose] [-noresolve] [-config <configuration file>] [-help]
The vos create command creates a read/write volume with the name specified by the -name argument at the site specified by the -server and -partition arguments. In addition, the command:
Allocates unique Volume ID numbers for the read/write volume and its associated read-only and backup volumes. The read-only and backup ID numbers are reserved in case read-only or backup volumes are created in the future using the vos_addsite(1) and vos_release(1) or vos_backup(1) commands. us
Sets an access control list (ACL) associated with the volume's root directory,
which takes the same name as volume's mount point when the volume is mounted with the fs mkmount command.
An ACE that grants all seven permissions to the members of the system:administrators group is automatically added to the ACL.
(In addition,
the File Server by default always implicitly grants the l (lookup) and a (administer) permissions to members of the system:administrators group for every directory and file,
even when the group does not appear on the applicable ACL.
Use the /etc/yfs/server/yfs-server.conf <[fileserver] implicit configuration parameter to alter the set of default rights on a server-by-server basis; if desired.)
Sets the volume's default space quota, set to 20 gibibytes (20,971,520 1KB blocks). Use the -maxquota argument to specify a different quota, or use the fs_setquota(1) command to change the volume's quota after mounting the volume with the fs_mkmount(1) command.
The volume is empty when created. To access it via the Cache Manager, mount it in the file namespace by using the fs_mkmount(1) command.
Currently, the maximum partition size and volume quota is 16 zettabytes (2^74 bytes). Note that tools such as fs_listquota(1) can only report sizes up to 2 terabytes (2^41 bytes) when accessing a volume housed on an IBM AFS or OpenAFS File Server.
Identifies the File Server on which to create the read/write volume. Provide a fully qualified host name, an IP address or UUID as reported by vos_listfs(1).
Identifies the partition on the File Server named by the -server argument on which to create the read/write volume.
Provide the partition's complete name with preceding slash (for example,
/vicepa) or use one of the three acceptable abbreviated forms.
For details,
see vos(1)
Specifies a name for the read/write volume.
The maximum length is 22 characters,
which can include any alphanumeric or punctuation character.
By convention,
periods separate the fields in a name.
Do not apply the .backup or .readonly extension to a read/write volume name; they are reserved and are added to the read/write name to represent the backup and read-only volumes respectively.
Specifies the maximum amount of disk space the volume can use.
The size should be a positive integer followed by an optional suffix: K for kibibytes (1024 bytes,
the default),
M for mebibytes (1024 kibibytes),
G for gibibytes (1024 mebibytes),
and T for tebibytes (1024 gibibytes).
The value 0 (zero) grants an unlimited quota,
but the size of the disk partition that houses the volume places an absolute limit on its size.
If this argument is omitted,
the default value is 20G.
Specifies the volume ID for the read/write volume. If this argument is not specified, or the given volume ID is 0, a volume ID will be allocated for the volume automatically. The automatically allocated volume IDs are sufficient for most situations.
Specifies the volume ID for the readonly volume corresponding to the read/write volume that is being created. The readonly volume will not be created; this merely specifies what volume ID the readonly volume will use when it is created. If a volume ID of 0 is specified here, no readonly volume ID will be assigned to the created volume immediately. A readonly volume ID can still be assigned later when vos_addsite(1) is run; if a volume does not have a readonly volume ID associated with it by the time vos_release(1) is run, a volume ID will be allocated for it.
If this option is not specified, the default readonly volume ID will be allocated. The readonly ID will be one greater than the read-write volume ID.
As with the -id option, the automatically allocated volume IDs are sufficient for most situations.
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1).
Assigns the unprivileged identity anonymous to the issuer.
Do not combine this flag with the -localauth flag.
For more details,
see vos(1).
Obtains an authentication token using the server encryption key with the highest key version number in the local /etc/yfs/server/KeyFileExt file. The resulting token never expires and has Super User privileges. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1).
Use the calling user's tokens from the kernel or as obtained using the active Kerberos ticket granting ticket to communicate with the Volume Server and Location Service. This is the default if neither -localauth nor -noauth is given.
Since this option is the default, it is usually not useful for running single command line operations. However, it can be useful when running commands via vos_interactive(1) or vos_source(1), since otherwise it would be impossible to switch from, for example, -localauth back to using regular tokens during a bulk operation.
Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear.
Enables or disables encrytion for the command so that the operation's results are not transmitted across the network in clear text.
Shows all servers as IP addresses instead of the reverse DNS lookup hostname.
-noresolve useful when troubleshooting no such volume and volume moved errors.
Set the location of the configuration file to be used. The default file is /etc/yfs/yfs-client.conf.
Prints the online help for this command. All other valid options are ignored.
The vos(1) command produces the following message to confirm that the volume was created on the designated File Server and partition:
Volume <volume_ID> created on partition <partition_name> of <machine_name>
The following command creates the read/write volume user.pat on the /vicepf partition of the File Server fs1.your-cell-name.com.
% vos create -server fs1.your-cell-name.com -partition /vicepf -name user.pat Volume user.pat created on partition /vicepf of fs1.your-cell-name.com
The issuer must be listed in the /etc/yfs/server/UserListExt file on the File Server specified by the -server argument and on each Location Server. If the -localauth flag is included, the issuer must instead be logged on to a server with an account capable of reading the /etc/yfs/server/KeyFileExt file.
fs_mkmount(1), fs_setquota(1), vos(1), vos_addsite(1), vos_backup(1), vos_listfs(1), vos_release(1), vos_setquota(1), yfs-server.conf(5)
IBM Corporation 2000. http://www.ibm.com/ All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
"AFS" is a registered mark of International Business Machines Corporation, used under license. (USPTO Registration 1598389)
"OpenAFS" is a registered mark of International Business Machines Corporation. (USPTO Registration 4577045)
The "AuriStor" name, log 'S' brand mark, and icon are registered marks of AuriStor, Inc. (USPTO Registrations 4849419, 4849421, and 4928460) (EUIPO Registration 015539653).
"Your File System" is a registered mark of AuriStor, Inc. (USPTO Registrations 4801402 and 4849418).
"YFS" and "AuriStor File System" are trademarks of AuriStor, Inc.