admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
NAME
admpdisk - administer physical disks
SYNOPSIS
admpdisk -o list [ -qQavprLw ] [ devicespec ... ]
admpdisk -o copy [ -q ] [ -Q ] -s source -d destination
admpdisk -o listmappedblocks [ -q ] [ -Q ] devicespec ...
admpdisk -o mapblock [ -q ] [ -Q ] { -B blocknolist } ...
devicespec
admpdisk -o unmapblock [ -q ] [ -Q ] { -B blocknolist } ...
devicespec
admpdisk -o verify [ -w [ -f ] ] [ -q ] [ -Q ] -B blocknolist ...
devicespec ...
admpdisk -o initialize [ -q ] [ -Q ] [ -V ] [ -m mapsize ]
[ -b bootstrapfile ] [ -l labelfile ] devicespec ...
admpdisk -o install [ -q ] [ -Q ] [ -m mapsize ]
[ -b bootstrapfile ] [ -l labelfile ] devicespec ...
admpdisk -o convert [ -q ] [ -Q ] [ -r ] [ -f | -n ] devicespec ...
admpdisk -o getdefaults [ -q ] [ -Q ] devicespec
admpdisk -o setdefaults [ -q ] [ -Q ] [ -r rootvirtualdisk ]
[ -s swapvirtualdisk ] devicespec
admpdisk -o register [ -q ] [ -Q ] [ -f ] [ -c | -C ] devicespec ...
admpdisk -o deregister [ -q ] [ -Q ] devicespec ...
admpdisk -o configure [ -q ] [ -Q ] devicespec ...
admpdisk -o deconfigure [ -q ] [ -Q ] devicespec ...
admpdisk -o repairvdit [ -q ] [ -Q ] devicespec
DESCRIPTION
The admpdisk command displays information about, and manages,
physical disks. For the purposes of this document, a physical disk
is anything for which an entry appears in /dev/pdsk. This includes
traditional single-spindle magnetic disks and CD-ROMs. In addition,
a single unit in a Highly Available Disk-Array is considered here to
be a single physical disk, even if it is made up of multiple
removable disk drives; see the documentation for your disk array
hardware for a description of units.
Physical disks are rarely used directly, although each physical disk
does have an entry in /dev/pdsk and /dev/rpdsk through which it can
Licensed material--property of copyright holder(s) 1
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
be accessed. However, access through these special files does not
benefit from software bad block mapping (see below). Normally, the
space on a physical disk is apportioned to one or more virtual disks
(see admvdisk(1M)), and these virtual disks are accessed directly, or
mounted as file systems. Virtual disk partitions can have bad block
mapping described below enabled or disabled, as desired.
Normally, each physical disk has tables that contain information
necessary for maintaining the layout of virtual disks, bad block
maps, the system bootstrap program, and so on.
In addition, each disk usually has a bad block map partition, whose
blocks are used as substitutes for blocks on the disk that have media
defects. Physical disk devices that provide an exceptional level of
reliability, such as RAID-5 disk arrays, generally do not need
software bad block mapping.
Physical Disk Formats
Physical disks that have been initialized under DG/UX version
5.4R3.00 or later are said to be in virtual disk format, that is,
they can contain virtual disks. Physical disks that were initialized
under versions of DG/UX prior to 5.4R3.00, and have not been
converted, as well as CD-ROMs designed to be compatible with such
older versions of DG/UX, contain a different set of system
information. Such physical disks (including CD-ROMs) contain logical
(as opposed to virtual) disks, and are said to be initialized for
logical disks, or in logical disk format. Writable physical disks in
logical disk format can be converted to virtual disk format and,
under certain circumstances, converted back (see the convert
operation). Read-only physical disks (such as CD-ROMs) cannot be
converted, but can be registered in compatibility mode (see below).
Physical disks and CD-ROMs in logical disk format can be registered
in compatibility mode. When so registered, temporary virtual disks
are created that mimic the logical disks defined on the physical
disks, so that the data blocks associated with the logical disks may
be mounted, read and written. However, the virtual disks may not be
permanently deleted, expanded, shrunk, or otherwise modified. They
also should not, in general, be incorporated as children into any
other virtual disk, although the system may not prevent you from
doing so. Note that when registering in compatibility mode, no
mirror virtual disks are created to mimic any mirrors defined on the
physical disk, nor cache virtual disks created to mimic any caches
defined on the physical disk.
Failover Physical Disks
Under certain circumstances a physical disk can be shared between
AViiON systems. This can happen if two AViiON systems are connected
to a single bus (e.g. SCSI bus), or if the physical disk subsystem
has multiple ports for host connections. When such a disk is opened
(or registered) by one system, it is said to be "owned" by that
system. Once so owned, the physical disk can be configured by
another system, but that's all: the other system can't initialize,
read, write, or perform an un-forced register operation on it. If
Licensed material--property of copyright holder(s) 2
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
the first system closes all its descriptors to the physical disk
(which generally includes deregistering the disk), the system ceases
to own the physical disk, and the physical disk becomes available for
access by another system. In addition, a system can gain access to a
physical disk that is owned by another system by using admpdisk -o
register -f (the force option), effectively stealing the physical
disk from the other system. Normally this would be done only if the
other system had crashed without relinquishing ownership of the
physical disk; see admfailoverdisk(1M).
In certain high-performance configurations, a single AViiON system
may have multiple I/O adapters, connected to multiple communication
buses, which are connected to multiple ports on a single physical
disk subsystem with multiple spindles. Thus an AViiON system can
"share" a "physical disk" (that is a portion of the physical disk
subsystem) with itself.
Physical Disk States
Physical disks can be categorized as follows:
State Description
------------------------------------------------------------------
Not Does not appear on listings of physical disks.
configured. Does not have an entry in /dev/pdsk. Cannot be
initialized, registered, read or written. All
that can be done to such a disk is to configure
it.
Configured, Appears in listings of physical disks, has an
but not owned. entry in /dev/pdsk. Cannot be initialized,
registered (except with the -f option), read or
written. Cannot determine if it is initialized
or not.
Configured and Appears in listings of physical disks, has an
owned, but not entry in /dev/pdsk. Can be read or written
initialized. directly, verified, or initialized. Usable only
by special-purpose applications that manage
their own disk resources. Has no tables of
virtual disks or logical disks, no bad-block
mapping. Cannot be registered.
Configured and Has system areas, but they cannot be used
initialized in (logical disks cannot be used or manipulated).
logical disk Can be re-initialized, read or written directly,
format, but verified, converted to virtual disk format, or
not registered in compatibility mode.
registered.
Licensed material--property of copyright holder(s) 3
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
Configured, Has partitions, but they cannot be used (virtual
initialized in disks cannot be used or manipulated). Can be
logical disk re-initialized, read or written directly,
format, verified, possibly converted to back to logical
converted to disk format, or registered.
virtual disk
format, but
not
registered.
Configured and Has partitions, but they cannot be used (virtual
initialized in disks cannot be used or manipulated). Can be
virtual disk re-initialized, read or written directly,
format, but verified, or registered.
not
registered.
Configured, Normal operating condition. Virtual disks can
initialized, be manipulated and used. Can be read, but
and cannot be written to directly (only virtual
registered. disks can be written to). Can have a new
bootstrap or bad-block mapping facilities
installed. Cannot be verified.
Normally, physical disks are configured when the kernel is booted, so
there is no need to configure them dynamically. In addition, when
the kernel is booted, those physical disks that are in virtual disk
format are automatically registered if possible. Disks that are in
logical disk format can be registered in compatibility mode, but only
by an invocation of admpdisk; the kernel will not do it
spontaneously.
Default Virtual Disks
On each physical disk that is in virtual disk format, a default root
virtual disk and a default swap virtual disk may be specified.
If a default root is specified, then when the system is booted,
unless the default is overridden, the /dgux kernel image will be
retrieved from that virtual disk. The bootstrap requires that the
virtual disk from which it obtains the /dgux image be either a
partition virtual disk or an aggregation virtual disk whose children
are all partition virtual disks on the same physical disk. However,
admpdisk will not prevent you from setting the default root to a
virtual disk that does not satisfy this requirement. In addition,
when the kernel is booted, it determines if the physical disk from
whence it was booted contains a default root virtual disk
specification. If it does, then that virtual disk is used as the
root file system by the kernel.
Similarly, when the kernel is booted, it determines if the physical
disk from whence it was booted contains a default swap virtual disk
specification. If it does, then that virtual disk is used as the
swap device. The swap virtual disk may be of any type, and be
located on any physical disk that will be configured and registered
Licensed material--property of copyright holder(s) 4
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
when the kernel is booted. However, if you want to use space on
multiple physical disks for swapping, it is generally better to
specify the areas separately, rather than collecting them together
with an aggregation virtual disk. See admswap(1M).
Confirmation
By default, admpdisk asks for confirmation before performing any
potentially destructive operation. In some contexts, such as
invoking admpdisk from an idl(4) script, or from a shell script being
run in the background, such requests for confirmation may be
inappropriate. Requests for confirmation can be broken down into two
categories: "standard" ones that are predictable, such as with
creating a virtual disk table on a physical disk, and "exceptional"
ones that may or may not be issued, depending upon factors that are
determined dynamically. An example of the latter is when attempting
to install a bootstrap on a physical disk that has no label. To
manage this issue, the following options are provided:
-q Quiet. Standard confirmation requests are suppressed.
Admpdisk behaves as if the request were generated, and the
user gave confirmation. Exceptional confirmation requests
are still generated. This option is appropriate when
admpdisk invoked from an idl(4) script, or by a user who is
confident that the requested operation is correct.
-Q Very quiet. Absolutely all requests for confirmation are
suppressed. Admpdisk behaves as if the request were
generated, and the user gave confirmation. This option is
appropriate when admpdisk is invoked from a script that
will be run in the background, so there is no way for a
user to interact with it.
Both the -q and -Q options are legal with all operations, although
they will not have any effect on those operations that don't generate
requests for confirmation. This is to allow one to write shell and
idl(4) scripts that will continue to work correctly even if admpdisk
is changed in the future to have more confirmation queries.
Operations
The -o option is used to specify which operation to perform.
list Displays information about one or more disks. If no
disks are specified, all configured disks, including
those that are not registered, are listed. By
default, for each registered disk, the list output
includes:
the common device specification of the physical
disk,
the state of the disk, as follows:
avail Available, the normal operating
condition.
Licensed material--property of copyright holder(s) 5
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
not ready Empty diskette or CD-ROM drive.
not owned Drive is on a SCSI bus that is shared
with another AViiON, and the other
AViiON has control of this drive.
not avail Otherwise unavailable.
the disk's registration status:
n Not registered.
y Registered.
c Registered in compatibility mode.
its size in blocks, and
the number of free blocks on the disk.
If you do not have the necessary permissions, some of
this information cannot be obtained, and the state
will always be listed as not avail, and the format,
total blocks, and free blocks are listed as n/a.
If the -p (partitions) option is specified, then in
addition to the one line described above, a listing of
the partitions on the disk is produced. This list of
partitions includes:
the name of the partition virtual disk, including
the ID number if necessary to disambiguate it;
or, if it has no name, a description of the role
that the partition plays in an ancestor virtual
disk.
the size (in blocks) of the partition, and
the block address of the partition.
Unless the -a (list all) option is specified,
partitions whose names start with '.' are clumped
together and listed as a single entry titled
"<Various System Partitions>".
For disks that are not registered, the output consists
of the disk's name, an indication that the disk is not
registered, and the disk's size.
The number of free blocks is shown as n/a for disks:
that are not writable, or
for which it is not possible to determine if
whether or not they are writable, or
that are not partitioned but are in use.
When such disks are listed with the -p option, any
free space is tagged appropriately; for example
Licensed material--property of copyright holder(s) 6
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
<unwritable free space> or <maybe unwritable free
space>.
copy Copies the contents of physical disk source to
physical disk destination. The source disk need not
be registered. The destination physical disk must not
be registered. Since this operation could cause data
loss on the destination disk, the user is asked to
confirm the operation before it is performed.
If the source disk is in virtual disk format, then the
system data is copied to the destination disk and all
of the partitions are copied. If the source device is
any other format or raw data, it is copied directly to
the destination device. In the latter case no mapping
of bad blocks is done when reading the source.
The size of the destination must be greater than or
equal to the size of the source.
listmappedblocks
The block numbers of those blocks that have been the
object of a mapblock operation (or an equivalent
mapping operation performed by the kernel) are listed.
The status field for each block will be one of the
following values:
mapped The bad block has been mapped to a new
block. All I/O is being redirected to this
new block.
unmapped The kernel has detected an error upon
attempting to read this block. Although the
original block has a remap block associated
with it, the contents of the remap block are
undetermined. Until a write is performed to
the new block, reads directed to the
original block will fail.
force A user has performed a map-block operation
upon this block. Although the original
block has a remap block associated with it,
the contents of the remap block are
undetermined. Until a write is performed to
the new block, reads directed to the
original block will fail.
pseudo An entry with this status corresponds to a
block that does not necessarily need
remapping but whose contents are
undetermined. Reads to pseudo bad blocks
will fail. The first write to a pseudo bad
block sets its contents and deletes the
corresponding remap table entry.
Licensed material--property of copyright holder(s) 7
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
bad An entry with this status represents a block
in the bad-block map area itself that is
unusable.
mapblock The block(s) specified with the -B option are marked
as being unusable, and alternative blocks on the
physical disk are substituted for them (i.e. they are
put into the force state). Nothing is done to recover
data from the defective block(s). Blocks that are
part of any of the partitions that are created by the
initialize or install operations cannot be mapped.
These partitions include the label (block 0), the
Virtual Disk Information Table, the bootstrap, and the
bad block map area itself.
unmapblock The block(s) specified with the -B option are marked
as being usable, and the substitute block(s) that had
been allocated to them are released.
verify Performs surface analysis on the disk. This is
generally not required for AViiON disk drives. You
may specify that you want a writing test with -w, or a
read-only test (by not using -w).
You must manually specify which blocks to verify with
the -B option. The disk must not be registered.
Without the -w option, the specified blocks are read,
and any hard read errors are reported. Soft read
errors are reported only to the system console. With
the -w option, each block is written and read.
Verifying in manual mode will not result in any blocks
being automatically tagged for software bad-block
remapping. If you want them to be mapped, you must
use the map operation explicitly.
If you use the -w option, then by default, three
passes are made over the appropriate block(s) of the
disk, writing and reading three different bit
patterns. You may use the -f (fast) option to make
admpdisk use only one bit pattern.
initialize and install
The initialize and install operations are closely
related. The initialize operation can be used to
create virtual disk layout tables (-V), install a
label (-l), install a bootstrap program (first
creating a partition to hold it if necessary) (-b),
and establish software bad-block mapping ability on
the physical disk (including creating the necessary
partitions) (-m). The first of these, creating
virtual disk layout tables, effectively destroys the
contents of the physical disk. The install operation
can do all the functions listed above except creating
the virtual disk layout tables. This provides a safer
Licensed material--property of copyright holder(s) 8
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
way to update the other items (disk label, bootstrap
program, and software bad block mapping) without
running any risk of accidentally wiping out the
virtual disk layout tables. If none of -V, -l, -b or
-m are specified, nothing is done.
To create new virtual disk layout tables, (-o
initialize -V), the disk must not be registered. The
disk may be automatically registered during either of
these operations.
There is no way to initialize a disk into logical disk
format.
convert Converts the specified physical disk(s) listed from
logical disk format to virtual disk format (or vice
versa, with the -r option). For each logical disk, a
corresponding virtual disk (either a partition or an
aggregation of partitions) is created. For each
logical disk-style software mirror, a mirror virtual
disk is created. Caches that used logical disks
cannot be converted. They must be deleted before the
physical disk is converted.
In situations where a logical disk or software mirror
spans multiple physical disks, then all the physical
disks should be converted at once, so that the
relationship between the pieces of the logical disk,
or between the images of the mirror, can be
maintained.
By default, if the set of physical disks being
converted includes some but not all pieces of a
logical disk (or an aggregation but not all its
children during a reverse conversion), an error
message is printed and the conversion is terminated
before the physical disks are modified. If a mirror
is found to have fewer than three images, a warning
messages is printed, but the conversion proceeds.
This behavior can be modified with the -f and -n
options.
getdefaults The default root and swap virtual disk specifications
stored on the specified physical disk are listed.
setdefaults The specified rootvirtualdisk and/or
swapvirtualdisk are recorded on the physical disk.
At least one of the virtual disks must be specified.
To make the physical disk have no default disk of
either type, specify a virtual disk name of "".
register Registers the specified disks(s). If no disks are
specified on the command line, all unregistered disks
that can be registered are registered. If the -C
Licensed material--property of copyright holder(s) 9
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
option is used, then disks will be registered in
compatibility mode, if necessary. During system boot,
physical disks in virtual disk format are normally
automatically registered.
deregister Deregisters the specified disks(s). At least one disk
name must be specified on the command line. A
physical disk cannot be deregistered if it contains a
piece of a virtual disk that is open (open by an
application, mounted as a file system, being swapped
upon, or is the child of any virtual disk that is any
of these things).
configure Configures the specified physical disk(s) in the
kernel. Normally, disks are configured statically
when the kernel is built; such disks do not need to be
dynamically configured. In order for a disk to be
configured, the kernel must already contain the
driver(s) appropriate for that disk. Generally this
means that one can dynamically configure a device only
if there is already another device of the same type
configured.
The admdevice(1M) command is preferred over
admpdisk(1M) for configuring and deconfiguring. New
scripts should use admdevice. The configure and
deconfigure operations are offered here for historical
compatibility.
deconfigure The specified physical disk(s) are deconfigured. To
be deconfigured, a disk must not be registered.
repairvdit On the specified physical disk, the damaged copy of
the Virtual Disk Information Table is restored from
the undamaged copy. If possible, the physical disk is
deregistered and reregistered, to allow full use of
the disk. If the deregistration/reregistration fails,
the disk will remain in a mode wherein modifications
to virtual disks (creation, removal, etc.) are
forbidden.
Options
The following options can be used with any operation, but currently
have an effect on only the list, listmappedblocks, copy, verify,
and initialize -V operations:
-q Quiet. With the list and listmappedblocks
operations, no headers are printed, and fields are
separated by colons, not white space. With the copy,
verify and initialize -V operations, the user is not
asked to confirm before the operation is performed.
-Q Very quiet. All requests for confirmation are
suppressed, including all those suppressed by the -q
Licensed material--property of copyright holder(s) 10
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
option. In addition, with initialize -b and install
-b, if there is no label on the physical disk, a SCSI
label will be installed before installing the
bootstrap, without asking the user to confirm.
The following options can be used with the list operation:
-v Verbose. This is the default output style.
-p Partitions. The partitions on the disk are listed as
described above.
-a All. System partitions (partitions whose names starts
with '.') are listed individually by name, rather than
being shown as a single "<Various System Partitions>"
entry. Specifying -a is the same as specifying -pa.
-r Registered. Only registered disks are listed; disks
registered in compatibility mode are not included. If
an unregistered disk is specified on the command line
along with this option, it is treated as an error.
-w Writable. Only writable disks are listed. If an
unwritable disk is specified on the command line along
with this option, it is treated as an error. The
combination -rw results in listing only those disks
that are both registered and writable. If a disk that
is either unregistered or unwritable is specified on
the command line along with this combination of
options, it is treated as an error.
-L Labels. Each disk's label is displayed along with any
other information.
-Q Very quiet. Lists only the names of the physical
disks, one per line, with no header.
The following options must be used with the copy operation:
-s source Source physical disk.
-d destination Destination physical disk.
The following option must be used with the mapblock, unmapblock,
and verify operations:
-B blocknolist
Block numbers. Multiple block numbers may be
specified by using multiple -B options, or by using
one -B option with a comma-separated list of block
numbers. Ranges of block numbers can be expressed
using dashes, as in -B 2500-2510. With the verify
operation, this could cause data loss, so the user is
asked to confirm the operation before it is performed.
Licensed material--property of copyright holder(s) 11
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
Numbers are decimal.
The following options can be used with the verify operation:
-f Fast. Only one pass is performed, using one bit
pattern, instead of three.
-w Write. In addition to reading the block(s) being
verified, test pattern(s) are written to the disk.
This destroys any data on the block(s).
The following option can be used with the initialize operation:
-V Initialize virtual disk tables. The tables on the
physical disk used to allocate space on the disk to
various virtual disks are created anew (whether they
were there before or not). This effectively destroys
any existing virtual disks that reside on the physical
disk(s) (but the actual data blocks of the virtual
disks may not be erased). If -b is not specified, the
disk will be left without a bootstrap program; if -m
is not specified, the disk will be left without a bad
block map area. Since this option could cause the
loss of virtual disks, the user is asked to confirm
the operation before it is performed.
The following options can be used with the initialize and install
operations:
-m mapsize Mapsize specifies the number of blocks to set aside
for software mapping of bad blocks. If the -V option
is specified, but the -m option is not, no bad block
mapping will be performed on this physical disk. If a
size of 0 is specified, an appropriate default size
will be chosen.
-b bootstrapfile
Establishes a bootstrap program partition on the disk
(if there isn't one already), and installs the
contents of the specified file as the bootstrap. In
order for a bootstrap program to be usable, there must
be a label on the physical disk. By default, if the
physical disk has no label and the -l option has not
been specified, admpdisk will ask the user if a SCSI
label should be installed. If the user agrees, the
label and bootstrap are installed; if the user
declines, neither is installed. This confirmation
request can be suppressed with the -Q option. Note
that if the disk is not a SCSI disk, the -l option
should be used to specify the correct label.
-l labelfile The disk label is rewritten based on the contents of
the labelfile. The format of label files is
documented in dgpd(3c).
Licensed material--property of copyright holder(s) 12
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
The following options can be used with the convert operation:
-r Reverse. The conversion is done in the reverse
direction, i.e. from virtual disk format to logical
disk format. The hierarchy of virtual disks on the
physical disk(s) must be compatible with what can be
achieved using logical disks. This includes the
physical virtual disk on each physical disk, a layer
of partition virtual disks above that, and a layer of
aggregation virtual disks above that.
-r Forceful. The conversion proceeds even if there are
missing logical disk pieces (or missing children of an
aggregation in a reverse conversion).
0f1 No-write. The physical disks are not actually
converted. This is useful for determining if the set
of physical disks includes any incomplete logical
disks (or aggregations).
The following options can be used with the register operation:
-f Force. Used with physical disks that are owned by
another AViiON system; -f wrests ownership of the
physical disk away from the other system. This is
normally used only when the other AViiON system has
crashed, and is normally used only by the failover
software. See admfailoverdisk(1M).
-c Compatibility mode. Allows registration of physical
disks that are formatted for logical disks, as
described above. If a logical disk spans more than
one physical disk, then all the physical disks
involved must be registered simultaneously, with the
-c (or -C) option. Any logical disk that is not fully
present (all pieces accounted for) on the physical
disks being registered at one time will not be
represented by a virtual disk.
-C Optional compatibility mode. Each physical disk to be
registered is registered normally (not in
compatibility mode) if possible (i.e. if it is
formatted for virtual disks), otherwise it is
registered in compatibility mode. If two physical
disks are registered with the -C option, and one is
registered in compatibility mode and the other not,
the disks are considered to have been registered
separately, for the purposes of joining up pieces of
logical disk that span the two physical disks.
One or both of the following options must be used with the
setdefaults operation:
-r Default root virtual disk. To arrange to have no
Licensed material--property of copyright holder(s) 13
admpdisk(1M) DG/UX 5.4R3.00 admpdisk(1M)
default root virtual disk, specify -r "".
-s Default swap virtual disk. To arrange to have no
default swap virtual disk, specify -s "".
FILES
/etc/pdsk/* block special physical disk devices
/etc/rpdsk/* character special physical disk devices
DIAGNOSTICS
Exit Codes
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions.
3 There was an error in the command line.
SEE ALSO
admvdisk(1M), admdevice(1M), gridman(1M).
Licensed material--property of copyright holder(s) 14