Beruflich Dokumente
Kultur Dokumente
named volumes, or for volumes residing on the specified disks medianame. If no medianame or volume is
specified, the operation applies to all volumes, or to all volumes in the specified disk group. If -s is
specified, disabled volumes are started. With -s and -n, volumes are started, but no other recovery takes
place. Recovery operations are started in an order that prevents two concurrent operations on the same
disk. Operations that involve unrelated disks run in parallel.
-b : Performs recovery operations in the background. With this option, vxrecover runs in the background to
attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID-5 parity. If this is used
with -s, volumes are started before recovery begins in the background.
-c : Operates on cluster-shareable disk groups. This option is used by the cluster reconfiguration utility to
effect recovery on volumes in shared disk groups after the failure of a node in the cluster. Do not use -c as
a command-line option. Available only if the VxVM cluster feature is enabled and a license is installed.
-E Starts disabled volumes or plexes even when they are in the EMPTY state. This is useful for starting up
volumes restored by the vxmake utility when specified along with the -s option.
-g diskgroup : Limits operation of the command to the given disk group, as specified by disk group ID or
disk group name. If no volume or medianame is specified, all disks in this disk group are recovered,
otherwise, the volume and medianame are evaluated relative to the given disk group. Without the -g option,
if no volume and medianame is specified, all volumes in all imported disk groups are recovered; otherwise,
the disk group for each medianame specified is determined based on name uniqueness within all disk
groups.
-m : Recognizes and enables volumes that were moved as a result of a disk group move, split or join
operation.
-n Does not perform any recovery operations. If used with -s, volumes are started, but no other actions
are taken. If used with -p, vxrecover only prints a list of startable volumes.
-o options : Passes the given option arguments to the -o options for the vxplex att and vxvol start
operations generated by vxrecover. You can specify an option argument in the form prefix:options to restrict
the set of commands that the -o option is applied to. Defined prefixes are:
vol applies to all invocations of the vxvol utility (volume starts, mirror resynchroniza- tions, RAID-5
partity rebuilds, and RAID-5 subdisk recoveries)
plex, applies to all invocations of the vxplex utility (used only for attaching plexes)
attach applies specifically to plex attach operations
start applies specifically to volume start operations
recover applies to subdisk recoveries
resync applies to mirror resynchronization and RAID-5 parity recovery.
-p Prints the list of selected volumes that are startable. For each startable volume, a line is printed
containing the volume name, the disk group ID of the volume, the volume's usage type, and a list of state
flags pertaining to mirrors of the volume. State flags include:
kdetach indicates that one of the mirrors was detached by an I/O failure
stale means that one of the mirrors needs recovery, but that the recovery is related to an
administrative operation, not an I/O failure
stopped prints if neither kdetach nor stale is appropriate for the volume.
-s : Starts disabled volumes that are selected by the operation. Volumes are started before any other
recovery actions are taken. Volumes are started with the -o delayrecover start option. This requests that
any operations that can be delayed in starting a volume are delayed. That is, only those operations
necessary to make a volume available for use occur. Other operations, such as mirror resynchronization,
attaching of stale plexes and subdisks, and recovery of stale RAID-5 parity, are typically delayed.
-t tasktag : If any tasks are registered to track the progress of the operation, marks them with the tag
tasktag. This option is also passed to any utilities called to perform recoveries, so all tasks registered by
any utility to perform the recoveries are also tagged with tasktag.
-v : Displays information about each task started by vxrecover. For recovery operations (as opposed to
start operations), prints a completion status when each task completes.
-V : Displays each command executed by vxrecover. The ouput generated is more verbose than the job
descriptions printed with the -v option.
EXAMPLES : To recover, in the background, any detached subdisks or plexes that resulted from
replacement of a specified disk, use the command:
vxrecover -b medianame
Veritas Commands
Page 1 of 93
Veritas Commands
Page 2 of 93
Veritas Commands
Page 3 of 93
1. Record type (rl), Record name, Associated RVG, or - if the RLINK is dissociated, RLINK kernel state
(derived from various flags), RLINK utility state, The remote host
7. The remote disk group, The remote RLINK
A header line is printed before any record information, for each type of record that could be selected based
on the -V, -P, -v, -p, -s, and -h options. These header lines are followed by a single blank line.
-v : Display only volumes. If a name operand refers to a plex or subdisk/subvolume, a diagnostic is written
to the standard error.
-V : Display only RVGs.
To display the names of all unassociated plexes, use the command
vxprint -n -p -e !assoc
To print all subdisks, including the subdisk name and either the subdisk plex association offset or the putil0
field for dissociated subdisks, enter:
vxprint -s -F "%{name:-14} %{pl_offset|putil0}"
The vxprint command can be used to back up objects from one disk group configuration with the use of the
combined options -mvpsch or -mvpschr. The output should be saved into a file that is maintained outside of
the system being backed up. Use the following command with the saved file to restore the configuration
---------------------------------------------------------------------------------------------------------------------------------------vxresize - change the length of a volume containing a file system
/etc/vx/bin/vxresize [-bfsx] [-F fstype] [-g diskgroup] [-t tasktag] volume
new_length [medianame...]
The vxresize command either grows or shrinks both the file system and its underlying volume to match the
specified new volume length. The ability to grow or shrink is file system dependent. Some file system types
may require that the file system be unmounted for the operation to succeed, as shown in the following
table:
Vxfs
UFS
Mounted FS
Grow only
Unmounted FS
Not allowed
Grow only
Note : vxresize works with VERITAS File System (VxFS) and UFS file systems only.
In some situations, when resizing large volumes, vxresize may take a long time to complete. Resizing a
volume with a usage type other than FSGEN or RAID5 can result in loss of data. Use the -f option to force
resizing of such a volume.
You cannot resize volumes comprised of different layout types. The new_length operand can begin with a +
/ - to indicate that the new length is added to or subtracted from from the current volume length.
The medianame operands name disks to use for allocating new space for a volume. These arguments can
be a simple name for a disk media record, or they can be of the form medianame, offset to specify an
offset within the named disk. If an offset is specified, then regions from that offset to the end of the disk are
considered candidates for allocation.
-o override : Resizes the specified volume and ignores any storage-specific guidelines. Overriding the
guidelines is not recommended as it can result in incompatible objects, or objects that cannot be
administered by VxVM and any associated software that exploit storage-specific features.
-o verify : Verifies that the specified volume can be resized without violating any storage-specific
guidelines, but does not resize the volume. If any guidelines are violated, vxresize exits with an error
message.
Note: These options need a specific license. Without the license, vxresize ignores the specified option.
OPTIONS
-b : Performs the resize operation in the background. Use the vxprint command to determine when the
operation completes.
Note : This option is only honored for grow operations on non-RAID5 volumes. Otherwise, it is ignored.
-f : Forces a operation that is usually disallowed by vxresize.
-F fstype : Supplies the type of the file system to be resized.
Veritas Commands
Page 4 of 93
Veritas Commands
Page 5 of 93
relocate failed subdisks. However, if no spare space is available, or the available spare space is not
suitable or sufficient, free space is also used except for those marked with the nohotuse flag.
Nohotuse Space : A disk can be marked as ``nohotuse.'' This excludes the disk from being used by
vxrelocd, but it is still available as free space.
Replacement Procedure : After mail is sent, vxrelocd relocates failed subdisks (those listed in the
subdisks list). This requires finding appropriate spare or free space in the same disk group as the failed
subdisk. A disk is eligible as replacement space if it is a valid VxVM disk (VM disk) and contains enough
space to hold the data contained in the failed subdisk. If no space is available on spare disks, the relocation
uses free space that is not marked nohotuse.
To determine which of the eligible disks to use, vxrelocd first tries the disk that is closest to the failed disk.
The value of ``closeness'' depends on the controller, target, and disk number of the failed disk. A disk on
the same controller as the failed disk is closer than a disk on a different controller; a disk under the same
target as the failed disk is closer than one under a different target.
vxrelocd moves all subdisks from a failing drive to the same destination disk if possible.
If the failing disk is a root disk, vxrelocd works only if it can relocate all of the file systems onto the same
disk. If none is found, mail sends the message:
Rootdisk medianame of disk group dg_name experienced a failure, but there is no suitable disk found to
relocate all associated subdisks.
If no spare or free space is found, mail is sent explaining the disposition of volumes that had storage on the
failed disk:
Hot-relocation was not successful for subdisks on disk dm_name in volume v_name in disk group
dg_name. No replacement was made and the disk is still unusable.
The following volumes have storage on medianame:
volumename
These volumes are still usable, but the redundancy of those volumes is reduced. Any RAID-5 volumes with
storage on the failed disk may become unusable in the face of further failures.
If any non-RAID-5 volumes were made unusable due to the disk failure, the following message is included:
The following volumes:
volumename
have data on medianame but have no other usable mirrors on other disks. These volumes are now
unusable and the data on them is unavailable. These volumes must have their data restored.
If any RAID-5 volumes were made unavailable due to the disk failure, the following message is included:
The following RAID-5 volumes:
volumename
had storage on medianame and have experienced other failures. These RAID-5 volumes are now unusable
and data on them is unavailable. These RAID-5 volumes must have their data restored.
If there is spare space available, a snapshot of the current configuration is saved in
/etc/vx/saveconfig.d/dg_name.yymmdd_hhmmss.mpvsh before attempting a subdisk relocation. Relocation
requires setting up a subdisk on the spare or free space not marked with nohotuse and using it to replace
the failed subdisk. If this is successful, the vxrecover command runs in the background to recover the data
in volumes that had storage on the disk.
If the relocation fails, the following message is sent:
Hot-relocation was not successful for subdisks on disk dm_name in volume v_name in disk group
dg_name. No replacement was made and the disk is still unusable.If any volumes (RAID-5 or otherwise)
become unusable due to the failure, the following message is included:
The following volumes:
volumename
have data on dm_name but have no other usable mirrors on other disks. These volumes are now unusable
and the data on them is unavailable. These volumes must have their data restored.
If the relocation procedure was successful and recovery has begun, the following mail message is sent:
Volume v_name Subdisk sd_name relocated to newsd_name, but not yet recovered.
After recovery completes, a mail message is sent relaying the result of the recovery procedure. If the
recovery is successful, the following message is included in the mail:
Veritas Commands
Page 6 of 93
Veritas Commands
Page 7 of 93
getsubpaths : Displays the paths controlled by the specified DMP node. The dmpnodename specified
must be a valid node in the /dev/vx/[r]dmp directory. getsubpaths can also obtain all paths through a
particular host disk controller. The attributes supported by getsubpaths are ctlr and dmpnodename. help
Displays a detailed information about attributes used with a particular keyword.
vxdmpadm help listctlr
listctlr Lists the disk controllers connected to the host. listctlr all lists all controllers on the host.
listenclosure Displays all attributes of the specified enclosure. For example:
vxdmpadm listenclosure ENC01
displays all attributes associated with the disk array ENC01. The attribute all displays the attributes
associated with all the enclosures connected to the host.
setattr enclosure : Assigns a meaningful name to the specified enclosure. An existing enclosure name
must be specified. vxdmpadm setattr supports the attribute name. For example:
vxdmpadm setattr enclosure ENC01 name=lab1_enc
The disk array will be referred to by this new name for all subsequent operations.
start restore Starts the DMP restore daemon. The restore daemon analyzes the condition of paths every
interval seconds. The type of analysis depends on the specified policy:
check_all The restore daemon analyzes all paths in the system and revives the paths that are back online
as well as disables the paths that are inaccessible.
check_alternate The restore daemon checks that at least one alternate path is healthy. It generates a
notification on the first occasion that this condition is not met. If there are less than two active (and enabled)
paths under a DMP node, vxnotify displays the message "dmpnode name has N alternate paths."
Note : This policy avoids inquiry commands on all healthy paths, and is less costly than check_all in cases
where a large number of paths are available. This policy reduces to check_all if there are only two paths
per DMP node.
check_disabled The restore daemon checks the condition of paths that were previously disabled due to
hardware failures and revives them if they are back online.
check_periodic The restore daemon performs check_all once in a given number of cycles, and
check_disabled in the remainder of the cycles.
Note : This policy may lead to periodic slowing down (due to check_all) if there are large numbers of paths
available.
The default policy is check_disabled. To change the interval or policy, you
must stop the restore daemon and restart it with new attributes. To set the
policy to check_all, enter:
vxdmpadm start restore policy=check_all
If a controller is disabled using the following command, the restore daemon does not change the disabled
state of the path through it.
vxdmpadm disable ctlr=ctlr
To set the polling interval to 400 seconds, enter:
vxdmpadm start restore interval=400
Caution : The default polling interval is 300 seconds. Decreasing this interval can adversely affect system
performance.
The check_periodic policy can be invoked as follows:
vxdmpadm start restore policy=check_periodic interval=t [period=n]
Note: The polling interval must be specified.
Here the period n is the number of times that check_disabled is invoked before check_all is invoked. This
sequence is then repeated. The integer value n of period can either be specified on the command line, or
set as a tunable dmp_restore_daemon_cycles in the vxdmp.conf file. (This requires a system shutdown
and reboot to take effect.) The value of period specified on the command line takes precedence. If not
specified in either of these ways, the default period is 10. The check_alternate policy can be invoked as
follows:
vxdmpadm start restore policy=check_alternate interval=t
stat errord Displays the number of error daemons running.
Veritas Commands
Page 8 of 93
stat restored Displays the status of the automatic path restoration daemon, the interval of polling, and the
policy used to check the condition of paths.
stop restore Stops the VxVM restore daemon. Automatic path failback stops if the restore daemon stops.
ATTRIBUTES Attribute values can be specified with keywords in the form attribute=value.
all Specified with the listctlr & listenclosure
ctlr Specifies the host I/O controller to print information about.
dmpnodename Specifies the DMP metanode name that must be listed in the /dev/vx/[r]dmp directory.
enclosure Used with the keywords getsubpaths, getdmpnode, and listctlr.
interval The restore daemon checks the status of disabled paths after every interval seconds.
name When used with the setattr keyword, name assigns a new name to the specified enclosure. The new
name cannot be more than 25 characters else setattr fails with an error message.
nodename Specifies the name of a physical path to a disk that must be entered in the /dev/[r]dsk directory.
policy Value can be set to check_all or check_disabled.
type The enclosure type must be one of the enclosure categories supported by DMP.
EXAMPLES : To list all attributes of all host I/O controllers on the system, enter:
vxdmpadm listctlr all
To list all attributes of the disk array enc0, enter:
vxdmpadm listenclosure enc0
To disable I/O through the host disk controller c2, enter:
vxdmpadm disable ctlr=c2
If you then run the listctlr all command, the state of the controller c2 is shown as disabled. To enable the
host disk controller c2, which was disabled by vxdmpadm disable ctlr=c2, enter:
vxdmpadm enable ctlr=c2
Executing listctlr all after this command shows the state of the controller c2 as enabled. The following
examples outline the attributes supported by vxdmpadm listctlr.
vxdmpadm listctlr all
vxdmpadm listctlr enclosure=enc0 type=ENC
vxdmpadm listctlr type=ENC
vxdmpadm listctlr enclosure=enc0
vxdmpadm listctlr ctlr=c2
The following command lists all paths controlled by the DMP node c2t1d0s2.
vxdmpadm getsubpaths dmpnodename=c2t1d0s2
The following command obtains all paths through the host disk controller c2.
vxdmpadm getsubpaths ctlr=c2
The following command displays the DMP node that controls the node c3t2d1s2.
vxdmpadm getdmpnode nodename=c3t2d1s2
The following command displays the DMP nodes connected to the enclosure enc0.
vxdmpadm getdmpnode enclosure=enc0
The following command assigns a new name, VMGRP_1, to the enclosure enc0.
vxdmpadm setattr enclosure enc0 name=VMGRP_1
To start the restore daemon with the default interval (300 seconds) and default policy (check_disabled) :
vxdmpadm start restore
To specify the interval of polling as 400 seconds, enter:
vxdmpadm start restore interval=400
The daemon checks the condition of the paths as specified by the policy attribute. To set the policy as
check_all, enter:
vxdmpadm start restore policy=check_all
Veritas Commands
Page 9 of 93
The following command stops the DMP restore daemon; the restore daemon is automatically started at
system startup time with default attributes.
vxdmpadm stop restore
To list the intervals of restore daemons running and the number of error daemons, enter :
vxdmpadm stat restored
vxdmpadm stat errord
If only a Base VxVM license is installed, the vxdctl license command displays "DMP (single path enabled)".
If either the Full VxVM license or an automatically generated license (such as that for the PHOTON array)
is installed, the command displays "DMP (multipath enabled)".
---------------------------------------------------------------------------------------------------------------------------------------vxconfigd - VxVM configuration daemon
SYNOPSIS
vxconfigd [-dfk] [-D diag_portal]
reset] [-R request_portal] [-x arg]
[-I
inquiry_portal]
[-m
mode]
[-r
DESCRIPTION : The VxVM configuration daemon, vxconfigd, maintains disk configurations and disk
groups in VxVM. vxconfigd takes requests from other utilities for configuration changes, and communicates
those changes to the kernel and modifies configuration information stored on disk. vxconfigd also initializes
VxVM when the system is booted.
OPTIONS
-d : Equivalent to -m disable, which starts vxconfigd in disabled mode.
-D diag_portal : Specifies a rendezvous file path name for diagnostic operation connections to
vxconfigd. /etc/vx/vold_diag is the default path name. The diagnostic portal exists in both the enabled and
disabled operating modes.
-f : Starts vxconfigd in the foreground. This is often useful when debugging vxconfigd, or when tracing
configuration changes. If -f is not specified, vxconfigd forks a background daemon process. The foreground
process exits when the vxconfigd startup processing completes.
-I inquiry_portal : Specifies a rendezvous file path name for inquiry operation connections to vxconfigd.
/etc/vx/vold_inquiry is the default path name. The inquiry portal accepts only opcodes for connection
requests and query requests submitted by vxprint. All other requests are rejected. The inquiry portal exists
only when vxconfigd is operating in enabled mode.
-k : If a vxconfigd process is already running, -k kills it before any other startup processing. This is useful
for recovering from a hung vxconfigd process. Killing the old vxconfigd and starting a new one usually does
not cause problems for volume devices that are being used by applications, or that contain mounted file
systems.
-m mode Sets the initial operating mode for vxconfigd. Possible modes are:
boot Handles boot-time startup of VxVM. This starts the rootdg disk group and any required volumes on
the root disk. Boot mode is capable of operating before the root file system is remounted to read-write.
vxdctl enable is called later in the boot sequence to trigger vxconfigd to rebuild the /dev/vx/dsk and
/dev/vx/rdsk directories.
disable Starts vxconfigd in disabled mode. disable creates a rendezvous file for utilities that perform
various diagnostic or initialization operations. disable can be used with the -r reset option as part of a
command sequence to completely reinitialize VxVM config. Use the vxdctl enable operation to enable
vxconfigd.
enable Starts vxconfigd fully enabled (default). enable uses the volboot file to bootstrap and load in the
rootdg disk group. It then scans all known disks for disk groups to import and imports those disk groups.
enable also sets up entries in the /dev/vx/dsk and /dev/vx/rdsk directories to define all of the accessible
VxVM devices. If the volboot file cannot be read, or if the rootdg disk group cannot be imported, vxconfigd
starts in disabled mode.
-r reset Resets all VxVM configuration information stored in the kernel as part of startup processing. The
reset fails if any volume devices are in use. This option is primarily useful for testing or debugging.
-R request_portal : Specifies a rendezvous file path name for regular configuration and query requests.
/etc/vx/vold_request is the default. The regular request portal exists only when vxconfigd is operating in
enabled mode.
Veritas Commands
Page 10 of 93
-x arg Turns on various parameters used for debugging or other aspects of vxconfigd operation. The
argument, arg, is a decimal number, 1 through 9, or a string. A number value sets the debug information
output level and is required to obtain any debug messages.
String arguments include:
boot=volboot_path : Specifies the path name to use for the volboot file. This is primarily useful with the
stub debug option. The volboot file contains an initial list of disks that are used to locate the root disk group.
It also contains a host ID that is stored on disks in imported disk groups to define ownership of disks as a
sanity check for disks that might be accessible from more than one host.
Cleartempdir : Removes and recreates the /var/vxvm/tempdb directory. This directory stores configuration
information that is cleared after system reboots (or cleared for specific disk groups on import and deport
operations). If the contents of this directory are corrupted, due to a disk I/O failure for example, vxconfigd
will not start up if it is killed and restarted. Such a situation can be cleared by starting vxconfigd with -x
cleartempdir. This option has no effect if vxconfigd is not started in enabled mode.
Note : It is advisable to kill any running operational commands (vxvol, vxsd, or vxmend) before using the -x
cleartempdir option. Failure to do so may cause these commands to fail, or may cause disastrous but
unchecked interactions between those commands and the issuance of new commands. It is safe to use
this option while running the graphical user interface, or while VxVM background daemons are running
(vxsparecheck, vxnotify, or vxrelocd).
devprefix=prefixdir : Specifies a directory path name to prefix for any disk device accessed by vxconfigd.
For example, with devprefix=/tmp, any access to a raw disk device named c2t1d0s2 would actually be
directed to the file /tmp/dev/rdsk/c2t1d0s2. In stubbed mode, vxconfigd can operate with such files being
regular files. vxconfigd only requires entries in the prefixdir /dev/rdsk directory in stubbed mode. See stub
below for more information.
log | nolog : Logs all vxconfigd console output directly to a file. This method of logging is very reliable in
that any messages output before a system crash are available in the log file (if the crash did not corrupt the
file system). You can enable direct vxconfigd logging with the -x log argument, and turn it off with the -x
nolog argument. Logging is disabled by default.
If direct logging is enabled, the default log file is /var/vxvm/vxconfigd.log. This option can be used in
conjunction with syslog | nosyslog. The following command logs all debug and error messages to the
specified log file:
vxconfigd -x9 -x log
logfile=logfilename : Specifies an alternate vxconfigd direct log file. This option requires using the -x log
argument.
noautoconfig : vxconfigd usually configures disk devices that can be found by inspecting kernel disk
drivers automatically. These auto_configured disk devices are not stored in persistent configurations, but
are regenerated from kernel tables after every reboot. Invoking vxconfigd with -x noautoconfig prevents the
automatic configuration of disk devices, forcing VxVM to use only those disk devices configured explicitly
using vxdisk define or vxdisk init.
nothreads : Runs vxconfigd single-threaded.
stub Specifies not to communicate configuration changes to the kernel. stub is typically used as a
demonstration mode of operation for vxconfigd. In most aspects, a stubbed vxconfigd behaves like a
regular vxconfigd, except that disk devices can be regular files and volume nodes are not created. A
stubbed vxconfigd can run concurrently with a regular vxconfigd, or concurrently with any other stubbed
vxconfigd processes, as long as different rendezvous, volboot, and disk files are used for each concurrent
process.
Other VxVM utilities can detect when they are connected to a vxconfigd that is running in stubbed mode.
When a VM utility detects a stubbed-mode vxconfigd, the utility typically stubs out any direct use of
volumes or plexes itself. This allows utilities to make configuration changes in a testing environment that
runs without any communication with the kernel or creation of real volumes or plexes.
syslog | nosyslog : vxconfigd supports using the syslog() library call to log all of its console messages
(this includes error, warning, and notice messages, but not debug messages). You can enable syslog()
logging using the -x syslog argument, and turn it off with the -x nosyslog argument. You can also enable
syslog() logging at boot-time by editing the VxVM startup scripts.
syslog can be specified along with log (described above) to obtain more reliable logging. For example, the
following command logs all debug messages to the specified log file, and logs all error messages to both
the direct log file and the syslog.log file:
vxconfigd -x9 -x log -x syslog
Veritas Commands
Page 11 of 93
Note : syslog() logging works only on systems where vxconfigd is compiled with support for the syslog()
library calls.
Synctrace : Flushes tracefile data to disk, invoking fsync, to ensure that the last entry is included in the file
even if the system crashes.
timestamp | mstimestamp : Attaches a date and time-of-day timestamp to all messages written by
vxconfigd to the console. If mstimestamp is used, a millisecond value is also displayed, allowing detailed
timing of vxconfigd's operation.
tracefile=file : Logs all possible tracing information to the specified file.
EXIT CODES : If errors are encountered, vxconfigd writes diagnostic messages to the standard error
output. vxconfigd exits if it encounters some serious errors. If an error is encountered when importing the
rootdg disk group during a normal startup, vxconfigd enters disabled mode.
Defined exit codes for vxconfigd are:
0 The requested startup mode completed successfully. This is returned if -f is not used to startup vxconfigd
as a foreground process. If vxconfigd is started as a foreground process, it exits with a zero status if vxdctl
stop is used to exit vxconfigd.
1 The command line usage is incorrect.
2 Enabled-mode operation was requested, but an error caused vxconfigd to enter disabled mode instead.
This is also returned for boot-mode operation if startup failed. However, with boot-mode operation, the
background vxconfigd process exits as well.
3 The -k option was specified, but the existing vxconfigd could not be killed.
4 A system error was encountered that vxconfigd cannot recover from. The specific operation that failed is
printed on the standard error output.
5 The background vxconfigd process was killed by a signal before startup completed. The specific signal is
printed on the standard error output.
6 A serious inconsistency was found in the kernel, preventing sane operation. This can also happen
because of version mismatch between the kernel and vxconfigd.
7 The -r reset option was specified, but the VxVM kernel cannot be reset. Usually this means that a volume
is open or mounted.
8 An interprocess communications failure (usually a STREAMS failure). Has made it impossible for
vxconfigd to take requests from other utilities.
9 Volumes that must be started early by vxconfigd could not be started. The reasons, and possible
recovery solutions, are printed to the standard error output. The early-started volumes are the root and /usr
file systems, if either or both of those file systems are defined on volumes.
FILES
/dev/vx/dsk Directory containing block device nodes for volumes.
/dev/vx/rdsk Directory containing raw device nodes for volumes.
/etc/vx/volboot File containing miscellaneous boot information.
/var/vxvm/tempdb Directory containing miscellaneous temporary files. Files in this directory are recreated
after reboot.
/var/vxvm/vxconfigd.log Default log file.
---------------------------------------------------------------------------------------------------------------------------------------vxdg - manage VxVM disk groups
SYNOPSIS
vxdg [ -g diskgroup ] [ -kp ] [ -o verify | override] adddisk [ medianame=]accessname...
vxdg [ -n newname ] [ -h newhostid ] deport diskgroup...
vxdg [ -o verify | override] destroy diskgroup...
vxdg flush [diskgroup...]
vxdg [ -g diskgroup ] [ -qa ] free [ medianame...]
vxdg [ -Cfst ] [ -n newname ] import diskgroup
vxdg [ -T version ] [ -s ] [ -o verify | override] init groupname [ nconfig=config-copies ] [ nlog=log-copies ]
[ minor=base-minor ] [ medianame =] accessname...
vxdg [ -o override | verify] join sourcedg targetdg
Veritas Commands
Page 12 of 93
Veritas Commands
Page 13 of 93
flush Rewrites all disk on-disk structures managed by VxVM for the named disk groups. This rewrites all
disk headers, configuration copies, and kernel log copies. Also, if any configuration copies were disabled
(for example as a result of I/O failures), this command rewrites those configuration copies, and attempts to
enable them.
free : Lists free space that can be used for allocating subdisks. If a disk group is specified, limit the output
to the indicated disk group, otherwise list space from all disk groups. If disks are specified, by disk media
name, then restrict the output to the indicated disks. A region of free space is identified by disk media
name, a physical device tag, an offset relative to the beginning of the public region for the media, and a
length.
The physical device tag is a reference that indicates which physical device the disk media is defined on. It
appears as a truncated disk access name. If a particular physical device is split into several VxVM disk
objects, then the device tags for each disk object are the same. Device tags can be compared to identify
space that is on the same or on different physical disks. If the -q option is specified, then no header is
printed describing output fields. If the -a option is specified, then space on spare disks (which is not really
allocatable) is listed in addition to regular free space; otherwise, space on spare disks is not listed.
import Imports a disk group to make the specified disk group available on the local machine. This makes
accessible any configuration information stored with the disk group, including any disk and volume
configurations. The disk group to import is indicated by the diskgroup argument, which can be either an
administrative disk group name or a disk group unique ID.
Typically, a disk group is not imported if some disks in the disk group cannot be found by the local host. The
-f option can be used to force an import if, for example, one of the disks is currently unusable or
inaccessible.
Note : Be careful when using the -f flag because it can import the same disk group twice from disjointed
sets of disks. This can make the disk group inconsistent.
When a disk group is imported, all disks in the disk group are stamped with the host's host ID. Typically, a
disk group cannot be imported if any of its disks are stamped with a non-matching host ID. This provides a
sanity check in cases where disks can be accessed from more than one host.
If it is certain that a disk is not in use by another host (such as because a disk group was not cleanly
deported), then the -C option can be used to clear the existing host ID on all disks in the disk group as part
of the import. A host ID can also be cleared using vxdisk clearimport. A new name can be given to the disk
group on import using -n newname. If -n is used with the -t option, the stored name of the disk group
remains unchanged, but the importing host knows the disk group under the new name; otherwise, the
name change is permanent.
Typically, an imported disk group is reimported automatically when the system is rebooted, if at least some
of the disks in the disk group remain accessible and usable. This can be disabled using the -t option, which
causes the import to be persistent only until the system is rebooted.
As an example of the use of -n and -t, a rootdg disk group from one host can be imported on a second
host, operations (such as making repairs to the root volume) can be performed on the second host and the
disk group can be given back to the originating host, which can then be rebooted on the repaired disk
group. To do this, identify the disk group ID for the rootdg disk group with
vxdisk -s list, and use that disk group to import that rootdg using -C to clear import locks, -t for a temporary
name, and -n to specify an alternate name (to avoid collision with the rootdg disk group on the second
host). After repair, deport the disk group using -h to restore the import lock from the first host. In a cluster
environment, use the -s option to import a disk group as cluster-sharable. This is only valid if the cluster is
active on the host where the import takes place. Ensure that all the disks in a shared disk group are
physically accessible by all hosts. A host which cannot access all the disks in a shared disk group cannot
join the cluster.
The disks in a shared disk group are stamped with the ID of the cluster to which the hosts belong and are
marked with the shared flag. When a host joins a cluster, it automatically imports disk groups whose disks
are stamped with the cluster ID. Trying to import a shared disk group during a cluster reconfiguration fails.
init Defines a new disk group composed of the indicated disks, identified by disk access names. This
involves assigning an internal unique ID to the group, storing a pointer to that group in the root
configuration, storing a reference to the group on all of the named disks that have a disk header, and
storing a disk group record in the disk group's configuration database. At least one of the disks specified
must have space allocated for a configuration copy.
An existing deported disk group is destroyed if it has the same name as that specified for the new disk
group. The init cannot complete if a disk is being used by a disk group, deported or otherwise. If vxdg finds
Veritas Commands
Page 14 of 93
an unneeded disk group on the disk, it can be cleaned with the vxdisk -f init command. vxdg init can then
be run again.
If a medianame is specified for use with a particular disk, then that medianame names the disk media
record used to reference the disk within the disk group (for operations such as rmdisk and subdisk
creations). If no medianame is specified, then the disk media name defaults to accessname. See
vxdisk(1M) for a discussion of definition and initialization of disk access records.
The init operation can be used to initialize a root disk group configuration, which is identified by the special
name rootdg. If any database locations are listed in the volboot file, then as a special case for initializing
rootdg, no disk specifications are allowed. Disks should be initialized and added to the disk group as the
first operations after creating rootdg. Some or all disks added to the rootdg disk group should also be
added to the volboot bootstrap file. The nconfig and nlog operands can be used to configure the number of
configuration database copies and kernel log copies that are maintained for a
disk group. The config-copies and log-copies values are either a decimal number (including 0 or -1) or set
to all or default. A value of all or -1 signifies that all configuration or log copies on all disks in the disk group
are to be maintained. A value of default or 0 (this is also the default value) signifies that VxVM is to manage
copies that are distributed in a reasonable pat- tern throughout the disks, controllers and enclosures on the
system. Any other number signifies that a particular number of copies should be maintained (or all copies, if
that number is larger than the number of available configuration or log copies on all disks).
When a specific number (or default) is requested, configuration copies are distributed across the
enclosures on the system. The number of copies in each enclosure is proportional to the number of disks in
that enclosure. With the default policy, at least one configuration and log copy is maintained for each
enclosure. It is ensured that at least one configuration and log copy is maintained for each host controller
connected to an enclosure. If this does not result in allocating at least 4 copies, then additional copies are
spread uniformly across enclosures.
Note: If a policy other than all is used, then some disks do not have up-to-date, online configuration and log
copies. As a result, it is possible that some number of disk failures can leave a disk group unusable, even if
some disks in the disk group remain usable. The default policy allocates a sufficient number of copies, in a
sufficient spread of locations, that such a scenario is very unlikely to occur.
Since disk groups can be moved between systems, it is desirable that device numbers used for volumes be
allocated in separate ranges for each disk group. That way, an administrator can choose ranges such that
all disk groups in a group of machines can be moved around without causing dev ice number collisions.
Collisions may occur because VxVM stores device numbers in disk group configurations, so that the same
numbers can be used after a reboot (which is necessary for use with NFS, which requires persistency of
device numbers). If two systems use the same device numbers for a set of volumes, and if a disk group
from one machine is moved to the other, then VxVM may be forced to temporarily remap some devices.
A base volume device minor number can be set for a disk group with the minor operand. Volume device
numbers for a disk group are chosen to have minor numbers starting at this base minor number. Minor
numbers can range up to 131071, so if it is presumed that no more than 1000 volumes would ever be
created in any one disk group, 131 different ranges of minor numbers are available for different disk
groups. A reasonably sized range should be left at the end for temporary device number remappings (in the
event that two device numbers still conflict).
If no minor operand is specified on the init command line, then VxVM chooses a random number of at least
1000 that is a multiple of 1000, and yields a usable range of 1000 device numbers. This default number is
chosen such that it does not overlap within a range of 1000 of any currently imported disk groups, and does
not overlap any currently allocated volume device numbers.
Note : The default policy is likely to ensure that a small number of disk groups can be merged successfully
between a set of machines. However, in cases where disk groups are merged automatically using fail-over
mechanisms, the administrator should select ranges that are known to avoid overlap.
In a cluster environment, the -s option defines a new disk group which is cluster-sharable while the cluster
is active. It is the responsibility of the user to ensure that disks specified as members of a cluster-sharable
disk group are physically accessible from the hosts that make up the cluster. The disks in a shared disk
group are stamped with the ID of the cluster to which the hosts belong and are marked with the shared flag.
When a host joins a cluster, it automatically imports disk groups whose disks are stamped with the cluster
ID.
Trying to create a shared disk group during a cluster reconfiguration fails.
Note : Volumes in shared disk groups must have the same minor number on all nodes in the cluster. If
there is a conflict when a node attempts to join the cluster, the join fails. In that case, the administrator
should use the reminor operation on the joined node(s) to resolve the conflict. In a cluster where more than
one node is joined, the administrator should use a base minor number which does not conflict on any node.
Veritas Commands
Page 15 of 93
If a version is specified with the -T option, the disk group is initialized with that disk group version. This
limits the operations that can be performed and features that can be used to those supported by the
specified disk group version. This makes the disk group compatible with releases of VxVM that support that
version. If no version is specified, the disk group is initialized with the highest versions supported by the
release of VxVM currently running on the system. See the vxdg upgrade operation for more information.
join Moves all objects from the imported source disk group, sourcedg, to the imported target diskgroup,
targetdg. At the conclusion of the move, sourcedg is removed.
The source disk group and target disk group to be joined must both be either private or shared. If one disk
group is private and the other is shared, deport and reimport the private disk group as shared before
performing the join.
The -o verify and -o override options modify the default behavior of a move, split or join operation that
includes disks from an EMC array. Usually, if the EMC license is present, the EMC disk compatibility check
is performed for each disk that is involved in a move. If the compatibility check succeeds, the normal
operation takes place. An internal check is made to ensure the configuration has not changed since the
compatibility check was performed. If it was changed, the entire process is retried.
If -o verify is specified, the access names of the disks to be moved are returned but the operation does not
take place.
If -o override is specified, the operation is performed without any EMC checking.
list Lists the contents of disk groups. If no diskgroup arguments are specified, then all disk groups are listed
in an abbreviated one-line format. If diskgroup arguments are specified, then a longer format is used to
indicate the status of the disk group, and of the specified disk group configuration.
If the -q option is specified, then no header is printed describing output fields. This option has no effect with
the long formats generated with diskgroup arguments.
In a cluster environment, if the -s option is specified, all cluster-shared disk groups are listed in a one-line
format. If diskgroup arguments are specified, -s has no effect.
listmove Displays a list of all objects, including all objects in hierarchies, that would move from the
imported source disk group, sourcedg, to the imported target disk group, targetdg, as implied by the
specified list of objects. The items in the specified object list must be top-level objects, disk media objects
or disk access objects. This command is used to confirm the validity and object content of a proposed
move operation without actually moving any objects.
move Moves the specified objects together with their hierarchies from the imported source disk group,
sourcedg, to the imported target disk group, targetdg.
The items in the object list must be top-level objects, disk media objects or disk access objects. The list
must define a set of self-contained objects, unless the -o expand option is specified. (Self-contained means
that the disks used by the selected objects should not contain any objects that are not selected for the
move.) If the -o expand option is specified, the object set is expanded to be self-contained.
The source disk group and target disk group must both be either private or shared. If one disk group is
private and the other is shared, deport and reimport the private disk group as shared before performing the
move.
See vxdg join for a description of the usage of the -o override and -o verify options.
nohotuse Lists free space that cannot be used by hot-relocation to replace failed subdisks. If a disk- group
is specified, the output is limited to the indicated diskgroup, otherwise nohotuse space from all disk groups
is listed. If disks are specified, by disk medianame, then the output is restricted to the indicated disks. A
region of nohotuse space is identified by disk medianame, a physical device tag, an offset relative to the
beginning of the public region for the media, and a length. The physical device tag is a reference that
indicates which physical device the disk media is defined on. It appears as a truncated disk access name. If
the -q option is specified, then no header is printed describing output fields.
recover Attempts to manually recover an incomplete move, split or join operation using either of the disk
groups that was involved in the operation.
In the event that the recovery cannot complete the operation, the -o clean option clears the MOVE flags
from the tutil0 fields of the objects in the disk group.
The -o remove option removes all objects marked with the MOVE flag from the disk group.
reminor Changes the base minor number for a disk group, and renumbers all devices in the disk group to
a range starting at that number. If the device for a volume is open, then the old device number remains in
effect until the system is rebooted or until the disk group is deported and re-imported. Also, if you close an
Veritas Commands
Page 16 of 93
open volume, then the user can execute vxdg reminor again to cause the renumbering to take effect
without rebooting or reimporting. A new device number may also overlap with a temporary renumbering for
a volume device. This also requires a reboot or reimport for the new device numbering to take effect. A
temporary renumbering can happen in the following situations: when two volumes (for example, volumes in
two different disk groups) share the same permanently assigned device number, in which case one of the
volumes is renumbered temporarily to use an alternate device number; or when the persistent device
number for a volume was changed, but the active device number could not be changed to match. The
active number may be left unchanged after a persistent device number change either because the volume
device was open, or because the new number was in use as the active device number for another volume.
vxdg fails if you try to use a range of numbers that is currently in use as a persistent (not a temporary)
device number. You can force use of the number range with use of the -f option. With -f, some device
renumberings may not take effect until a reboot or a re-import (just as with open volumes). Also, if you force
volumes in two disk groups to use the same device number, then one of the volumes is temporarily
renumbered on the next reboot. Which volume device is renumbered should be considered random, except
that device numberings in the rootdg disk group take precedence over all others.
The -f option should be used only when swapping the device number ranges used by two or more disk
groups. To swap the number ranges for two disk groups, you would use -f when renumbering the first disk
group to use the range of the second disk group. Renumbering the second disk group to the first range
does not require the use of -f.
repldisk Dissociates the DA record from the DM record named by spare-medianame, and reassociates it
with the unassociated DM record named by unassoc medianame. Both unassoc-medianame and sparemedianame must be members of the disk group named by the diskgroup argument (rootdg by default).
However, if the -k flag is specified, then the disk media records for the spare-medianame are retained,
although in a removed state.
rmdisk Removes the specified disk or disks from a disk group (rootdg by default). The last disk cannot be
removed from its disk group. It is not possible to remove the last disk containing a valid disk group
configuration or log copy from its disk group. Typically, the rmdisk operation fails if subdisk records point to
the named disk media records. However, if the -k flag is specified, then the disk media records are kept,
although in a removed state, and the subdisk records still point to them. The subdisks, and any plexes that
refer to them, remain unusable until the disk is re-added using the -k option to the adddisk operation. Any
volumes are disabled that become unusable because all plexes become unusable.
set Changes disk group characteristics. Specify changes by entering arguments after the set key- word in
the form attribute=value. The only settable attribute is the activation mode of the disk group:
activation=mode. The activation mode of a disk group allows applications to read and write to volumes in
the disk group. The following are the valid activation modes and corresponding read/write capability for
non-shared disk groups:
readwrite | rw Volumes in the disk group are available for read and write access.
readonly | ro Volumes in the disk group are available for read access only.
off Volumes in the disk group are not available for read or write access.
For a shared disk group, the activation mode is on a per node basis. The following are the valid activation
modes and corresponding read/write capability for shared disk groups:
exclusivewrite | ew The node has exclusive write access to volumes in the disk group. No other node in
the cluster can activate the disk group for write access.
sharedwrite | sw The node has write access to volumes in the disk group. Other nodes can activate the
disk group for shared write access.
readonly | ro The node has read access to volumes in the disk group. It has no write access and denies
write access to all other nodes in the cluster.
sharedread | sr The node has read access to volumes in the disk group, but no write access, However,
other nodes can activate the disk group for write access.
spare Lists spare space that can be used for relocating subdisks during recovery. If a disk group is
specified, the output is limited to the indicated disk group, otherwise spare space is listed from all disk
groups. If disks are specified, by disk media name, the output is restricted to the indicated disks. A region of
spare space is identified by disk media name, a physical device tag, an offset relative to the beginning of
the public region for the media, and a length. The physical device tag is a reference that indicates which
physical device the disk media is defined on. It appears as a truncated disk access name. If the -q option is
specified, then no header is printed describing output fields.
split Moves the specified objects together with their hierarchies from the imported source disk group,
sourcedg, to a newly created target disk group, targetdg.
Veritas Commands
Page 17 of 93
This operation fails if it would remove all the disks from the source disk group, or if an imported disk group
exists with the same name as the target disk group. An existing deported disk group is destroyed if it has
the same name as the target disk group (as is the case for the vxdg init command).
The items in the object list must be top-level objects, disk media objects or disk access objects. The list
must define a set of selfcontained objects, unless the -o expand option is specified. (Self-contained means
that the disks used by the selected objects should not contain any objects that are not selected for the
move.) If the -o expand option is specified, the object set is expanded to be self-contained. The newly
created target disk group is imported as shared if the source disk group is shared; otherwise, it is imported
as private. The -C, -f, and -t options are import options for the new disk group. See the description of vxdg
import for details of their use.
See vxdg join for a description of the usage of the -o override and -o verify options.
upgrade Upgrades the disk group to the latest VxVM version. By default, the disk group version is updated
to the running version of VxVM. The -T option upgrades the disk group to a specified version. The following
section lists each disk group version, the features it supports, and the VxVM release that introduced it.
Note: Some VxVM versions are not available on all supported OS platforms.
10 Supports only the most basic volume management features of mirroring and simple striping. This format
was introduced in VxVM Release 1.2. Starting with VxVM Release 3.0, disk groups of version 10 can be
imported, but no operations can be performed on the objects it contains (for example, starting volumes or
adding mirrors). The only operation supported is to upgrade the disk group to a later release.
20 Introduced support for RAID-5 Volumes, new style stripes, recovery checkpointing, disk group
configuration/klog copy limiting, and Dirty Region Logging. This version was introduced in VxVM Release
2.0 and is supported by all subsequent releases of VxVM.
30 Enabled support for the Oracle Resilvering Interface. This version was introduced in VxVM Release 2.2
and is supported by all subsequent releases of VxVM.
40 Support for Hot Relocation. Introduced in VxVM Release 2.3 and is supported by all subsequent
releases of VxVM.
60 Support for Online Relayout, safe RAID-5 subdisk moves, Striped Mirrors, and RAID-5 Snapshots.
Introduced in Release 3.0.
70 Non-Persistent FastResync, VERITAS Volume Replicator (VVR) enhancements, and Unrelocate.
Introduced in Release 3.1.
80 VERITAS Volume Replicator (VVR) Enhancements. Introduced in Release 3.1.1.
90 Cluster support for Oracle Resilvering, disk group move, split and join, Device Discovery Layer (DDL),
layered volume support in clusters, ordered allocation, OS independent Naming support, and Persistent
FastResync. Introduced in Release 3.2. To determine the version of a disk group, use the vxdg list
diskgroup command.
Hardware-Specific Options Some environments provide guidelines to optimize VxVM's interaction with
intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when creating disk
groups and adding disks to disk groups. By default, vxdg only allows disk groups to contain disks that
conform with these guidelines. The following options change the behavior of vxdg:
-o override Performs the disk group task and ignores any storage-specific guidelines. Overriding the
guidelines is not recommended as it can result in incompatible objects, or objects that cannot be
administered by VxVM.
-o verify Verifies that the specified disk group task can be performed without violating any storage-specific
guidelines, but does not perform the task. If any guidelines are violated, vxdg exits with an error message.
Note : These options need a specific license. Without the license, vxdg ignores the specified option.
---------------------------------------------------------------------------------------------------------------------------------------vxddladm - Device Discovery Layer subsystem administration
SYNOPSIS
/etc/vx/bin/vxddladm keyword [attribute[=value] ...]
vxddladm [-a | -f | -n] addforeign {dirname=directory | pathname=device}
vxddladm addjbod vid=vendor-id [pid=product-id] [opcode=scsi_opcode]
[pagecode=page_code] [offset=page_offset] [length=sno_length]
vxddladm excludearray libname=libname
vxddladm excludearray arrayname=arrayname
vxddladm excludearray vid=vendor-id pid=product-id
Veritas Commands
Page 18 of 93
Veritas Commands
Page 19 of 93
Veritas Commands
Page 20 of 93
you are prompted whether to continue the operation. If the device is initialized, vxdisksetup is called to set
up public and private regions and to create the disk header. Given an initialized disk, the operation replaces
the disk in a disk group with vxdg -k adddisk.
Mirror volumes on a disk Prompts for a disk, by media name. It then prompts for a destination disk within
the same disk group, also by media name. Specifying no destination disks indicates that any disk can be
the destination. The operation calls vxmirror to mirror the volumes.
Move volumes from a disk Prompts for a disk, by media name. It then prompts for a possible list of
destination disks, also by disk media name. Specifying no destina- tion disks indicates that any disk is
suitable. The operation calls vxevac to move subdisks off the disk.
Enable access to (import) a disk group Prompts for a disk group name. The operation calls vxdg import
to import the disk group stored on that disk.
Remove access to (deport) a disk group Prompts for a disk group name. The prompt lists alternate disk
groups and the disks (media name and access name) that they contain. The operation calls vxdg deport.
Enable (online) a disk device Prompts for a disk device. The prompt lets you display the disks on the
system. The operation functions only for disks currently offline. It then makes the disk accessible.
Disable (offline) a disk device Prompts for a disk device. The prompt lets you display the disks on the
system. The operation functions only for disks currently online, but not part of any disk group. It then marks
the disk as offline such that VxVM no longer tries to access the disk.
Mark a disk as a spare for a disk group Sets up a disk as a spare device for its disk group. A spare disk
can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked
as a spare.
Turn off the spare flag for a disk Removes a disk from the list of spare disks, and returns its space to the
general pool of available space.
Unrelocate subdisks back to a disk Moves subdisks which were hot-relocated following a disk failure
back to the original disk, or to a disk with a different name, possibly with a different offset.
Exclude a disk from hot-relocation use Sets up a disk to be excluded from use by hot- relocation. The
disk is marked as nohotuse and it cannot be used by hot-relocation to replace a disk that has failed.
However, it remains available to be used as free space for its disk group.
Make a disk available for hot-relocation use Turns off the nohotuse flag on a disk. Use this option to make a
disk available for hot-relocation use. This only applies to disks that were previously excluded from hotrelocation use.
Prevent multipathing/Suppress devices from VxVM's view Excludes devices from VxVM's view, or prevents
them from being multipathed by the dynamic multipathing (DMP) driver, vxdmp. There are three ways of
specifying the devices on which these operations are to be performed:
o As a controller for all devices connected through the controller.
o As a physical pathname for all devices under that path.
o As a combination of the Vendor ID and Product ID (VID:PID) for all devices of that type.
This option also provides a method to define path-groups in case of disks which are not multipathed by
VxVM. Only one path from a pathgroup will be made visible to VxVM. This is useful to avoid duplicate
entries for devices that are not multipathed by vxdmp. Allow multipathing/Unsuppress devices from VxVM's
view Makes devices visible to VxVM again or makes vxdmp multipath these devices again. This can be
performed only on devices that have already been specified using the "Prevent multipathing/Suppress
devices from VxVM's view" option.
List currently suppressed/non-multipathed devices Lists all devices suppressed from VxVM's view and all
devices prevented from being multipathed by vxdmp.
Change the disk naming scheme Changes the disk naming scheme from the c#t#d# format to enclosurebased. Alternatively, if the existing naming scheme is enclosure-based, it is changed to c#t#d# format.
Get the newly connected/zoned disks in VxVM view Scans and configures any new disk devices that are
attached to the host, disk devices that became online, or fibre channel devices that were zoned to host bus
adapters connected to this host.
List disk information Displays a list of disks. You can also choose to list detailed information about the disk
at a specific disk device address.
Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with
intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks
to disk groups and when mirroring the volumes on a disk. If the operation fails due to these guideline(s),
you are prompted to use the force option. The force option ignores any such storage-specific guidelines.
Veritas Commands
Page 21 of 93
FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadm operations.
/etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadm operations.
/etc/vx/enclr.exclude Specifies the names of enclosures to exclude from vxdiskadm operations.
---------------------------------------------------------------------------------------------------------------------------------------vxmake - create VxVM configuration records
SYNOPSIS
vxmake [-pV ] [-g diskgroup] [-o useopt] [-U usetype] [-T a|o] [-d
descfile]
vxmake [-pV ] [-g diskgroup] [-o useopt] dco name [attribute=value...]
vxmake [-pV ] [-g diskgroup] [-o useopt] plex name [attribute=value...]
vxmake [-pV ] [-g diskgroup] rlink name [attribute=value...]
vxmake [-pV ] [-g diskgroup] rvg name [attribute=value...]
vxmake [-pV ] [-g diskgroup] [-o useopt] sd name [attribute=value...]
vxmake [-pV ] [-g
[attribute=value...]
diskgroup]
[-o
useopt]
[-U
usetype]
vol
name
DESCRIPTION The vxmake utility creates subdisk, plex, and volume records for VxVM (VxVM). Records
can be created entirely from parameters specified on the command line, or they can be created using a
description file.
vxmake can also create a data change object (DCO) that is used to implement Persistent FastResync on a
volume. When the VERITAS Volume Replicator (VVR) option is avail- able, vxmake can also create RVG
and RLINK records. RVG and RLINK records only support gen usage.
Note : The vxprint utility can be used with vxmake to perform the functions of a rudimentary configuration
backup and restore. This should be the primary use of vxmake. Use of vxmake other than through a
description file containing content mostly gathered from either the vxprint utility is discouraged in VxVM
releases starting with 3.0. The vxassist utility and the graphical user interface are the recommended means
of creating new or modified volume hierarchies.
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. For convenience, a special attribute
form can be used for subdisks specified directly from the command line. This special attribute form is:
devicepath,offset[,len] or 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. This is the default behavior. The -T option allows users to
select transaction control that differs from the default behavior when restoring records within a volume
hierarchy from a description file. This is particularly helpful with layered volume hierarchies that include
subvolumes.
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.
OPTIONS
Veritas Commands
Page 22 of 93
-d descfile Specify the name of a description file to use for building subdisks, plexes, volumes, RVGs and
RLINKs. If the descfile option argument is -d, then the description file is read from the standard input. If no
operands are specified, and no descfile is specified, then a description file is read from the standard input.
This option is ignored for records that are specified directly on the command line.
-g diskgroup Specify the disk group for the operation. The disk group can be specified either by name or
by disk group ID.
-o useopt Give usage-type-specific options to the usage type utility.
-p Print a list of all changes that would be made to the standard output, but do not make those changes.
The output is in the vxmake description file format. All computable and potentially useful attributes are
printed for new records. For records that would be modified, only those attributes that would change are
printed, along with an extra attribute declaration, CHANGED=yes. In this way the -p option performs a
preview run of the utilities.
This option is intended for use with higher-level tools that preview record creations, particularly with respect
to usage-type-dependent attribute modifications.
-T This option controls the unit of work that vxmake uses to make records within a single transaction when
restoring records from a description file. If the option argument is a or the -T option is absent altogether,
then vxmake attempts to create all records within a single transaction, so that either all records are created
or no records are created. This behavior is considered the default behavior and it is backward- compatible
with previous releases of VxVM. If the option argument is o, then one complete top-level object (Volume
hierarchy, dissociated plex hierarchy, or dissociated subdisk hierarchy) is created at a time, and if multiple
top-level objects are to be created from the same description file, then vxmake attempts to create each one
a top-level object at a time in its own transaction. Note that should some objects be creatable and some
not, the configuration results in those objects that vxmake was actually able to create. This option can be
used for any record hierarchy. Because record hierarchies with layered volumes may contain many
subordinate records (such as subvolumes), the -T o option is particularly useful for safely creating these
kinds of objects.
-U usetype Use usetype as the default usage type for volumes. This option has no effect if only subdisks
and plexes are created, or if the usage type for a volume is specified directly with the description file
variable usetype.
-V Display a list of utilities that would be called from vxmake, along with the arguments that would be
passed. The -V option performs a preview run of the utilities; the utilities are not actually called, and no
changes are made to the volume configuration database.
Attribute Specification Rules The only attributes that must be specified are the path and len attributes for
subdisk records, and a usage type for volume records. In addition, if the layout attribute for a plex record is
set to STRIPE, then a positive value must be specified for the stwidth attribute. Also, if no subdisks are
specified for a plex of the STRIPE layout, the ncolumn attribute must be specified.
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.
Subdisks 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, 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).
Plexes 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.
Veritas Commands
Page 23 of 93
Veritas Commands
Page 24 of 93
Veritas Commands
Page 25 of 93
Veritas Commands
Page 26 of 93
Veritas Commands
Page 27 of 93
plexes.
VxVM 3.5 Last change: 1 Oct 2002 8
Maintenance Commands vxmake(1M)
EXAMPLES
The following is an example of a vxmake description file:
#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,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"
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.
Note: More than one attribute may be declared on a single
line if separated by one or more tabs or spaces. An attribute and its specified values must be defined on the same
line. Attributes that are specified on lines subsequent to
the first line for an object definition must be preceded by
one or more tabs or spaces.
For striped or RAID-5 plex subdisk associations, if one
number is specified for the column and column offset field,
the number is interpreted as a column number and the subdisk
Veritas Commands
Page 28 of 93
Veritas Commands
Page 29 of 93
Veritas Commands
Page 30 of 93
attribute...]
vxassist [ options ] remove { volume | mirror | log } volume
[storage-spec...] [ attribute...]
vxassist [ options ] shrinkby volume lengthchange [ attribute...]
vxassist [ options ] shrinkto volume newlength [ attribute...]
vxassist [ options ] snapabort volume
vxassist [ options ] snapback snapvolume
vxassist [ options ] snapclear volume [snap_object]
vxassist [ options ] snapprint [volume]
vxassist [ options ] snapshot volume snapvolume [ attribute...]
VxVM 3.5 Last change: 1 Jun 2002 1
Maintenance Commands vxassist(1M)
vxassist [ options ] [ -b ] snapstart volume [ attribute...]
vxassist [ options ] snapwait volume
DESCRIPTION
The vxassist utility is a command-line interface to the VERITAS Volume Manager (VxVM) that:
o Finds space for and creates volumes
o Performs volume conversion
o Adds mirrors and logs to existing volumes
o Extends and shrinks existing volumes
o Migrates data from a specified set of disks
o Provides facilities for the online backup of existing volumes
Veritas Commands
Page 31 of 93
Veritas Commands
Page 32 of 93
Veritas Commands
Page 33 of 93
Veritas Commands
Page 34 of 93
Veritas Commands
Page 35 of 93
Veritas Commands
Page 36 of 93
Veritas Commands
Page 37 of 93
Veritas Commands
Page 38 of 93
convert from a 4-column mirror-stripe to a 5column mirror-stripe, first relayout the volume as
a stripe-mirror:
vxassist relayout vol1 nstripe=5
If you view the volume with vxprint during relayout, the volume shows several subvolumes that are
used during the change, and a more complex configuration than usual.
After the new column is added, the volume is in
stripe-mirror layout. Use vxassist convert to convert back to a mirror-stripe layout:
vxassist convert vol1 layout=mirror-stripe
Note: If the system crashes during relayout or
conversion, the process continues when the system
is rebooted. However, if the crash occurred during the first stage of a two-stage relayout and
convert operation, only the first stage is subsequently completed after rebooting. You must run
vxassist convert manually to complete the second
stage.
remove volume | mirror | log
Deletes the entire volume, one or more mirrors, or
one or more logs, according to the argument. When
deleting a mirror or a log, specify the storage to
be removed using the attribute form !diskname (see
Storage Specifications below). For example, to
remove a mirror on disk01, enter:
vxassist remove mirror vol01 !disk01
See vxplex(1M) for an example of an alternative
method of removing a mirror from a volume.
Use the logtype= attribute to specify the type of
log to be removed. For example, specify
logtype=drl to remove a DRL log.
VxVM 3.5 Last change: 1 Jun 2002 8
Maintenance Commands vxassist(1M)
Veritas Commands
Page 39 of 93
Veritas Commands
Page 40 of 93
Veritas Commands
Page 41 of 93
Veritas Commands
Page 42 of 93
Veritas Commands
Page 43 of 93
Veritas Commands
Page 44 of 93
specified.
The comment attribute may also be used to set the
comment field for the snapshot volume.
The following are examples of the use of the nmirror and comment attributes:
vxassist snapshot nmirror=2 \
comment="mirrored snapvol for myvol" myvol snapvol
Some usage types attempt to synchronize any inmemory data associated with the volume (such as
unwritten file system modifications) when the
snapshot operation is done. In particular, if the
fsgen usage type is used with a volume containing
a VERITAS File System (VxFS), then cooperating
procedures ensure that all file system data is
consistently flushed to the volume. For ufs and
s5, the synchronization operation calls sync.
This makes the snapshot a better image, but it may
leave some inconsistencies between in-memory file
system data and the data residing on the backup
image.
The snapshot command accepts more than one volume.
All the given volumes are split atomically (in a
single transaction). That is, all the given
volumes are relatively consistent as a result of
taking the snapshot. If you specify the -o allvols
option without giving any volume names, vxassist
attempts to create a sufficiently long vxplex command to take a snapshot of all the volumes in the
disk group. You can use the -o name=pattern option
to specify a name for the new volume. Otherwise,
the default name assigned to the new volume has
the form SNAP%d-%v.
snapstart Creates a plex and attaches it to the named volume
as a snapshot mirror. When the attach completes,
the plex has state SNAPDONE and is a candidate for
selection by the snapshot operation. Attributes
can be specified to indicate the desired properties of the snapshot mirror.
VxVM 3.5 Last change: 1 Jun 2002 13
Veritas Commands
Page 45 of 93
Veritas Commands
Page 46 of 93
-E template_file
Specifies the path name of a template file that
contains SAN storage set specifications. See the
section Using SAN Storage Attributes with vxassist
for more information.
-f Forces operations not usually allowed by vxassist.
-g diskgroup
VxVM 3.5 Last change: 1 Jun 2002 14
Maintenance Commands vxassist(1M)
Specifies the disk group for the operation, either
by disk group ID or by disk group name. By
default, the disk group is chosen based on the
medianame operands (if any) for the vxassist make
operation, or based on the volume operands for all
other operations.
-n Prevents the system defaults file being read.
-o useopt Passes in options specific to a usage type to the
operation. A certain set of operations are
expected to be implemented by all usage types:
allplexes Specifies that all available snapshot
plexes in a disk group are to be reattached to their original volume during a
snapback operation.
allvols Takes a snapshot of all the volumes in
the disk group. An error results if one
or more volumes do not have a plex that
is usable for the snapshot.
iosize=size
Performs copy and recovery operations in
regions with the length specified by
size, which is a standard VERITAS Volume
Manager length number (see vxintro(1M)).
Specifying a larger number typically
causes the operation to complete sooner,
but with greater impact on other
processes using the volume. The default
Veritas Commands
Page 47 of 93
Veritas Commands
Page 48 of 93
Veritas Commands
Page 49 of 93
resyncfromreplica
Performs a resync using the data in the
snap plex during a snapback.
sequential
When specified with the useopt numchild
for values of number greater than 1, the
child processes co-operate in resynchronizing regions of the volume that
are close together, starting at the
beginning of the volume and moving to
the end. This creates more overhead for
the resynchronization, but it potentially makes better use of the sequential read-ahead buffer of the physical
disks.
slow[=iodelay]
Reduces the impact on system performance
of copy operations. Copy and plex consistency recovery operations are usually
a set of short operations on small
regions of the volume (normally from 16
kilobytes to 128 kilobytes). This option
inserts a delay between the recovery of
each such region. A specific delay can
be specified with iodelay as a number of
milliseconds, or a default is chosen
(normally 250 milliseconds).
-p Prints only the maximum size with no text wrappers
(used with maxsize and maxgrow).
-r Includes spare disks (reserved for hot-relocation)
in the calculation.
-t tasktag
Marks any tasks that are registered to track the
progress of an operation with the tag tasktag.
This option is passed to utilities called by
VxVM 3.5 Last change: 1 Jun 2002 17
Maintenance Commands vxassist(1M)
Veritas Commands
Page 50 of 93
Veritas Commands
Page 51 of 93
fied option.
Refer to the vendor-specific documentation for more information on how intelligent storage systems can interact with
VxVM.
VxVM 3.5 Last change: 1 Jun 2002 18
Maintenance Commands vxassist(1M)
ATTRIBUTES
Attribute values for various purposes can be specified with
arguments of the form attribute=value. Attributes can also
be passed in through a defaults file. Default attribute
values can be stored in the file /etc/default/vxassist.
Attributes are selected according to the order in which they
are scanned. In general they are taken in decreasing priority of being specified on:
1. The command line.
2. The specified defaults file (as supplied with the -d command line argument).
3. The system defaults file (as specified in
/etc/default/vxassist).
Attributes from all sources have the same form. However, in
some cases, command-line attributes change default behaviors
in ways that attributes in the defaults file do not. In particular, references to mirroring (such as specifying a mirror count) or logging (such as specifying a log count or
length) on the command line cause mirroring or logging to
happen by default. If such attributes are specified in a
defaults file, they indicate the attributes that would be
used if mirroring or logging were enabled.
Attributes are either storage specifications (possibly
negated), or are in the form attribute=value. In a defaults
file, attributes are separated by a space or are on separate
lines. Blank lines in a defaults file are ignored, and comments can be included with the standard # convention.
Storage Specifications
Note: You cannot use storage specification attributes in
Veritas Commands
Page 52 of 93
Veritas Commands
Page 53 of 93
Veritas Commands
Page 54 of 93
Veritas Commands
Page 55 of 93
Veritas Commands
Page 56 of 93
Veritas Commands
Page 57 of 93
Veritas Commands
Page 58 of 93
Veritas Commands
Page 59 of 93
Veritas Commands
Page 60 of 93
Veritas Commands
Page 61 of 93
Veritas Commands
Page 62 of 93
Veritas Commands
Page 63 of 93
Veritas Commands
Page 64 of 93
Veritas Commands
Page 65 of 93
columns, cols)
Specifies the number of stripe columns to use when
creating a new RAID-5 volume (with the make operation) or when creating a striped plex (with the
make, relayout, mirror, and snapstart operations).
The default is to adjust to the number of available disks. For the relayout operation, the
default is the same number of stripe columns the
volume has. For a relayout, this value can be preceded by a + or a - to add or subtract columns.
probe_granularity=size
Specifies the granularity for the maxsize request.
The default size value is 1m (1 megabyte).
raid5_stripeunit=width
(alias: raid5_stwid, raid5_st_width,
raid5_stwidth, raid_st_width, raid_stripeunitsize,
raid5_stripeunitsize, raid5_stripeunitwidth,
raid_stwid, raid_stwidth, raid_stripeunit,
raid_stripeunitwidth)
Specifies the stripe unit size to use when creating a new RAID-5 volume (default value is 16k (16
kilobytes)). This attribute is used only with the
make operation.
raid5loglen=length (alias: raidloglen)
Specifies the log length to use when adding the
first log to a RAID-5 volume. The default is four
times the full stripe width (the stripe unit size
times the number of stripe columns).
VxVM 3.5 Last change: 1 Jun 2002 30
Maintenance Commands vxassist(1M)
regionloglen=length (alias: drlloglen, drllen)
Specifies the log subdisk length to use when
adding the first log subdisk to a mirrored volume.
The default is chosen based on a formula involving
the volume length.
salcontact=no
If SAN Access Layer (SAL) is installed and running
Veritas Commands
Page 66 of 93
Veritas Commands
Page 67 of 93
Veritas Commands
Page 68 of 93
user=owning-user
Specifies the user ID for a new volume (default
value is root). The user ID can be specified
numerically or it can be a system login name.
This attribute is used only with the make operation.
usetype=volume-usage-type
VxVM 3.5 Last change: 1 Jun 2002 32
Maintenance Commands vxassist(1M)
Specifies the usage type to use when creating a
new volume (default value is raid5 for RAID-5
volumes; otherwise fsgens the default). This
attribute is only used with the make operation.
The usage type can also be specified using the -U
option.
wantalloc=storage-spec[,storage-spec,...]
Specifies a set of desired storage specifications.
This is useful in a defaults file to indicate
desired storage specifications that should be discarded if they fail to yield a reasonable set of
allocations. The format is the same as for the
alloc attribute (a comma-separated list of storage
specifications).
For example, a defaults file can name a specific
controller type to use for allocations, if possible. When all disks on that type of controller are
full, other controllers are used.
Note: You cannot use wantalloc in combination with
SAN storage set specifications. See the section
Using SAN Storage Attributes with vxassist for
more information.
wantmirror=diskclass[,diskclass,...]
Specifies a desired list of disk class mirroring
specifications. This is useful in a defaults file
to indicate a set of desired mirroring constraints
that can be dropped if they fail to yield a reasonable set of allocations.
Veritas Commands
Page 69 of 93
Veritas Commands
Page 70 of 93
Layout Specifications
The layout attribute specifies a comma-separated list of
simple parameters (with no arguments) that apply to vxassist
operations.
Two new layouts were added in the 3.0 release of VxVM:
stripe-mirror and concat-mirror. In previous releases,
whenever mirroring was used, the mirroring had to happen
above striping or concatenation. Now there can be mirroring
both above and below striping and concatenation.
Putting mirroring below striping mirrors each column of the
stripe. If the stripe is large enough to have multiple subdisks per column, each subdisk can be individually mirrored.
A similar concatenated volume would also mirror each subdisk
individually. These new layouts enhance redundancy and
reduce recovery time in case of an error. In a mirrorstripe layout, if a disk fails, the entire plex is detached,
thereby losing redundancy on the entire volume. When the
disk is replaced, the entire plex must be brought up to
date. Recovering the entire plex can take a substantial
amount of time. If a disk fails in a stripe-mirror layout,
only the failing subdisk must be detached, and only that
portion of the volume loses redundancy. When the disk is
replaced, only a portion of the volume needs to be
recovered.
The new volume layouts are more complex than the older
volume layouts. Because the advantages of recovery time and
improved redundancy are more important for larger volumes,
VxVM 3.5 Last change: 1 Jun 2002 34
Maintenance Commands vxassist(1M)
it is best to continue using mirror-stripe and mirror-concat
for most volumes and only use stripe-mirror and concatmirror for very large volumes.
You can specify layout=mirror-stripe or layout=stripe-mirror
to implement the desired layout. If you specify
layout=stripe,mirror or layout=mirror,stripe, vxassist
automatically determines the best layout for the volume.
Unless there is a reason to implement a particular layout,
it is best to let vxassist create the layout for each
volume. Because the advantages of the new layouts are
Veritas Commands
Page 71 of 93
related to the size of the volume, vxassist creates the simplest configuration for smaller volumes and the more complex
stripe-mirror for larger volumes.
The attributes stripe-mirror-col-trigger-pt and stripemirror-col-split-trigger-pt control the selection. They can
be set in /etc/default/vxassist. Volumes that are smaller
than stripe-mirror-col-trigger-pt are created as mirrorstripe, and volumes that are larger are created as stripemirror. If vxassist creates the stripe-mirror and the
columns are larger than stripe-mirror-col-split-trigger-pt,
the individual subdisks are mirrored instead of mirroring
the columns of the stripe. By default, both of these attributes are set to one gigabyte.
The disk group must be created on a 3.0 or later release to
use the new layouts, but older disk groups can be updated.
See the vxdg upgrade command for more information on upgrading disk groups.
Defined layout specifications are:
concat-mirror
Specifies that new volumes should be concatenated
and mirrored. The mirroring is handled at each
subdisk level. The attribute stripe-mirror-colsplit-trigger-pt is applied.
contig, nocontig
Disallows or allows (default) plexes, regular
stripe columns, or RAID-5 stripe columns from
using multiple regions of disk. If contig is
specified, then plexes and columns must be allocated from a single contiguous region of disk. If
this is not possible, the allocation fails. By
default, vxassist tries to allocate space contiguously, but it can use multiple regions or multiple
disks if required.
diskalign, nodiskalign
Aligns (default for all volumes except layered
VxVM 3.5 Last change: 1 Jun 2002 35
Maintenance Commands vxassist(1M)
Veritas Commands
Page 72 of 93
Veritas Commands
Page 73 of 93
Veritas Commands
Page 74 of 93
Veritas Commands
Page 75 of 93
Veritas Commands
Page 76 of 93
Veritas Commands
Page 77 of 93
Veritas Commands
Page 78 of 93
in this example:
vxassist -g dg1 -E storage.def make vol3 100m
For example, the following complex set definition allows
storage to be allocated from any combination of disks at
locations loc1 and loc2:
confine {
select:location=loc1
select:location=loc2
}
This clause can also be written as follows:
confine {
select:location=loc1 ; select:location=loc2
}
Examples of Set Definitions
Allocate storage using only HITACHI disks:
confine:vendor=HITACHI
Allocate storage using only HITACHI disks of protection type
Raid5:
confine:vendor=HITACHI,protection=Raid5
Allocate storage using any combination of EMC and HITACHI
disks:
select:vendor=EMC,vendor=HITACHI
Do not allocate storage on EMC disks:
noneof:vendor=EMC
The following complex clause allocates storage using any
combination of EMC and HITACHI disks, and any combination of
Raid5 and Mirr2 protection:
VxVM 3.5 Last change: 1 Jun 2002 41
Maintenance Commands vxassist(1M)
Veritas Commands
Page 79 of 93
confine{
select:vendor=EMC,vendor=HITACHI
select:protection=Raid5,protection=Mirr2
}
Support for Remote Operation with SAL
If the host on which you are running vxassist is not the
primary SAL server, or the port used by the SAL daemon
(sald) is not the default (2802), specify the hostname of
the primary SAL server and the sald port in the file
/etc/default/vxassist_sal_info using the following format:
sal_primary = hostname
sal_port = port_number
The following is an example of such a file:
sal_primary = chives
sal_port = 1001
Note: If SAL cannot be contacted by vxassist for any reason
such as authentication failure, link failure and so on, it
issues a warning and completes execution normally. No LUN
attributes are retrieved from SAL in such a scenario.
Authentication with SAL
The user name to be authenticated by the SAL primary server
(if required) may be specified using the sal_username attribute. User names and passwords that VxVM is to use with SAL
may be specified using the vxspcshow command. See the
vxspcshow(1M) manual page for more information.
FILES
/etc/default/vxassist System default settings file
for vxassist attributes.
EXIT CODES
The vxassist utility exits with a non-zero status if the
attempted operation fails. A non-zero exit code is not a
complete indicator of the problems encountered, but rather
denotes the first condition that prevented further execution
of the utility.
---------------------------------------------------------------------------------------------------------------------------------------vxtunefs - tune a VxFS file system
SYNOPSIS
Veritas Commands
Page 80 of 93
Veritas Commands
Page 81 of 93
Veritas Commands
Page 82 of 93
volume geometry.
If the file system is being used with a hardware disk array
or another volume manager, align the parameters to match the
geometry of the logical disk. For disk striping and RAID-5
configurations, set read_pref_io to the stripe unit size or
interleave factor and set read_nstream to be the number of
columns. For disk striping configurations, set
write_pref_io and write_nstream to the same values as
read_pref_io and read_nstream, but for RAID-5 configurations, set write_pref_io, to the full stripe size and set
VxFS 3.5 Last change: 07 Jun 2002 2
Maintenance Commands vxtunefs(1M)
write_nstream to 1.
For an application to do efficient direct I/O or discovered
direct I/O, it should issue read requests that are equal to
the product of read_nstream and read_pref_io. In general,
any multiple or factor of read_nstream multiplied by
read_pref_io is a good size for performance. For writing,
the same general rule applies to the write_pref_io and
write_nstream parameters. When tuning a file system, the
best thing to do is use the tuning parameters under a real
workload.
If an application is doing sequential I/O to large files,
the application should issue requests larger than the
discovered_direct_iosz. This performs the I/O requests as
discovered direct I/O requests which are unbuffered like
direct I/O, but which do not require synchronous inode
updates when extending the file. If the file is too large
to fit in the cache, using unbuffered I/O avoids losing useful data out of the cache and lowers CPU overhead.
default_indir_size
On VxFS, files can have up to 10 variable sized extents
stored in the inode. After these extents are used, the
file must use indirect extents which are a fixed size
that is set when the file first uses indirect extents.
These indirect extents are 8K by default. The file
system does not use larger indirect extents because it
must fail a write and return ENOSPC if there are no
extents available that are the indirect extent size.
Veritas Commands
Page 83 of 93
Veritas Commands
Page 84 of 93
for subsequent writes, which improves the write performance during migration.
The hsm_write_prealloc parameter is implemented outside
of the DMAPI specification, and its usage has limitations depending on how the space within an HSM controlled file is managed. It is advisable to use
hsm_write_prealloc only when recommended by the HSM
application controlling the file system.
initial_extent_size
Changes the default size of the initial extent.
VxFS determines, based on the first write to a new
file, the size of the first extent to allocate to the
file. Typically the first extent is the smallest power
of 2 that is larger than the size of the first write.
If that power of 2 is less than 8K, the first extent
allocated is 8K. After the initial extent, the file
system increases the size of subsequent extents (see
max_seqio_extent_size) with each allocation.
Because most applications write to files using a buffer
size of 8K or less, the increasing extents start doubling from a small initial extent. initial_extent_size
changes the default initial extent size to a larger
value, so the doubling policy starts from a much larger
initial size, and the file system won't allocate a set
of small extents at the start of file.
Use this parameter only on file systems that have a
very large average file size. On such file systems,
there are fewer extents per file and less
VxFS 3.5 Last change: 07 Jun 2002 4
Maintenance Commands vxtunefs(1M)
fragmentation.
initial_extent_size is measured in file system blocks.
max_buf_data_size
Not available.
max_direct_iosz
Veritas Commands
Page 85 of 93
Veritas Commands
Page 86 of 93
Veritas Commands
Page 87 of 93
Veritas Commands
Page 88 of 93
Veritas Commands
Page 89 of 93
striping.
To change the value of vol_maxio, add an entry to
/etc/system and reboot for the change to take effect. The
following example sets the maximum I/O size to 16 MB. Note
that vol_maxio goes after the forceload entry.
forceload: drv/vxio
set vxio:vol_maxio=32768
The value of vol_maxio is in 512-byte sectors and is stored
as a 16-bit number, so it cannot be larger than 65535.
---------------------------------------------------------------------------------------------------------------------------------------The following examples verify a feature defined for the same
product. The first example identifies the product by its
license key, the second by its product name, and the third
by its product ID.
vxlictest -k PR66-WPBD-NZCY-P3ZP-CPOP -f "VxVM"
vxlictest -n "VERITAS Volume Manager" -f "VxVM"
vxlictest -i 78 -f "VxVM"
The following example uses quiet mode (the -q can also be
entered as the first argument):
vxlictest -k PR66-WPBD-NZCY-P3ZP-CPOP -f "VxVM" -q
The following example displays all the licensed features in
any keys installed for Volume Manager:
vxlictest -n "VERITAS Volume Manager" -l
The following example displays all the licensed features in
the specified key:
vxlictest -k PR66-WPBD-NZCY-P3ZP-CPOP -l
---------------------------------------------------------------------------------------------------------------------------------------qlog - VERITAS QuickLog device driver
AVAILABILITY VRTSvxfs
DESCRIPTION : The VERITAS QuickLog device driver is a performance enhance- ment feature for the
VERITAS File System (VxFS). QuickLog improves file system performance by moving all logging of file
system data and metadata to a separate raw disk or VxVM volume. This saves disk access time for log
writes because it eliminates seek time from the logging area to the file system area on a single volume or
disk. There is no disk seek time involved in the log writes on the QuickLog device, because all log writes on
the Quick-Log device are sequential.
Veritas Commands
Page 90 of 93
A QuickLog device is a device file to which you can attach up to four QuickLog Volumes. The volumes
provide the disk space for the file systems being logged to that device. The QuickLog devices are named :
o /dev/qlog/admin
o /dev/qlog/vxlog1-31
o /dev/qlog/cvxlog1-32
The admin device is for QuickLog internal use. The 31 /dev/qlog/vxlog1-31 devices are for logging local file
systems. The 32 /dev/qlog/cvxlog1-32 devices are for logging clustered file systems.
For QuickLog to log VxFS file system data and metadata (referred to as enabling QuickLog for a file
system), all VxFS log writes are redirected from the VxFS intent log to a QuickLog device.
Another key aspect of QuickLog is crash recovery. During a system start up, the QuickLog startup script,
/etc/rcS.d/S88qlog-startup, searches the QuickLog configura- tion file (see qlog_config(4)). For each
QuickLog device in this file that is in the attached state, the script tries to recover the log data and metadata
that were not committed to the VxFS file system before the crash or reboot (see qlogck(1M)). If this data is
successfully recovered, VxFS does not need to perform a full consistency check when running fsck. If an
error occurs on one of the VxFS file systems, only that file system with the error has a full consistency
check run. The configuration information for cluster QuickLog devices is maintained internally, not in the
QuickLog configuration file (/etc/qlog/config), and is consistent across the cluster.
If an error occurs on one of the QuickLog devices or Quick-Log volumes, the QuickLog device is removed
and a full consistency check is performed on the VxFS file systems that were enabled on this device.
Finally, all recovered Quick-Log volumes are reattached to QuickLog devices and are ready to begin
logging after the VxFS file systems are mounted.
To begin logging a VxFS file system by a QuickLog device, there are a few set up steps. First, the
VRTSvxfs package must be installed. This modifies the /etc/devlink.tab file and creates the 63 QuickLog
device nodes that can be used to attach QuickLog volumes to the QuickLog driver. Then choose the VxFS
file systems are to be enabled on these QuickLog devices. For each of these file systems, the tag qlog=
must be added to the mount option field of its entry in the /etc/vfstab file as in the following example:
# device device mount FS fsck mount mount
# to mount to fsck point type pass at boot options
/dev/vx/dsk/vol1 /dev/vx/rdsk/vol1 /vol1 vxfs 1 no qlog=
At this point, there are two methods of enabling QuickLog on a file system. One way is to remount the
VxFS file system with the modified entry in /etc/vfstab. This can be done by running mount -o remount. The
other method is to run qlogenable on a mounted file system's mount point. qlogenable incorporates mount
-o remount,qlog=. and issues the mount system call. Similarly, to disable logging by QuickLog without
unmounting the VxFS file system across system reboots, remove the qlog= option from the /etc/vfstab file
and run mount -o remount. You can also run the qlogdisable command.
The QuickLog configuration file is /etc/qlog/config.
QuickLog can use VxVM or raw disk partitions for all Quick-Log volumes. A cluster QuickLog device must
use a shared Cluster Volume Manager (CVM) volume for QuickLog volumes. VxFS can operate
independently from QuickLog.
Cluster File System Issues : This section describes the operation of QuickLog on cluster file systems.
Cluster QuickLog Devices There are up to 32 QuickLog device nodes in a cluster. All the systems in a
cluster can access a cluster QuickLog device, but a given QuickLog device can be accessed by only one
system at a time. The cluster node that has access to the QuickLog device is termed the master. The
cluster QuickLog device master mediates all log transactions for the cluster, and only the master can
change the cluster configuration information. Most QuickLog commands master the device automatically,
and no manual intervention is required. If a non-master node tries to initiate a configuration update, the
corresponding ioctl returns an EBUSY diagnostic.
The configuration information for all the cluster QuickLog devices is duplicated on all nodes. This
information is kept consistent by broadcasting any configuration updates. When a node joins a cluster, it
receives the configuration information from one of the existing member nodes. The con- figuration
information is used primarily during a cluster reconfiguration.
When a master node leaves the cluster, all the other nodes in the cluster mark the master node devices
"DIRTY." When a file system check (fsck) is run on a file system, the clus- ter QuickLog configuration
information is checked to determine if the file system was enabled to a cluster QuickLog device. If so, the
cluster QuickLog device is recovered before the fsck command does a log replay. If the primary file system
is QuickLog enabled and leaves the cluster, the secondary file system that assumes the primaryship can be
enabled to a different cluster QuickLog device. For each shared diskgroup in a cluster, it is advisable to
Veritas Commands
Page 91 of 93
configure either one cluster QuickLog device per cluster file system, or one per node, whichever number is
smaller.
Cluster QuickLog Device Life Cycle
CLEAN Initial state of the device. The device is clean and there are no VxFS file systems enabled by it.
DIRTY The master node of the cluster QuickLog device has left the cluster. In this state, no node can use
the device. Only a CLEAN or RECOVERED device can be used for logging.
RECOVERED The DIRTY cluster QuickLog device was recovered. The device is clean and there are no
VxFS file systems enabled by it.
UNDERRECOVERY The DIRTY cluster QuickLog device is being recovered.
ERRORS The QuickLog driver returns the standard error codes.
FILES
/dev/qlog/admin The QuickLog device driver special device node reserved solely for administrative
purposes.
/dev/qlog/vxlog [1-31] The QuickLog device driver special device nodes used for VxFS file system logging.
/dev/qlog/cvxlog [1-32] The QuickLog device driver special device nodes used for VxFS file system logging.
These are the cluster QuickLog devices.
/etc/qlog/config QuickLog configuration file.
/etc/rcS.d/S88qlog-startup QuickLog start up script.
/etc/vfstab Table of file system default parameters.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Veritas Commands
Page 92 of 93
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Veritas Commands
Page 93 of 93