How to extend a subvolume filesystem

raunaz · ‎11-09-2011

Hi Guys,

I need to extend a vxfs filesystem that is using subvolume. I did'nt manage to get the correct short way.
I managed to create up to subvolume, but didn't get how to extend the subvolume i have created in the main volume.

vxprint -hr -g p40sapdata1dg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

dg p40sapdata1dg p40sapdata1dg - - - - - -

dm p40sapdata1dg01 xp24k0_4070 - 1048368224 - - - -

dm p40sapdata1dg02 xp24k0_4071 - 1048368224 - - - -

dm p40sapdata1dg03 xp24k0_4072 - 1048368224 - - - -

dm p40sapdata1dg04 xp24k1_4107 - 1048368224 - - - -

dm p40sapdata1dg05 xp24k1_4108 - 1048368224 - - - -

dm p40sapdata1dg06 xp24k1_4109 - 1048368224 - - - -

v sapdata1 fsgen ENABLED 3145090000 - ACTIVE - -

pl sapdata1-04 sapdata1 ENABLED 3145090000 - ACTIVE - -

sv sapdata1-S01 sapdata1-04 ENABLED 1048368224 0 - - -

v2 sapdata1-L01 fsgen ENABLED 1048368224 - ACTIVE - -

p2 sapdata1-P01 sapdata1-L01 ENABLED LOGONLY - ACTIVE - -

s2 p40sapdata1dg06-02 sapdata1-P01 ENABLED 4160 LOG - - -

p2 sapdata1-P02 sapdata1-L01 ENABLED 1048368224 - ACTIVE - -

s2 p40sapdata1dg04-02 sapdata1-P02 ENABLED 1048368224 0 - - -

p2 sapdata1-P03 sapdata1-L01 ENABLED 1048368224 - ACTIVE - -

s2 p40sapdata1dg01-02 sapdata1-P03 ENABLED 1048368224 0 - - -

sv sapdata1-S02 sapdata1-04 ENABLED 1048368224 1048368224 - - -

v2 sapdata1-L02 fsgen ENABLED 1048368224 - ACTIVE - -

p2 sapdata1-P04 sapdata1-L02 ENABLED LOGONLY - ACTIVE - -

s2 p40sapdata1dg06-03 sapdata1-P04 ENABLED 4160 LOG - - -

p2 sapdata1-P05 sapdata1-L02 ENABLED 1048368224 - ACTIVE - -

s2 p40sapdata1dg05-02 sapdata1-P05 ENABLED 1048368224 0 - - -

p2 sapdata1-P06 sapdata1-L02 ENABLED 1048368224 - ACTIVE - -

s2 p40sapdata1dg02-02 sapdata1-P06 ENABLED 1048368224 0 - - -

sv sapdata1-S03 sapdata1-04 ENABLED 1048353552 2096736448 - - -

v2 sapdata1-L03 fsgen ENABLED 1048353552 - ACTIVE - -

p2 sapdata1-P07 sapdata1-L03 ENABLED LOGONLY - ACTIVE - -

s2 p40sapdata1dg06-04 sapdata1-P07 ENABLED 4160 LOG - - -

p2 sapdata1-P08 sapdata1-L03 ENABLED 1048353552 - ACTIVE - -

s2 p40sapdata1dg06-05 sapdata1-P08 ENABLED 1048353552 0 - - -

p2 sapdata1-P09 sapdata1-L03 ENABLED 1048353552 - ACTIVE - -

s2 p40sapdata1dg03-03 sapdata1-P09 ENABLED 1048353552 0 - - -

# rpm -qa | grep -i vx

HPOvXercesA-2.07.063-1

VRTSvxvm-5.1.101.000-SP1RP1_SLES11

VRTSvxfen-5.1.101.000-SP1RP1_SLES11

HPOvXpl-6.20.110-1

VRTSvxfs-5.1.101.002-RP1HF2_SLES11

HPOvXalanA-1.10.073-1

# cat /etc/*release

SUSE Linux Enterprise Server 11 (x86_64)

VERSION = 11

PATCHLEVEL = 1

LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"

raunaz · ‎11-09-2011

any comments? Appreciate for the help

TonyGriffiths · ‎11-10-2011

Hi

Do you know how the volume was created ?

Could you provide vxprint -ht display i.e

vxprint -g p40sapdata1dg -ht sapdata1

It should be the case that a grow operation on the upper volume (sapdata1) will grow the sub structures required for the resize as long as there is free space

Look up vxresize command that will resize volume and file system

cheers

tony

Tmy_70 · ‎11-10-2011

RESIZE

VEA: ACTION -> VOLUMES T FS

VXASIST: VOLUME

FSADM: VXFS

VEA: Select action-> resize volume
CLI: vxassist -g datadg growto/growby Shrikto/Shrikby
vxresize -b fstype -g diskgroup volumen
vxassit growto/growby/shrinkto/shrinkby <volname> <length>
vxvol set len=<length> <volname>

RESIZE Dinamico:

VEA: ACTIONS-> RESIZE DISK

CLI: vxdisk -F -g DISKGROUP reize Dmname

resize a filesystem (ufs cannot be shrunk, only grown)

# vxresize -g <diskgroup> <volumename> + <size>
# vxresize -g <diskgroup> <volumename> - <size>

Yasuhisa_Ishika · ‎11-10-2011

It seems that you have created RAID1+0(striped-mirror) volume using whole space of 6 disks. You have to add at least 2 disks into this disk group before you grow the volume & filesystem using vxresize or etc..

TonyGriffiths · ‎11-10-2011

Here is the vxresize man page

https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/manualpages/html/man/volume_manager/html/man1m/vxresize.1m.html

Gaurav_S · ‎11-11-2011

I think there is little mis-calculation here...

you have total disk space of 6290209344 ( i.e 1048368224 * 6) which translates to 2999 G (approx 3000G)

what you have used currently is 3145090000 which translates to 1499 G (1500 G) :

v sapdata1 fsgen ENABLED 3145090000 - ACTIVE - -
pl sapdata1-04 sapdata1 ENABLED 3145090000 - ACTIVE - -

So you stil have almost 1499 G of space left...

So question is what is the issue with resize ?

Lets understand the volume structure, so you actually have concat at the top layer & mirror at the lower layer, so it is a concat-mirror

sv sapdata1-S01 sapdata1-04 ENABLED 1048368224 0      -        -       -
sv sapdata1-S02 sapdata1-04 ENABLED 1048368224 1048368224 -    -       -
sv sapdata1-S03 sapdata1-04 ENABLED 1048353552 2096736448 -    -       -

I would expect the resize to go normally over here because if you run a vxresize, it should ideally create one more subvolume & concat the same with existing subvolumes ..

vxresize -t <filesystem> <volume> <new_length>

Please note, for volume & FS both to resize, you should have FS mounted..

Is there any specific error you faced ?

Gaurav

Yasuhisa_Ishika · ‎11-13-2011

1.5TB RAID1+0 of 2 way mirror required 3TB capacity.
No space left now.

VOX

How to extend a subvolume filesystem