VERITAS Volume Manager 3.1 Administrator's Guide

Volume Manager Operations
Common Volume Manager Commands
Chapter 3 129
started, the size and progress of the operation, and the state and rate of
progress of the operation. The administrator can change the state of a
task, giving coarse-grained control over the progressof the operation. For
those operations that support it, the rate of progress of the task can be
changed, giving more fine-grained control over the task.
Every task is given a unique task identifier. This is a numeric
identifier for the task that can be specified to the vxtask utility to
specifically identify a single task. For most utilities, the tag is specified
with the -t tag option.
Operations The vxtask utility supports the following operations:
list
List tasks running on the system in one-line summaries. The -l option
prints tasks in long format. The -h option prints tasks hierarchically,
with child tasks following the parent tasks. By default, all tasks running
on the system are printed. If a taskid argument is supplied, the output
is limited to those tasks whose taskid or task tag match taskid. The
remaining arguments are used to filter tasks and limit the tasks actually
listed.
monitor
The monitor operation causes information about a task or group of tasks
to be printed continuously as task information changes. This allows the
administrator to track progress on an ongoing basis. Specifying -l
causes a long listing to be printed. By default, short one-line listings are
printed. In addition to printing task information when a task state
changes, output is also generated when the task completes. When this
occurs, the state of the task is printed as EXITED (see “Output”).
pause
resume
abort
These three operations request that the specified task change its state.
The pause operation puts a running task in the paused state, causing it
to suspend operation. The resume operation causes a paused task to
continue operation. The abort operation causes the specified task to
cease operation. In most cases, the operations “back out” as if an I/O
error occurred, reversing to the extent possible what had been done so