If no operands are specified, then a description file is used to specify what records to create. By default, this description file is read from the standard input. If operands are specified, then the first operand is a keyword that determines the object to build, the second operand is the name of the object to be created, and additional operands specify attributes for the object to be built. An attribute given on the command line is specified in the same manner used with the description file (with multiple attributes given, one attribute per operand), except that the double-quote convention is not needed. See the ``Examples'' section for sample uses.
For convenience, a special attribute form can be used for subdisks specified directly from the command line. This special attribute form is:
medianame,offset[,len]The first form specifies a subdisk location by device path, offset within that device, and length. The second form specifies the subdisk location by a disk media record name, offset within the disk's public region, and length. Optionally, the length can be specified with a len=length attribute instead. If a device path is specified, then it must match the device path for the public region of a known disk in the indicated disk group.
More than one record, including more than one volume or plex hierarchy, can be specified in a single description file. vxmake attempts to create all records within a single transaction, so that either all records are created or no records are created.
See the man page vxmake(4) for a specification of vxmake descriptions.
Descriptions of records within a volume hierarchy are filtered through a usage-type-specific utility, as appropriate for the usage type, before the records are actually created. Subdisks and plexes that are not specified within a volume hierarchy are filtered by the gen usage type. The usage-type utilities may change the descriptions so that certain fields are ignored or set up with initial values. Plex or subdisk records to be associated with a volume or plex may also be changed if the association is indicated in the description, even if the plex or subdisk record is not explicitly specified.
A usage type must be specified for every volume record, either through setting the usetype field in the volume record description, or through the -U option to vxmake.
Attempts to specify certain attributes are ignored by vxmake. Some attributes are ignored by the switchout (usage-type independent) vxmake itself. The usage-type dependent vxmake may cause additional attributes to be ignored.
The sections that follow provide information on the attributes that can be specified for subdisk, plex, and volume creation.
Fields that can be specified for subdisks are: tutil0, tutil1, tutil2, putil0, putil1, putil2, daname, dmname (or disk), path, comment, devoffset, dmoffset, len and dmrid.
The disk specification for subdisks uses one of following fields, in order of precedence: dmrid, dmname, daname, or path. The dmrid field is used, if non-zero. One of the other fields is used if defined to a non-empty string. If the path field is the only field used, then it must define the block device path for a partition containing the public region of a disk in the requested disk group.
With path, the devoffset field is used as an offset into the partition; otherwise dmoffset is used as an offset into the private region. This distinction is important if the public region does not begin at the beginning of its partition.
Specification of a disk in some form (including possibly the special forms devicepath,offset,length or medianame,offset,length) is required. Specification of the len field is also required. All other fields default to zero (for numbers) or empty strings (for strings).
Fields that can be specified for plexes are: tutil0, tutil1, tutil2, putil0, putil1, putil2, comment, layout, ncolumn, stwidth, sd, and logsd.
There are no required fields for plex records. All fields default to zero (for numbers) or empty strings (for strings). The layout field defaults to concat.
If the layout field is set to stripe or raid5, then the stwidth attribute must be specified. If the layout field is set to concat, the ncolumn field cannot be specified.
An sd specification names the subdisks to associate with the plex. The specification optionally names the offsets of the subdisks within the plex. If no offsets are specified, then the subdisks are directly concatenated in the order indicated. If the sd attribute is specified for a striped plex and ncolumn is not specified, ncolumn will default to the column of the subdisk with the highest column specification. As a special case, if ncolumn is not specified and the sd does not specify columns or offsets for the subdisks, then each subdisk will be placed in its own column at an offset of zero in the order they are specified and the plex's ncolumn attribute is set to the number of subdisks specified.
A logsd specification names a subdisk to associate as a special log subdisk for recording volume activity as part of the dirty region logging feature.
Fields that can be specified for volumes are: tutil0, tutil1, tutil2, putil0, putil1, putil2, comment, usetype, startopts, readpol, prefname, minor, user, group, mode, len, writeback, writecopy, logtype, and plex.
Specification of a usage type is required, either using the -U option on the command line, or using the usetype attribute. Specification of a usetype attribute overrides a value specified with -U. All other fields have default values: readpol defaults to round; user and group both default to 0 (root); mode defaults to u=rw (mode 600); writeback and writecopy default to on; len defaults to the length of the shortest associated plex (or zero, if no plex associations are requested); all other numeric fields default to zero, and all other string fields default to empty strings.
A plex specification names the plexes to associate with the volume. The order of plexes in this list is not important.
The value of the prefname field is relevant only if the readpol attribute is set to prefer.
#rectyp #name #options sd disk3-01 disk=disk3 offset=0 len=10000 sd disk3-02 disk=disk3 offset=25000 len=10480 sd disk4-01 disk=disk4 offset=0 len=8000 sd disk4-02 disk=disk4 offset=15000 len=8000 sd disk4-03 disk=disk4 offset=30000 len=4480 plex db-01 layout=STRIPE ncolumn=2 stwidth=16k sd=disk3-01:0/0,disk3-02:0/10000,disk4-01:1/0,This description specifies a gen type volume that contains two plexes: a volatile memory disk plex (db-02), which is preferred, and a physical disk plex (db-01). The memory disk plex is sparse and covers only the last 640 sectors of the 40960-sector length of the volume. The physical disk plex is striped across two 20480-sector columns. Column zero contains two subdisks and column one contains three subdisks. The plex offset specified for each subdisk concatenates the subdisks contiguously in their respective columns.
disk4-02:1/8000,disk4-03:1/16000 sd ramd1-01 disk=ramd1 len=640 comment="Hot spot for dbvol plex db-02 sd=ramd1-01:40320 vol db usetype=gen plex=db-01,db-02 readpol=prefer prefname=db-02 comment="Uses mem1 for hot spot in last 5m
For striped or RAID-5 plex subdisk associations, if one number is specified for the the column and column offset field, the number is interpreted as a column number and the subdisk is associated at the end of the column in the order it appears in the subdisk list. The same subdisk association list for plex db-01 could be re-written as follows:
sd=disk3-01:0,disk3-02:0,disk4-01:1,disk4-02:1,disk4-03:1The following is a simple sequence of commands to create a hierarchy with one subdisk, one plex, and one volume:
volmake sd 5s1-01 /dev/dsk/5s1,32000 comment="5s1 subdisk 1" volmake plex demo-1 sd=5s1-01 comment="Demo volume, plex 1" volmake -U gen vol demo plex=demo-1 comment="Demo gen volume"
Subdisk fields are set, checked, or modified as follows:
The putil0 fields are not set, and their contents are preserved.
Subdisk fields are set, checked or modified as follows:
The putil0 fields are not set, and their contents are preserved.
The raid5 specific vxmake utility will only allow one plex with a layout of raid5 to be associated with a volume. Plexes not of the raid5 layout are associated as RAID-5 log plexes.
See vxintro(1M) for a list of standard exit codes.