Lets find out how much space is free in vvrdg diskgroup for volume resizing.
# vxdg -g vvrdg free
DISK DEVICE TAG OFFSET LENGTH FLAGS
vvrdg01 disk_0 disk_0 699200 1328064 -
vvrdg02 disk_1 disk_1 699200 1328064 -
vvrdg03 disk_3 disk_3 699136 1328128 -
vvrdg04 disk_4 disk_4 512000 1515264 -
vvrdg05 disk_5 disk_5 512000 1515264 -
vvrdg06 disk_6 disk_6 0 2027264 -
Note - Total free size available for resizing is 4 GB (1328064+1328064+1328128+1515264+1515264+2027264=> (9042048/(2*1024*1024) => 4 GB)
Lets check using vxassist command too ->
# vxassist -g vvrdg maxgrow vol1
Volume vol1 can be extended by 8527872 to: 10625024 (5188Mb)
Note - this volume vol1 could be extended by 8527872, which is the approximately 4 GB ( 8527872/(2*1024*1024)
Note - Please make sure replication status is intact for the local RVG and all the flags are in active status.
Lets increase volume size by additional 3GB,
# vradmin -g diskgroupname resizevol rvg_name volumename +3G
After this we verified the volume size both in VVR primary and secondary, and also mounted UFS filesytem increased successfully.
Applies To
Two sites, one VVR primary and VVR secondary with vxvm volume and underneath we have UFS filesystem which configured and mounted under solaris localzone with devicename as rdmp device.
We could verify localzone config file consists entry of rdmp device /dev/vx/rdmp/dgname/volumename
Vxvm volume needs to resize is under Replicated Data Set, and which is a UFS filesystem and mounted in primary and volume replication going on to DR site