expand veritas file system from gz on 3par

Markets GroupSystems ManagementVeritas File System Expansion for Global Zone Mount Point from 3PAR Array ______________________________

Internal

Identify the file systems on the Local Zone that is being requested for the disk space increase (in bold):

b7qcapshdb2[b3mce01] df -h |grep caps/caps00 27G 11G 15G 42% /caps00/caps01 16G 15G 1.1G 94% /caps01/caps02 42G 27G 14G 66% /caps02/caps03 50G 17G 31G 36% /caps03/capsfra 100G 71G 27G 73% /capsfrab7qcapshdb2[b3mce01]

On the Local Zone identify the hostname of the Global Zone where the Veritas changes will take place:

b7qcapshdb2[b3mce01] arp -a |grep SPLAnxge2 b7qgz9_m.mg.ny.frb.org 255.255.255.255 SPLA 00:21:28:34:95:00nxge0 b7qgz9.mg.ny.frb.org 255.255.255.255 SPLA 00:21:28:34:94:fenxge0 b7qcapsdb2.mg.ny.frb.org 255.255.255.255 SPLA 00:21:28:34:94:fenxge0 b7qcapshdb2 255.255.255.255 SPLA 00:21:28:34:94:fenxge2 b7qcapsdb2_m.mg.ny.frb.org 255.255.255.255 SPLA 00:21:28:34:95:00nxge2 b7qcapshdb2_m.mg.ny.frb.org 255.255.255.255 SPLA 00:21:28:34:95:00b7qcapshdb2[b3mce01]

On the Global Zone identify the disk group and devices associated to the Local Zone’s file system(s) – keeping in mind that the “FSdg” disk group is associated with the local zones file system and the “LZdg” disk group is associated with the Local Zone itself:

