7.10 VxVM Rootability Rootability is the mechanism whereby we host root , boot , swap , and dump volumes under the control of VxVM. Until recently, this has been the sole preserve of IPF machines. Since Application Release 0902 of HP-UX 11i, PA-RISC machines can also decide to enjoy the benefits of VxVM rootability . We can either perform a cold install to achieve VxVM rootability, or we can use a utility ( vxcp_lvmroot ) that will duplicate an existing LVM root volume group and create a root disk group containing all the same software and volume sizes as in vg00 . First, we need to check our current release of HP-UX 11i:
root @uksd3 # swlist -l bundle HPUXBaseAux # Initializing... # Contacting target "uksd3"... # # Target: uksd3:/ # HPUXBaseAux B.11.11. 0303 HP-UX Base OS Auxiliary root @uksd3 #
As you can see, our Application Release version is greater than the minimum required. We should be able to make a rootable VxVM disk group. Next, we need to establish how many disks are currently in vg00 . We need to supply the same number of disks in order to perform the copy:
root @uksd3 # lvlnboot -v vg00 Boot Definitions for Volume Group /dev/vg00: Physical Volumes belonging in Root Volume Group: /dev/dsk/c0t0d0 (2/0/1/0/0.0.0) -- Boot Disk /dev/dsk/c0t1d0 (2/0/1/0/0.1.0) Boot: lvol1 on: /dev/dsk/c0t0d0 Root: lvol3 on: /dev/dsk/c0t0d0 Swap: lvol2 on: /dev/dsk/c0t0d0 Dump: lvol2 on: /dev/dsk/c0t0d0, 0 root @uksd3 #
The disks that we supply to the vxcp_lvmroot command must not be LVM disks or have any recognizable data on them; otherwise , the process will fail. My VxVM boot disk will be c3t8d0 , and my additional disk (the “p option to specify a pool of additional disks) in the root disk group will be c3t10d0 . We could also specify the “m <disk> option in order to set up a root mirror at this time. We are now ready to start the copy:
root @uksd3 # /etc/vx/bin/vxcp_lvmroot -v -p c3t10d0 c3t8d0 vxcp_lvmroot 18:05: Gathering information on LVM root volume group vg00 vxcp_lvmroot 18:05: Checking specified disk(s) for usability vxcp_lvmroot 18:05: Starting up VxVM FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured vxcp_lvmroot 18:05: Preparing disk c3t8d0 as a VxVM root disk vxcp_lvmroot 18:05: Adding disk c3t8d0 to rootdg as DM rootdisk01 FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured vxcp_lvmroot 18:05: Preparing disk c3t10d0 as a VxVM disk vxcp_lvmroot 18:05: Adding disk c3t10d0 to rootdg as DM rootaux01 vxcp_lvmroot 18:05: Copying /dev/vg00/lvol1 (hfs) to /dev/vx/dsk/rootdg/standvol vxcp_lvmroot 18:06: Cloning /dev/vg00/lvol2 (swap) to /dev/vx/dsk/rootdg/swapvol vxcp_lvmroot 18:06: Copying /dev/vg00/lvol3 (vxfs) to /dev/vx/dsk/rootdg/rootvol vxcp_lvmroot 18:07: Copying /dev/vg00/lvol4 (vxfs) to /dev/vx/dsk/rootdg/homevol vxcp_lvmroot 18:07: Copying /dev/vg00/lvol5 (vxfs) to /dev/vx/dsk/rootdg/optvol vxcp_lvmroot 18:14: Copying /dev/vg00/lvol6 (vxfs) to /dev/vx/dsk/rootdg/tmpvol vxcp_lvmroot 18:15: Copying /dev/vg00/lvol7 (vxfs) to /dev/vx/dsk/rootdg/usrvol vxcp_lvmroot 18:32: Copying /dev/vg00/lvol8 (vxfs) to /dev/vx/dsk/rootdg/varvol vxcp_lvmroot 18:38: Copying /dev/vg00/lvol9 (vxfs) to /dev/vx/dsk/rootdg/u01vol vxcp_lvmroot 18:40: Copying /dev/vg00/lvol10 (unkn) to /dev/vx/dsk/rootdg/lvol10 vxcp_lvmroot 19:16: Setting up disk c3t8d0 as a boot disk vxcp_lvmroot 19:16: Installing fstab and fixing dev nodes on new root FS vxcp_lvmroot 19:16: Installing bootconf & rootconf files in new stand FS vxcp_lvmroot 19:16: Disk c3t8d0 is now a VxVM rootable boot disk root @uksd3 # root @uksd3 # vxdg list NAME STATE ID rootdg enabled 1068573947.1025.uksd3 root @uksd3 # root @uksd3 # vxprint -g rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg rootdg rootdg - - - - - - dm rootaux01 c3t10d0 - 35562186 - - - - dm rootdisk01 c3t8d0 - 35560170 - - - - v homevol fsgen ENABLED 155648 - ACTIVE - - pl homevol-01 homevol ENABLED 155648 - ACTIVE - - sd rootdisk01-04 homevol-01 ENABLED 155648 0 - - - v lvol10 gen ENABLED 24616960 - ACTIVE - - pl lvol10-01 lvol10 ENABLED 24616960 - ACTIVE - - sd rootdisk01-10 lvol10-01 ENABLED 12308480 0 - - - sd rootaux01-01 lvol10-01 ENABLED 12308480 0 - - - v optvol fsgen ENABLED 1314816 - ACTIVE - - pl optvol-01 optvol ENABLED 1314816 - ACTIVE - - sd rootdisk01-05 optvol-01 ENABLED 1314816 0 - - - v rootvol root ENABLED 204800 - ACTIVE - - pl rootvol-01 rootvol ENABLED 204800 - ACTIVE - - sd rootdisk01-03 rootvol-01 ENABLED 204800 0 - - - v standvol fsgen ENABLED 307200 - ACTIVE - - pl standvol-01 standvol ENABLED 307200 - ACTIVE - - sd rootdisk01-01 standvol-01 ENABLED 307200 0 - - - v swapvol swap ENABLED 4194304 - ACTIVE - - pl swapvol-01 swapvol ENABLED 4194304 - ACTIVE - - sd rootdisk01-02 swapvol-01 ENABLED 4194304 0 - - - v tmpvol fsgen ENABLED 204800 - ACTIVE - - pl tmpvol-01 tmpvol ENABLED 204800 - ACTIVE - - sd rootdisk01-06 tmpvol-01 ENABLED 204800 0 - - - v usrvol fsgen ENABLED 1433600 - ACTIVE - - pl usrvol-01 usrvol ENABLED 1433600 - ACTIVE - - sd rootdisk01-07 usrvol-01 ENABLED 1433600 0 - - - v u01vol fsgen ENABLED 1024000 - ACTIVE - - pl u01vol-01 u01vol ENABLED 1024000 - ACTIVE - - sd rootdisk01-09 u01vol-01 ENABLED 1024000 0 - - - v varvol fsgen ENABLED 2097152 - ACTIVE - - pl varvol-01 varvol ENABLED 2097152 - ACTIVE - - sd rootdisk01-08 varvol-01 ENABLED 2097152 0 - - - root @uksd3 #
The boot paths for this system have not been modified because I didn't use the “b option to vxcp_lvmroot . root @uksd3 # setboot Primary bootpath : 2/0/1/0/0.0.0 Alternate bootpath : 2/0/1/0/0.8.0 Autoboot is ON (enabled) Autosearch is ON (enabled) Note: The interpretation of Autoboot and Autosearch has changed for systems that support hardware partitions. Please refer to the manpage. root @uksd3 # lssf /dev/dsk/c3t8d0 sdisk card instance 3 SCSI target 8 SCSI LUN 0 section 0 at address 2/0/4/0/0.8.0 /dev/dsk/c3t8d0 root @uksd3 # I want to test rootability before I decide to change my Primary Boot Path . I will now reboot this node and interrupt the boot process in order to boot from this VxVM device. Attempting to boot using the primary path. ------------------------------------------------------------- To discontinue, press any key within 10 seconds. Boot terminated. *** Manufacturing permissions ON *** ---- Main Menu -------------------------------------------------------------- Command Description ------- ----------- BOot [PRIHAAALT<path>] Boot from specified path PAth [PRIHAAALT] [<path>] Display or modify a path SEArch [ALL<cell><path>] Search for boot devices ScRoll [ONOFF] Display or change scrolling capability COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DeBug menu Displays debug commands MFG menu Displays manufacturing commands DIsplay Redisplay the current menu HElp [<menu><command>] Display help for menu or command REBOOT Restart Partition RECONFIGRESET Reset to allow Reconfig Complex Profile ---- Main Menu: Enter command or menu > bo 2/0/4/0/0.8.0 BCH Directed Boot Path: 2/0/4/0/0.8 Do you wish to stop at the ISL prompt prior to booting? (y/n) >> y Initializing boot Device. Boot IO Dependent Code (IODC) Revision 0 Boot Path Initialized. HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL> hpux ll Ls : disk(2/0/4/0/0.8.0.0.0.0.0;0)/. dr-xr-xr-x 10 2 2 1024 ./ dr-xr-xr-x 10 2 2 1024 ../ drwxr-xr-x 2 0 0 8192 lost+found/ -rw-r--r-- 1 0 3 7496 ioconfig -rw-r--r-- 1 0 3 19 bootconf -r--r--r-- 1 0 3 1063 system drwxr-xr-x 2 0 3 1024 krs/ drwxr-xr-x 2 0 3 1024 system.d/ drwxr-xr-x 4 0 3 1024 build/ -rwxr-xr-x 1 0 0 28133624 vmunix* drwxrwxrwx 5 0 0 1024 dlkm/ -r--r--r-- 1 0 3 82 kernrel -rw------- 1 0 0 12 rootconf drwxr-xr-x 2 0 0 24 krs_tmp/ drwxr-xr-x 2 0 0 1024 krs_lkg/ -r--r--r-- 1 0 3 1058 system.prev drwxrwxrwx 5 0 3 1024 dlkm.vmunix.prev/ -rwxr-xr-x 1 0 3 27239144 vmunix.prev* -r-xr-xr-x 1 2 2 1062320 vpmon* -rw------- 1 0 0 17813008 vpmon.dmp -rw------- 1 0 3 8232 vpdb ISL> At this point, all looks like a normal LVM-based system. In fact, there aren't many changes on the surface of it. We still use the hpux command to boot the kernel.
ISL> hpux Boot : disk(2/0/4/0/0.8.0.0.0.0.0;0)/stand/vmunix 10125312 + 1949784 + 1347720 start 0x81d7868 gate64: sysvec_vaddr = 0xc0002000 for 2 pages NOTICE: nfs3_link(): File system was registered at index 3. NOTICE: autofs_link(): File system was registered at index 6. NOTICE: cachefs_link(): File system was registered at index 7. td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 2/0/12/0/0 System Console is on the Built-In Serial Interface fddi4: INITIALIZING: 0150 PCI FDDI card in slot 2/0/10/0/0 Entering cifs_init... Initialization finished successfully... slot is 9 Swap device table: (start & size given in 512-byte blocks) entry 0 - major is 2, minor is 0x1; start = 0, size = 8388608 ... The system is ready. uksd3 [HP Release B.11.11] (see /etc/issue) Console Login: ... root @uksd3 # bdf Filesystem kbytes used avail %used Mounted on /dev/vx/dsk/rootdg/rootvol 204800 147825 53429 73% / /dev/vx/dsk/rootdg/standvol 300488 75968 194471 28% /stand /dev/vx/dsk/rootdg/varvol 2097152 903710 1118889 45% /var /dev/vx/dsk/rootdg/usrvol 1433600 801901 592229 58% /usr /dev/vx/dsk/rootdg/u01vol 1024000 924557 93280 91% /u01 /dev/vx/dsk/rootdg/tmpvol 204800 43488 151252 22% /tmp /dev/vx/dsk/rootdg/optvol 1314816 957101 335396 74% /opt /dev/vx/dsk/rootdg/homevol 155648 146704 8426 95% /home root @uksd3 # root @uksd3 # vxinfo -p -g rootdg vol standvol fsgen Started plex standvol-01 ACTIVE vol u01vol fsgen Started plex u01vol-01 ACTIVE vol varvol fsgen Started plex varvol-01 ACTIVE vol usrvol fsgen Started plex usrvol-01 ACTIVE vol tmpvol fsgen Started plex tmpvol-01 ACTIVE vol optvol fsgen Started plex optvol-01 ACTIVE vol homevol fsgen Started plex homevol-01 ACTIVE vol lvol10 gen Started plex lvol10-01 ACTIVE vol rootvol root Started plex rootvol-01 ACTIVE vol swapvol swap Started plex swapvol-01 ACTIVE root @uksd3 #
As you can see, we have a fully functioning rootdg with all our original data, and volumes running from a disk that is under the control of VxVM. It should be noted that the /stand filesystem is still an HFS filesystem:
root @uksd3 # fstyp /dev/vx/dsk/rootdg/standvol hfs root @uksd3 #
It's a minor point, but one worth remembering. There are a couple of commands we should look at in regard to the counterpart commands under LVM. To analyze the BDRA , we used the lvlnboot command. We don't have a BDRA under VxVM, but we do have a LABEL file in the LIF area. We use the vxvmboot command to read the entries in the LABEL file:
root @uksd3 # vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 1180 on VxVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 3168; length: 300 MB Label Entry: 1, Root Volume start: 4504672; length: 200 MB Label Entry: 2, Swap Volume start: 310368; length: 4096 MB Label Entry: 3, Dump Volume start: 310368; length: 4096 MB root @uksd3 #
We still have use of the mkboot and lifcp commands to interrogate the LABEL file:
root @uksd3 # lifcp /dev/rdsk/c3t8d0:AUTO - hpux root @uksd3 # mkboot -a "hpux /stand/vmunix" /dev/rdsk/c3t8d0 root @uksd3 # lifcp /dev/rdsk/c3t8d0:AUTO - hpux /stand/vmunix root @uksd3 #
Booting the system into single- user mode still works the same way, although we don't have the “lq option to boot the system, ignoring quorum; this concept doesn't exist with VxVM. We do have maintenance mode, should something happen to the underlying VxVM/boot structure ”if we lose the LABEL file, for example. The option to the hpux secondary loader is “vm : | WARNING : Before booting into VxVM Maintenance mode, if you are going to try some of these commands, you MUST install patch PHCO_27101 . Ideally, you should install the patch before starting the vxcp_lvmroot command to ensure that the patch exists on both your root disk and volume group. If you do not install the patch, VxVM and mkboot will not be able to create a workable root disk. This is from the patch text:
" The VERITAS Volume Manager (VxVM) is not able to create workable  root/boot disk on a system."
You have been warned ! |
Attempting to boot using the primary path. ------------------------------------------------------------- To discontinue, press any key within 10 seconds. Boot terminated. *** Manufacturing permissions ON *** ---- Main Menu -------------------------------------------------------------- Command Description ------- ----------- BOot [PRIHAAALT<path>] Boot from specified path PAth [PRIHAAALT] [<path>] Display or modify a path SEArch [ALL<cell><path>] Search for boot devices ScRoll [ONOFF] Display or change scrolling capability COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DeBug menu Displays debug commands MFG menu Displays manufacturing commands DIsplay Redisplay the current menu HElp [<menu><command>] Display help for menu or command REBOOT Restart Partition RECONFIGRESET Reset to allow Reconfig Complex Profile ---- Main Menu: Enter command or menu > bo 2/0/4/0/0.8.0 BCH Directed Boot Path: 2/0/4/0/0.8 Do you wish to stop at the ISL prompt prior to booting? (y/n) >> y Initializing boot Device. Boot IO Dependent Code (IODC) Revision 0 Boot Path Initialized. HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL> hpux -vm VxVM Maintenance Mode boot Boot : disk(2/0/4/0/0.8.0.0.0.0.0;0)/stand/vmunix 10125312 + 1949784 + 1347720 start 0x81d7868 gate64: sysvec_vaddr = 0xc0002000 for 2 pages NOTICE: nfs3_link(): File system was registered at index 3. NOTICE: autofs_link(): File system was registered at index 6. NOTICE: cachefs_link(): File system was registered at index 7. td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 2/0/12/0/0 System Console is on the Built-In Serial Interface fddi4: INITIALIZING: 0150 PCI FDDI card in slot 2/0/10/0/0 Entering cifs_init... Initialization finished successfully... slot is 9 Swap device table: (start & size given in 512-byte blocks) entry 0 - auto-configured on root device; ignored - no room WARNING: no swap device configured, so dump cannot be defaulted to primary swap. WARNING: No dump devices are configured. Dump is disabled. Starting the STREAMS daemons-phase 1 Starting vxconfigd in boot mode (pre_init_rc). INFO: VxVM Maintenance Mode Boot - vxconfigd aborted Checking root file system. file system is clean - log replay is not required Root check done. Create STCP device files Starting the STREAMS daemons-phase 2 $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_$ Memory Information: physical page size = 4096 bytes, logical page size = 4096 bytes Physical: 4186112 Kbytes, lockable: 3223180 Kbytes, available: 3703524 Kbyts /sbin/ioinitrc: Can't open /dev/vx/dsk/rootdg/standvol, errno = 6 /dev/vx/dsk/rootdg/standvol: CAN'T CHECK FILE SYSTEM. /dev/vx/dsk/rootdg/standvol: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/vx/dsk/rootdg/standvol: No such device or address Unable to mount /stand - please check entries in /etc/fstab Skipping KRS database initialization - /stand can't be mounted INFO: VxVM Maintenance Mode Boot - vxconfigd aborted INIT: Overriding default level with level 's' INIT: SINGLE USER MODE INIT: Running /sbin/sh # If we are going to issue any VxVM commands, we need to start the vxconfigd daemon and then effect any repairs as we see fit (repair a lost LABEL file): # vxconfigd FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured FC60 claim_device: LUN not configured NOTICE: vxvm:vxdmp: added disk array DISKS, datype = Disk NOTICE: vxvm:vxdmp: added disk array 000A00A0B8001CA2, datype = FC60 WARNING: vxvm:vxdmp: Unlicensed array S/N 000A00A0B8001CA2 installed # vxdg list NAME STATE ID rootdg enabled 1037114965.1025.uksd3 # We can now attempt to start all the volumes in the rootdg and mount our filesystems.
# vxvol -g rootdg startall # mount -a # bdf Filesystem kbytes used avail %used Mounted on /dev/vx/dsk/rootdg/rootvol 204800 147413 53813 73% / /dev/vx/dsk/rootdg/u01vol 1024000 924558 93278 91% /u01 /dev/vx/dsk/rootdg/varvol 2097152 901231 1121234 45% /var /dev/vx/dsk/rootdg/usrvol 1433600 801908 592222 58% /usr /dev/vx/dsk/rootdg/tmpvol 204800 44232 150554 23% /tmp /dev/vx/dsk/rootdg/optvol 1314816 957101 335396 74% /opt /dev/vx/dsk/rootdg/homevol 155648 146704 8426 95% /home /dev/vx/dsk/rootdg/standvol 300488 75965 194474 28% /stand #
Now I want to see what my LABEL file looks like.
# vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 834 on LVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 2912; length: 34730 MB #
There are no entries in my LABEL file. As you can imagine, this is the reason I have had problems booting the system! Because I am unsure of the state of the LIF area, I will rebuild it using the mkboot command:
# mkboot -l /dev/rdsk/c3t8d0 # # vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 834 on LVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 2912; length: 34730 MB #
As you can see, my LABEL file is still empty, but I am happy that my LIF area is now okay. I can now use the vxbootsetup command to reconstruct my LABEL file. It is at this point that you might see an error from the vxbootsetup command. If you haven't installed patch PHCO_27101 , this part ( the most important part ) of the process will fail.
# /etc/vx/bin/vxbootsetup rootdisk01 # vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 1180 on VxVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 3168; length: 300 MB Label Entry: 1, Root Volume start: 4504672; length: 200 MB Label Entry: 2, Swap Volume start: 310368; length: 4096 MB Label Entry: 3, Dump Volume start: 310368; length: 4096 MB #
Suppose you have definitely installed patch PHCO_271 01, but you are still getting an error message of the following form:
# /etc/vx/bin/vxbootsetup rootdisk01 ERROR: Could not contact host "unknown" because of an invalid protocol sequence. Protocol sequences are specified with the rpc_binding_info option. Make sure this option is specified correctly. ERROR: More information may be found in the daemon logfile on this target (default location is unknown:/var/adm/sw/swagentd.log). vxbootsetup: ERROR: Required patch PHCO_27101 not installed #
It is because the vxbootsetup command is attempting to run the swlist command, which has a problem with no networking running in Maintenance Mode. The simplest solution, if you have definitely installed patch PHCO_27101, is to edit the vxbootsetup script and comment out the lines regarding the swlist command. Alternately, you could get into the vxvmboot command, which is exactly what vxbootsetup uses:
# vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 834 on LVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 2912; length: 34730 MB # # vxvmboot -b -o 3168 -l 307200 /dev/rdsk/c3t8d0 # vxvmboot -r -o 4504672 -l 204800 /dev/rdsk/c3t8d0 # vxvmboot -s -o 310368 -l 4194304 /dev/rdsk/c3t8d0 # vxvmboot -d -o 310368 -l 4194304 /dev/rdsk/c3t8d0 # vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 834 on VxVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 3168; length: 300 MB Label Entry: 1, Root Volume start: 4504672; length: 200 MB Label Entry: 2, Swap Volume start: 310368; length: 4096 MB Label Entry: 3, Dump Volume start: 310368; length: 4096 MB # # reboot
The offset ( -o ) is as displayed by vxvmboot “v , but the length ( -l ) of each volume is specified in kilobytes even though it is displayed in megabytes. In order to run the vxvmboot command successfully, you will need to know the sizes and offsets of each of the volumes. As always when we are in Maintenance Mode, we never take the system directly to multi-user mode; we reboot first. Just before we finish, here is an idea to test VxVM's rootability . If you have a spare disk, you can simply use the vxcp_lvmroot command to set up a rootdg that is a copy of your existing LVM vg00 , as demonstrated above. Using this, we can test whether VxVM rootability is a good option for your installation. What would be even better after that is to set up Virtual Partitions, if your server supports them. You could then have two systems running simultaneously , one with LVM boot/root and one with VxVM boot/root. In fact, that is what I have done here. I have booted my VxVM configuration and changed the hostname. Now, I have one vPar running as uksd3 , using LVM:
root @uksd3 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================== ===== ========== ===================== ===== vPar0 Up Dyn,Auto /stand/vmunix vPar1 Up Dyn,Auto /stand/vmunix [Virtual Partition Resource Summary] CPU Num Memory (MB) CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== vPar0 1/ 5 1 1 9 0/ 0 2048 vPar1 1/ 2 1 1 5 0/ 0 2048 root @uksd3 # vparstatus -w The current virtual partition is vPar0. root @uksd3 # lvlnboot -v vg00 Boot Definitions for Volume Group /dev/vg00: Physical Volumes belonging in Root Volume Group: /dev/dsk/c0t0d0 (2/0/1/0/0.0.0) -- Boot Disk /dev/dsk/c0t1d0 (2/0/1/0/0.1.0) Boot: lvol1 on: /dev/dsk/c0t0d0 Root: lvol3 on: /dev/dsk/c0t0d0 Swap: lvol2 on: /dev/dsk/c0t0d0 Dump: lvol2 on: /dev/dsk/c0t0d0, 0 root @uksd3 #
I also have another vPar running as uksd5 , using VxVM:
root @uksd3 # <ctrl-a> [vPar1] root @uksd5 # vparstatus -w The current virtual partition is vPar1. root @uksd5 # vxvmboot -v /dev/rdsk/c3t8d0 LIF Label File @ (1k) block # 834 on VxVM Disk /dev/rdsk/c3t8d0: Label Entry: 0, Boot Volume start: 3168; length: 300 MB Label Entry: 1, Root Volume start: 4504672; length: 200 MB Label Entry: 2, Swap Volume start: 310368; length: 4096 MB Label Entry: 3, Dump Volume start: 310368; length: 4096 MB root @uksd5 #
Both vPars are running within a Superdome nPar:
root @uksd5 # parstatus -P [Partition] Par # of # of I/O Num Status Cells Chassis Core cell Partition Name (first 30 chars) === ============ ===== ======== ========== =============================== 1 active 2 2 cab0,cell0 uksd2 2 active 1 1 cab0,cell2 uksd3 3 active 1 1 cab0,cell6 uksd4 root @uksd5 # parstatus -w The local partition number is 2. root @uksd5 # root @uksd5 # model 9000/800/SD32000 root @uksd5 #
Cool, huh? | 