volencap, volreconfig - Encapsulates disks, disk partitions,
or AdvFS domains on a single system or a cluster,
or the swap devices for one or more cluster members
/usr/sbin/volencap [-g diskgroup] [-p volprefix]
[privlen=nn] [nconfig=nn] { [diskname | partition_name |
domain_name]... }
/usr/sbin/volencap swap [privlen=nn] [nconfig=nn]
[[diskname] | [partition_name] ]...
/usr/sbin/volencap -k -a
/usr/sbin/volencap -k { [swap | diskname | partition_name
| domain_name]... }
/usr/sbin/volencap -s
/sbin/volreconfig
Specifies the disk group, by disk group ID or disk group
name, in which to add the encapsulated disk or domain. The
default is rootdg.
All system volumes on a standalone system (encapsulated
system partitions: /, /usr, /var, and swap)
and the swap devices for cluster members must be in
the rootdg disk group. The command fails if you
specify a different disk group for these devices.
Specifies a prefix for the LSM volume names generated
by the encapsulation process. This is useful
if the LSM volume names generated already exist.
The default volume name is derived from the disk
partition, except for the root (/) and primary swap
volumes on a standalone system, which are always
named rootvol and swapvol. Removes all pending
encapsulation requests. Removes any pending encapsulation
requests for the specified disk, partition,
or domain.
In a cluster, the swap operand removes pending
encapsulation requests for all swap devices in the
/etc/sysconfigtab file of the member the command is
executed on. Displays all pending encapsulation
requests.
Specifies the size of the LSM private region in blocks;
for example, privlen=1024. The default is 4096 blocks.
Specifies the number of log copies and copies of the configuration
database; for example, nconfig=0. In a cluster,
nconfig for swap is 0 by default. This is the recommended
value but you can set it differently.
Used in a cluster. Creates encapsulation scripts for all
devices listed under the swapdevice entry of a cluster
member's /etc/sysconfigtab file. To encapsulate the swap
devices for one or more other members at the same time,
specify additional operands naming the other members' swap
devices. See EXAMPLES for more information. Specifies
the disk to encapsulate. Specifies the partition to
encapsulate. Can be any disk partition that contains data
you want to encapsulate, including the swap partition for
a single system or a cluster member. Specifies the AdvFS
domain to encapsulate.
The /usr/sbin/volencap command encapsulates one or more
disks or disk partitions, including storage in an AdvFS
domain. On a single system, this includes the root file
system partitions /, /usr, and /var, and the primary swap
partition. In a cluster, this includes the swap devices
for one or more cluster members, but excludes the cluster
root file system domains (cluster_root, cluster_usr, and
cluster_var), member root domains, and member cnx partitions.
To place the cluster root file system domains under
LSM control, use the volmigrate command. See volmigrate(8) for more information. For an AdvFS
domain, you can specify the domain name as a shortcut
to encapsulate all the storage in that domain.
General and Single-System Behavior [Toc] [Back]
The volencap command encapsulates the storage in an AdvFS
domain, or any disk or partition that contains data,
including the partitions on the boot disk of a standalone
system (the root file system, primary swap, /usr, and /var
partitions), into LSM volumes. See the Logical Storage
Manager guide for more information on encapsulating these
partitions.
The volencap command generates LSM commands that take
effect when you execute the /sbin/volreconfig command to
perform the actual conversion of disk partitions to LSM
volumes.
If the disk, partition, or domain being encapsulated contains
a mounted file system or is otherwise open or in
use, the volreconfig command must reboot the system or
cluster member to complete the encapsulation process. If
you cannot reboot the system at the time of encapsulation,
either defer running the volreconfig command until you can
reboot the system, or unmount or close the disk partition,
then run the volreconfig command. If you specify an
entire disk, the volencap command creates a nopriv disk
and volume for each in-use partition on the disk.
LSM examines the disk label partition table for any
partition that is not marked unused in the fstype
field. If all partitions are marked as unused, the
command exits with a message indicating there was
nothing to encapsulate. If you specify an individual
partition for encapsulation, the volencap command
creates a nopriv disk and a volume for that
partition, regardless of the disk label partition
table entry. If you specify an AdvFS domain, the
volencap command creates a nopriv disk and volume
for each disk or partition in the domain.
See the Logical Storage Manager guide for more details.
Cluster Behavior [Toc] [Back]
In a cluster, the volencap command encapsulates any AdvFS
domain except the cluster root file system domains, member
root domains, and member cnx partitions.
The swap operand creates encapsulation scripts for all
devices listed under the swapdevice entry of a cluster
member's /etc/sysconfigtab file. For each device, the
script creates a nopriv disk and a volume for each in-use
partition on the disk. (The swap operand has no effect on
a single system.) The swap operand is a shortcut method of
encapsulating all the swap devices for one member at the
same time, without having to look up and then specify all
the swap devices.
You can run the volencap command on one member to encapsulate
the swap devices for that and any other member all at
once; you do not need to run volencap on each member individually.
However, you must run the /sbin/volreconfig
command on each member to complete the encapsulation of
that member's swap devices.
All system-related volumes on a standalone system (the
result of encapsulating the root file system, /usr, /var,
or swap) must belong to the rootdg disk group.
In a cluster, you cannot encapsulate the swap devices for
a member that is not running, the cluster root file system
domains, member root domains, or member cnx partitions.
The following examples apply to single systems. In each
case, the volreconfig command will request confirmation
prior to rebooting the system, if the disk, partition, or
domain being encapsulated is still mounted. The LSM command
scripts created by the volencap command will execute
as the system reboots. To encapsulate all disk partitions
on the boot disk (dsk0) to LSM volumes, enter: # volencap
dsk0 # volreconfig To encapsulate only the root file system
(dsk0a) and swap (dsk0b) partitions on the boot disk,
enter: # volencap dsk0a dsk0b # volreconfig To convert all
disk partitions in the AdvFS domain called dom1 to LSM
volumes, enter: # volencap dom1 # volreconfig To encapsulate
the specific partition dsk1g to an LSM volume, enter:
# volencap dsk1g # volreconfig
The following examples apply to clusters. In each
case, the volreconfig command will request confirmation
prior to rebooting the cluster member, if
the disk, partition, or domain being encapsulated
is still mounted. The LSM command scripts created
by the volencap command will execute as the member
reboots. To encapsulate all the swap devices for a
cluster member, enter: # volencap swap # volreconfig
The volencap command creates an encapsulation
script for each device in the swapdevice entry in
the /etc/sysconfigtab file. To encapsulate only
one swap device (dsk11b) for a cluster member,
enter: # volencap dsk11b # volreconfig The
following example is for a three-member cluster.
The commands shown encapsulate all the swap devices
for the member the command is executed on (moe),
plus swap devices dsk5b and dsk6b for the second
member (larry), and swap devices dsk13b and dsk14b
for the third member (curly). You must run volreconfig
on each member separately to complete the
encapsulation. moe> volencap swap dsk5b dsk6b
dsk13b dsk14b moe> volreconfig larry> volreconfig
curly> volreconfig The following example shows how
to encapsulate specific swap devices for several
cluster members at once. In this example, the swap
device for member moe, the member executing the
command, is dsk8b. The swap device for member larry
is dsk9b, and the swap device for member curly is
dsk10b. You must run volreconfig on each member
separately to complete the encapsulation. moe>
volencap dsk8b dsk9b dsk10b moe> volreconfig larry>
volreconfig curly> volreconfig
Commands: volmigrate(8)
Other: volintro(8), Logical Storage Manager, Cluster
Administration
volencap(8)
[ Back ] |