b7qgz9[root] vxdisk -o alldgs list |grep capsc3t22540002AC0008D9d1s2 auto:cdsdisk - (b7qcapsdb1_LZdg) online udid_mismatchc3t22540002AC0008D9d2s2 auto:cdsdisk - (b7qcapsdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d3s2 auto:cdsdisk - (b7qcapsdb1_FSdg) online udid_mismatchc3t22540002AC0008D9d4s2 auto:cdsdisk - (b7qcapsdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d5s2 auto:cdsdisk - (b7qcapshdb1_LZdg) online udid_mismatchc3t22540002AC0008D9d6s2 auto:cdsdisk - (b7qcapshdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d7s2 auto:cdsdisk - (b7qcapshdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d8s2 auto:cdsdisk b7qcapsdb2_LZdg01 b7qcapsdb2_LZdg onlinec3t22540002AC0008D9d9s2 auto:cdsdisk b7qcapsdb2_ORAdg01 b7qcapsdb2_ORAdg onlinec3t22540002AC0008D9d10s2 auto:cdsdisk b7qcapsdb2_ORAdg02 b7qcapsdb2_ORAdg onlinec3t22540002AC0008D9d11s2 auto:cdsdisk b7qcapsdb2_FSdg01 b7qcapsdb2_FSdg online


Internal

c3t22540002AC0008D9d12s2 auto:cdsdisk b7qcapshdb2_LZdg01 b7qcapshdb2_LZdg onlinec3t22540002AC0008D9d13s2 auto:cdsdisk b7qcapshdb2_ORAdg01 b7qcapshdb2_ORAdg onlinec3t22540002AC0008D9d14s2 auto:cdsdisk b7qcapshdb2_ORAdg02 b7qcapshdb2_ORAdg onlineb7qgz9[root]

Perform the following on the 3PAR GUI:

Identify the CPG associated for the application for the Oracle Database (which is usually for the LZ, File System and Oracle DB – the “FRA” is normally under the “x.ORACLE_FRA.CPG):

Identify the Virtual Volume that would be associated with the Disk Group:

Identify the VLUN that is associated with the Virtual Volume:

Run a vxdisk command again to identify the physical disk associated from the VLUN:

Perform the following back on the Global Zone server:

After identifying the VLUN from the 3PAR, find the disk that is associated with the VLUN within the disk group:

b7qgz9[root] vxdisk -o alldgs listDEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:sliced rootdg01 rootdg onlinec1t1d0s2 auto:sliced rootdg02 rootdg onlinec3t22540002AC0008D9d1s2 auto:cdsdisk - (b7qcapsdb1_LZdg) online udid_mismatch


Internal

c3t22540002AC0008D9d2s2 auto:cdsdisk - (b7qcapsdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d3s2 auto:cdsdisk - (b7qcapsdb1_FSdg) online udid_mismatchc3t22540002AC0008D9d4s2 auto:cdsdisk - (b7qcapsdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d5s2 auto:cdsdisk - (b7qcapshdb1_LZdg) online udid_mismatchc3t22540002AC0008D9d6s2 auto:cdsdisk - (b7qcapshdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d7s2 auto:cdsdisk - (b7qcapshdb1_ORAdg) online udid_mismatchc3t22540002AC0008D9d8s2 auto:cdsdisk b7qcapsdb2_LZdg01 b7qcapsdb2_LZdg onlinec3t22540002AC0008D9d9s2 auto:cdsdisk b7qcapsdb2_ORAdg01 b7qcapsdb2_ORAdg onlinec3t22540002AC0008D9d10s2 auto:cdsdisk b7qcapsdb2_ORAdg02 b7qcapsdb2_ORAdg onlinec3t22540002AC0008D9d11s2 auto:cdsdisk b7qcapsdb2_FSdg01 b7qcapsdb2_FSdg onlinec3t22540002AC0008D9d12s2 auto:cdsdisk b7qcapshdb2_LZdg01 b7qcapshdb2_LZdg onlinec3t22540002AC0008D9d13s2 auto:cdsdisk b7qcapshdb2_ORAdg01 b7qcapshdb2_ORAdg onlinec3t22540002AC0008D9d14s2 auto:cdsdisk b7qcapshdb2_ORAdg02 b7qcapshdb2_ORAdg onlineb7qgz9[root]

Run a format command for that physical disk (without the s2 reference) and confirm that it is the right size that is identified from the 3PAR GUI:

b7qgz9[root] format c3t22540002AC0008D9d13……………….……………….partition> pCurrent partition table (original):Total disk cylinders available: 58204 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks 0 unassigned wm 0 0 (0/0/0) 0 1 unassigned wm 0 0 (0/0/0) 0 2 backup wu 0 - 58203 134.99GB (58204/0/0) 283104256 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 - wu 0 - 58203 134.99GB (58204/0/0) 283104256

partition>


Internal

Perform the following on the 3PAR GUI:

Increase the size of the Virtual Volume from 135GB to 170GB based on the following screen shots:


Internal


Internal

Click next:


Internal

Verify the new size of the Virtual Volume :


Internal

Perform the following back on the Global Zone server:

Now have Veritas resize the physical disk in the associated disk group:

b7qgz9[root] vxdisk -g b7qcapshdb2_ORAdg resize c3t22540002AC0008D9d13b7qgz9[root]

Run a format for the selected disk and verify that it is now 170GB:

b7qgz9[root] format c3t22540002AC0008D9d13selecting c3t22540002AC0008D9d13………………..………………..………………..partition> pCurrent partition table (original):Total disk cylinders available: 65533 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks 0 unassigned wm 0 0 (0/0/0) 0 1 unassigned wm 0 0 (0/0/0) 0 2 backup wu 0 - 65532 169.99GB (65533/0/0) 356499520 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 - wu 0 - 65532 169.99GB (65533/0/0) 356499520

partition>

After exiting out of format, perform a vxprint for the specific disk group so you can confirm the physical disk(s) assigned as well as the volumes associated:

b7qgz9[root] vxprint -g b7qcapshdb2_ORAdg


Internal

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0dg b7qcapshdb2_ORAdg b7qcapshdb2_ORAdg - - - - - -

dm b7qcapshdb2_ORAdg01 c3t22540002AC0008D9d13s2 - 356433728 - - - -dm b7qcapshdb2_ORAdg02 c3t22540002AC0008D9d14s2 - 209639808 - - - -

v caps00 fsgen ENABLED 56623104 - ACTIVE - -pl caps00-01 caps00 ENABLED 56623104 - ACTIVE - -sd b7qcapshdb2_ORAdg01-01 caps00-01 ENABLED 56623104 0 - - -

v capsfra fsgen ENABLED 209639424 - ACTIVE - -pl capsfra-01 capsfra ENABLED 209639424 - ACTIVE - -sd b7qcapshdb2_ORAdg02-01 capsfra-01 ENABLED 209639424 0 - - -



v caps03 fsgen ENABLED 104779776 - ACTIVE - -pl caps03-01 caps03 ENABLED 104779776 - ACTIVE - -sd b7qcapshdb2_ORAdg01-04 caps03-01 ENABLED 104779776 0 - - -b7qgz9[root]

Check to see what space is free within each disk (remember for this exercise we have been using d13) assigned to the disk group:

b7qgz9[root] vxdg -g b7qcapshdb2_ORAdg freeDISK DEVICE TAG OFFSET LENGTH FLAGSb7qcapshdb2_ORAdg01 c3t22540002AC0008D9d13s2 c3t22540002AC0008D9d13 283037696 73396032 -b7qcapshdb2_ORAdg02 c3t22540002AC0008D9d14s2 c3t22540002AC0008D9d14 209639424 384 -b7qgz9[root]

Check to see how much additional disk you can add to a volume within the disk group:


Internal

b7qgz9[root] vxassist -g b7qcapshdb2_ORAdg maxsizeMaximum volume size: 73396224 (35838Mb)b7qgz9[root]

Check to see the maximum growth of a volume within the disk group (in this case /caps01):

b7qgz9[root] vxassist -g b7qcapshdb2_ORAdg maxgrow caps01Volume caps01 can be extended by 73396224 to: 106950656 (52222Mb)b7qgz9[root]

Check to see the maximum growth of a volume within the disk group (in this case /caps02):

b7qgz9[root] vxassist -g b7qcapshdb2_ORAdg maxgrow caps02Volume caps02 can be extended by 73396224 to: 161476608 (78846Mb)b7qgz9[root]

Verify again the current size(s) of the file systems on the Local Zone (you could also look on the Global Zone as well):

b7qcapshdb2[b3mce01] df -h |grep caps/caps00 27G 11G 15G 41% /caps00/caps01 16G 15G 1.1G 94% /caps01/caps02 42G 27G 14G 66% /caps02/caps03 50G 17G 31G 36% /caps03/capsfra 100G 71G 27G 73% /capsfrab7qcapshdb2[b3mce01]

Add an additional 15GB of space to the /caps01 directory (volume) from the Global Zone:

b7qgz9[root] /etc/vx/bin/vxresize -g b7qcapshdb2_ORAdg caps01 +15gb7qgz9[root]

Verify the growth of the file system:

b7qcapshdb2[b3mce01] df -h |grep caps01/caps01 31G 15G 15G 50% /caps01


Internal

b7qcapshdb2[b3mce01]

Add an additional 15GB of space to the /caps02 directory (volume) from the Global Zone:

b7qgz9[root] /etc/vx/bin/vxresize -g b7qcapshdb2_ORAdg caps02 +15gb7qgz9[root]

Verify the growth of the file system:

b7qcapshdb2[b3mce01] df -h |grep caps02/caps02 57G 27G 28G 49% /caps02b7qcapshdb2[b3mce01]

You can check to see what space is available for volume growth for future expansion (in this case it is about 5GB):

b7qgz9[root] vxassist -g b7qcapshdb2_ORAdg maxsizeMaximum volume size: 10481664 (5118Mb)b7qgz9[root]

expand veritas file system from gz on 3par

Documents

current partition table

global zone server

total disk cylinders

global zone

local zone

reserved cylinders

disk group

partition