unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OSF1-V5.1-alpha)
Page:
Section:
Apropos / Subsearch:
optional field



volencap(8)							  volencap(8)



NAME

  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

SYNOPSIS

  /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	 { [diskname | partition_name |	domain_name]...	}

  /usr/sbin/volencap -k	 -a

  /usr/sbin/volencap -s

  /sbin/volreconfig

OPTIONS

  -g diskgroup
      Puts the encapsulated disk or domain into	the disk group specified by
      disk group ID or disk group name.

      All system volumes (encapsulated system partitions: /, /usr, /var, and
      swap) must be in the rootdg disk group. You cannot put them in a dif-
      ferent disk group.

  -p volprefix
      Uses the specified volume	prefix for LSM volume names generated. This
      is useful	if the LSM volume names	generated already exist.

  -k diskname |	partition_name | domain_name ...
      Removes any pending encapsulation	requests for the specified disk, par-
      tition, or domain.

  -k -a
      Removes all pending encapsulation	requests.

  -s  Displays all pending encapsulation requests.

ATTRIBUTES

  privlen=nn
      Specifies	the size of the	LSM private region in bytes; for example,
      privlen=1024.

  nconfig=nn
      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 dif-
      ferently.




OPERANDS

  swap	  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.

  diskname
	  Specifies the	disk to	encapsulate.

  partition_name
	  Specifies the	partition to encapsulate. Can be any disk partition
	  that contains	data you want to encapsulate, including	the swap par-
	  tition for a single system or	a cluster member.

  domain_name
	  Specifies the	AdvFS domain to	encapsulate.

DESCRIPTION

  The /usr/sbin/volencap command encapsulates:

    +  One or more disks, disk partitions, or AdvFS domains on a single	sys-
       tem

    +  One or more AdvFS domains (except the cluster root domain and member
       root domains) on	a cluster

    +  The swap	devices	for one	or more	cluster	members

			       Note for	Clusters

       In a cluster, you must use the volmigrate command instead of the
       volencap	command	to place the cluster_root domain under LSM control.
       You can use either volmigrate or	volencap for any other domain,
       including cluster_usr and cluster_var.

       The volmigrate command creates an LSM volume on different disks than
       the domain currently uses, and therefore	does not require you to
       reboot the cluster. See volmigrate(8) for more information.

  Disk partitions that have data can be	placed under LSM control using the
  encapsulation	process. If you	have existing data in disk partitions, you
  can easily migrate to	the use	of LSM volumes instead of disk partitions.

    +  If you specify an individual partition for encapsulation, the volencap
       command creates a nopriv	disk and a volume for that partition.

    +  If you specify an entire	disk, the volencap command creates a nopriv
       disk and	volume for each	in-use partition on the	disk.

    +  If you specify an AdvFS domain, all disk	partitions in the domain are
       converted to LSM	volumes.

  In a cluster,	the volencap command encapsulates any AdvFS domain except the
  cluster root domain and member root domains. 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 dev-
  ices for that	and any	other member all at once; you do not need to run
  volencap on each member individually.

  On a single system, the volencap command encapsulates	any AdvFS domain, or
  any disk or partition	that contains data, including the partitions on	the
  boot disk (the root file system, primary swap, /usr, and /var	partitions),
  into LSM volumes.  See the Logical Storage Manager guide for more informa-
  tion on encapsulating	these partitions.

  The volencap command generates LSM commands that do not take effect until
  you execute the /sbin/volreconfig command to perform the actual conversion
  of disk partitions to	LSM volumes.  When encapsulating the swap devices for
  a cluster member, you	must run the /sbin/volreconfig command on each member
  to complete the encapsulation	of that	member's swap devices.

  If the disk partition	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 you encapsulate the disk partition, either defer running the	vol-
  reconfig command until you can reboot	the system, or unmount or close	the
  disk partition, then run the volreconfig command.

  See the Logical Storage Manager guide	for more details.

RESTRICTIONS

  All system-related volumes (the result of encapsulating the root file	sys-
  tem, /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	domain,	or member root domains.

EXAMPLES

   1.  The following examples apply to single systems.

	 +  To encapsulate all disk partitions on the boot disk	(dsk0) to LSM
	    volumes, enter:


		 # volencap dsk0
		 # volreconfig

	    The	volreconfig command will request confirmation prior to
	    rebooting the system. The LSM command scripts created by the
	    volencap command will execute as the system	reboots.

	 +  To encapsulate only	the root file system (dsk0a) and swap (dsk0b)
	    partitions on the boot disk, enter:


		 # volencap dsk0a dsk0b
		 # volreconfig

	    The	volreconfig command will request confirmation prior to
	    rebooting the system. The LSM command scripts created by the
	    volencap command will execute as the system	reboots.

	 +  To convert all disk	partitions in the AdvFS	domain called dom1 to
	    LSM	volumes, enter:


		 # volencap dom1
		 # volreconfig

	    The	volreconfig command will determine if the domain is active,
	    and	if so, request confirmation prior to rebooting the system.
	    The	LSM command scripts created by the volencap command will exe-
	    cute as the	system reboots.	If the AdvFS filesets in domain	dom1
	    are	not mounted, then volreconfig can complete without rebooting
	    the	system.

	 +  To encapsulate the specific	partition dsk1g	to an LSM volume,
	    enter:


		 # volencap dsk1g
		 # volreconfig

	    The	volreconfig command will determine if the partition is open,
	    and	if so, request confirmation prior to rebooting the system.
	    The	LSM command scripts created by the volencap command will be
	    executed as	the system reboots.

   2.  The following examples apply to clusters.

	 +  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.

	    The	volreconfig command will determine if the partition is open,
	    and	if so, request confirmation prior to rebooting the member.
	    The	LSM command scripts created by the volencap command will be
	    executed as	the member reboots.

	 +  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	volreconfig command will determine if the partition is open,
	    and	if so, request confirmation prior to rebooting the member.
	    The	LSM command scripts created by the volencap command will be
	    executed as	the member reboots.

	 +  The	following example shows	how to encapsulate specific swap dev-
	    ices 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

	 +  To encapsulate only	one swap device	for a cluster member (in this
	    example, dsk11b), enter:


		 # volencap dsk11b
		 # volreconfig



SEE ALSO

  Commands: volintro(8), volmigrate(8)

  Logical Storage Manager, Cluster Administration