cancel
Showing results for 
Search instead for 
Did you mean: 

VXVM Strip volume extension

Hello,

I have the following issue.

 

sunstation1:/root# vxassist -g DG-DB001 maxsize
Maximum volume size: 326191104 (159273Mb)------------------------->It is showing that volume can be increased up to 159273Mb
sunstation1:/root#
sunstation1:/root#
sunstation1:/root# /etc/vx/bin/vxresize -g DG-DB001 VOL-DB001-data1 +50g
VxVM vxassist ERROR V-5-1-436 Cannot allocate space to grow volume to 1498001965 blocks
VxVM vxresize ERROR V-5-1-4703 Problem running vxassist command for volume VOL-DB001-data1, in diskgroup DG-DB001

 

Is it due to any internal restriction of the Volume manager.

 

 

regards

Arup

1 Solution

Accepted Solutions
Accepted Solution!

Your volume is an 8-way

Your volume is an 8-way stripe (STRIPE 8/512) so you will need 8 LUNs to increase the size of the volume.

If you don't have 8 LUNs, then you will need to with do a "vxassist relayout" which just needs a relatively small tmp space to relayout, but takes a while to relayout and effects peformance of volume or you can mirror to a new LUN as concat and then remove old mirror, but this requires you temporarlly assign double the storage, but has less impact on performance - see https://www-secure.symantec.com/connect/forums/how-expand-dg-vgbackup-and-after-filesystem-prod01p

Mike

View solution in original post

8 Replies

Hello, What is the structure

Hello,

What is the structure of the volume ? can you paste the output of vxprint ?

It is quite possible that striped volume is getting spread across multiple disks & the available space is all available from one or multiple disk however not enough to equally cut the stripes to grow the volume ..

so if the volume has 3 stripes, you should have spaces available in 3 different disks in order for resize to succeed ...

Alternatively, you can try below technote

https://support.symantec.com/en_US/article.TECH136828.html

 

G

Arup, 'vxassist -g xxx

Arup,

'vxassist -g xxx maxsize' will list free blocks in the disk group (without regard to volume geometry).

Instead, use 'vxassist -g xxx maxgrow <volume_name>' to list the amount that a specific volume can grow, taking into account the volume's geometry (concat vs stripe vs mirror).

You should do a 'vxprint -ht' before and after to see how the disks are mapped to the stripes. It should be a unique disk for each stripe in the volume.

Ken W

Hello Gaurav Please refere

Hello Gaurav

Please refere the below output--

sunstation1:/root# vxprint -htqg DG-DB001 VOL-DB001-data1
v  VOL-DB001-data1 -       ENABLED  ACTIVE   1414115885 SELECT  VOL-DB001-data1-01 fsgen
pl VOL-DB001-data1-01 VOL-DB001-data1 ENABLED ACTIVE 1414164480 STRIPE 8/512 RW
sd DSK-DG-DB001-110d-01 VOL-DB001-data1-01 DSK-DG-DB001-110d 3328 170826240 0/0 xp24k1_110d ENA
sd DSK-DG-DB001-1369-02 VOL-DB001-data1-01 DSK-DG-DB001-1369 2107648 3317760 0/170826240 xp24k1_1369 ENA
sd DSK-DG-DB001-1369-04 VOL-DB001-data1-01 DSK-DG-DB001-1369 110288128 2626560 0/174144000 xp24k1_1369 ENA
sd DSK-DG-DB001-110f-01 VOL-DB001-data1-01 DSK-DG-DB001-110f 3328 170826240 1/0 xp24k1_110f ENA
sd DSK-DG-DB001-136B-02 VOL-DB001-data1-01 DSK-DG-DB001-136B 20969728 5944320 1/170826240 xp24k1_136b ENA
sd DSK-DG-DB001-1100-01 VOL-DB001-data1-01 DSK-DG-DB001-1100 3328 170826240 2/0 xp24k1_1100 ENA
sd DSK-DG-DB001-1112-03 VOL-DB001-data1-01 DSK-DG-DB001-1112 21292288 5944320 2/170826240 xp24k1_1112 ENA
sd DSK-DG-DB001-1101-01 VOL-DB001-data1-01 DSK-DG-DB001-1101 3328 170826240 3/0 xp24k1_1101 ENA
sd DSK-DG-DB001-110e-02 VOL-DB001-data1-01 DSK-DG-DB001-110e 49024768 5944320 3/170826240 xp24k1_110e ENA
sd DSK-DG-DB001-1102-01 VOL-DB001-data1-01 DSK-DG-DB001-1102 3328 170826240 4/0 xp24k1_1102 ENA
sd DSK-DG-DB001-110c-02 VOL-DB001-data1-01 DSK-DG-DB001-110c 83891968 5944320 4/170826240 xp24k1_110c ENA
sd DSK-DG-DB001-1103-01 VOL-DB001-data1-01 DSK-DG-DB001-1103 3328 170826240 5/0 xp24k1_1103 ENA
sd DSK-DG-DB001-1368-02 VOL-DB001-data1-01 DSK-DG-DB001-1368 135232768 5944320 5/170826240 xp24k1_1368 ENA
sd DSK-DG-DB001-1104-01 VOL-DB001-data1-01 DSK-DG-DB001-1104 3328 170826240 6/0 xp24k1_1104 ENA
sd DSK-DG-DB001-110b-02 VOL-DB001-data1-01 DSK-DG-DB001-110b 164723968 5944320 6/170826240 xp24k1_110b ENA
sd DSK-DG-DB001-1105-01 VOL-DB001-data1-01 DSK-DG-DB001-1105 3328 170826240 7/0 xp24k1_1105 ENA
sd DSK-DG-DB001-1111-03 VOL-DB001-data1-01 DSK-DG-DB001-1111 165430528 5399040 7/170826240 xp24k1_1111 ENA
sd DSK-DG-DB001-1640-01 VOL-DB001-data1-01 DSK-DG-DB001-1640 3328 545280 7/176225280 xp24k1_1640 ENA

 

 

Hello Haniwa Thank you for

Hello Haniwa

 

Thank you for your reply. Yes the volumes are stipe one.Out put is already posted in reply to Gaurav.

Accepted Solution!

Your volume is an 8-way

Your volume is an 8-way stripe (STRIPE 8/512) so you will need 8 LUNs to increase the size of the volume.

If you don't have 8 LUNs, then you will need to with do a "vxassist relayout" which just needs a relatively small tmp space to relayout, but takes a while to relayout and effects peformance of volume or you can mirror to a new LUN as concat and then remove old mirror, but this requires you temporarlly assign double the storage, but has less impact on performance - see https://www-secure.symantec.com/connect/forums/how-expand-dg-vgbackup-and-after-filesystem-prod01p

Mike

View solution in original post

Hi,    You should try:  

Hi, 

  You should try:

  vxassist -g DG-DB001 maxsize layout=stripe ncol=8

 

same layout as your current volume.

 

As others have mentioned, the

As others have mentioned, the error is most likely due to the fact that the grow operation is requiring free space from 8 devices as the volume is of a striped layout.

 

cheers

tony

Thank you all,all of you

Thank you all,all of you pointining to the correct root cause.The same has been communicated to the end customer also.Kudos to all!!!!