DOCUMENT

        Adding A Disk To A Volume Group In A ServiceGuard Package 

1a.  Select an unused disk to add to the volume group (VG).

     NOTE:  At this time, SAM is unable to determine if a deactivated
     disk is in use on another system.  It can mistakenly allow you to
     allocate the disk again on a system that doesn't yet claim the disk.
     BE AWARE BEFORE YOU SHARE.

     Use SAM:
       Disks & File Systems -> Volume Groups ->  Select a Disk

                                  OR

1b.  LVM will allow you to extend a physical volume into a VG whether or
     not the VG is active.  On the node where it is active, use this syntax:

       Example:
       # vgextend vg07 /dev/dsk/c4t4d0

2.  On the same node, add logical volumes to the volume group as
    needed, or extend current logical volumes
    NOTE - Online JFS is required to extend logical volumes that
    are active.

    Example:
       # lvcreate -L 600 vg07    (creates a 600MB logical volume)
       # newfs -F vxfs /dev/vg07/rlvol1 (if not a raw database lvol)

    Mount the new lvol:

       # mount /dev/vg07/lvol1 /data7

    Load the new lvol with data as needed.  Umount it when complete.

3.  On the same node, create a new map file:

    Example:

       # vgexport -pvs -m /etc/lvmconf/vg_shared.map /dev/vg_shared

    NOTE:  the -s option adds the unique VGID to the top of the map
    file.  It will be used by the vgimport process to identify disks
    labeled with this VGID, to eliminate the need to specify the actual
    physical disks to import.  The -s option is NOT available with HP-UX
    10.01.  In that case, you must explicitly list every disk that belongs
    to the volume group during the vgimport.

4.  Copy the map file to the other adoptive node(s)

    Example:
       # rcp /etc/lvmconf/vg_shared.map nodeB:/etc/lvmconf

5.  On the adoptive node that doesn't have the VG activated, record the
    group minor number for the VG to which you added the disk.

 # ll /dev/vg*/group
 crw-r-----   1 root      root     64 0x000000 Sep 19  1996 /dev/vg00/group
 crw-rw-rw-   1 root      sys      64 0x020000 Jun  4 12:39 /dev/vg07/group
                                         ^
                              Record eg:0x02 <--

6.  On the adoptive nodes where the VG is not active, vgexport the volume
    group:

    Example:

       # vgexport /dev/vg07

    It will remove /dev/vg07 and all special files in it.

7.  Recreate the directory and group file:

    Example:                       Note: from step 5
                                              |
       # mkdir /dev/vg07               |
       # mknod /dev/vg07/group c 64 0x020000

8.  Reimport the VG using the new map file.

    Example:

       # vgimport -vs -m /etc/lvmconf/vg07.map /dev/vg07

    This command will cause LVM to query ALL PV's (Physical disks) on the
    system, inspecting them for a VGID that matches the one listed in the
    top of the map file.  It adds all matching disks into the /etc/lvmtab.
    It also adds new lvols.  If you want your pvlinks listed in a
    particular order, do NOT use the -s option, but individually specify
    the sequence of disks.

9.  On the original node, update the package control script with the
    additional lvols and mountpoints and distribute the control script to
    all adoptive nodes.

    Example listing of lines added in the control script.  Note the
    sequentially increasing array index numbers :

       LV[0]="/dev/vg06/lvol1"; FS[0]="/vg06/lvol1_mount"
       LV[1]="/dev/vg06/lvol2"; FS[1]="/vg06/lvol2_mount"
       LV[2]="/dev/vg07/lvol1"; FS[2]="/vg07/lvol4_mount"
       LV[3]="/dev/vg07/lvol2"; FS[3]="/vg07/lvol5_mount"
       LV[4]="/dev/vg07/lvol3"; FS[4]="/vg07/lvol6_mount"
       LV[5]="/dev/vg07/lvol4"; FS[5]="/vg07/lvol7_mount"
           \                        \
     Note the index numbers don't start at zero since this particular disk
     added more mount points in the VG

10.  Test the new logical volume actuation on all adoptive nodes by
     restarting the package on all nodes.

                           ### END ###

Other "how-to" ServiceGuard documents can be founding using the string
uxsg*