Adding Storage to a System File.


 
Thread Tools Search this Thread
Operating Systems AIX Adding Storage to a System File.
# 1  
Old 02-08-2011
MySQL Adding Storage to a System File.

Guys,

I have been asked to do the following:

Please add the following space in system AAAAA
/dev/sapdata5qa - 9.00GB
/dev/sapdata6qa - 7.75GB
/dev/sapdata7qa - 11.00GB
/dev/sapdata8qa - 7.50GB

I have never done this before.

We have 4 Volume Groups:

rootvg
pd2vg
qa2vg
pagingvp

Questions:

1. Do I need to identify from which volume group I want to pull this storage ?
2. What is the command to add the storage to the file system?
3. Do I need to do anything with the system before adding the storage?
4. Do I need to do anything with the system after adding the storage?

I know I can verify it with df -g

Thank you guys!
# 2  
Old 02-08-2011
I presume you mean "file system" (your subject line says "system file")?

1. Yes. You need to know which volume groups these logical volumes belong to (looking at the names, I would guess qa2vg).
Code:
lslv sapdata5qa
lslv ... etc for each

Run lsvg <volume group name>. Perhaps the space you need is already available.
Code:
lsvg $(lsvg) | grep -E "VOLUME|FREE"

2. Use chfs to add space to a filesystem
Code:
chfs -a size=+X ...
chfs -a size=X

where +X is to increase by an amount (like +1G, +100M, etc. and =X is to increase it to X (like =1G, 100M, etc.). Read the man page for chfs.

3. Have the disks been added? Did you run cfgmgr, then have a look with lspv. You should change the healthcheck interval to 60 using chdev. Extend the volume group(s) with the new disk(s). Read man extendvg. You may need to run chlv -x to increase the maximum LV's for the logical volumes. If chfs fails because of that, it will tell you what the value should be. Are the logical volumes striped (lslv will show this.)?

4. df -g should be sufficient.
# 3  
Old 02-08-2011
what version of AIX are you running?
By the names of the File systems I would say they are all qa so a lsvg of qa2vg to see if free space is there
then a
Code:
 lsvg -p qa2vg

to get a look at the distrbution.
Now is this san disk, or SSA or local scsi?
but the command to extend could be different if say AIX 5.2 or AIZ 5.3 ML8
maybe a
Code:
 oslevel -s

so we know.

Lets start with some of this info first.

Last edited by dukessd; 02-08-2011 at 08:18 PM.. Reason: added close code tag - good effort though.
# 4  
Old 02-09-2011
Quote:
Originally Posted by scottn
I presume you mean "file system" (your subject line says "system file")?

1. Yes. You need to know which volume groups these logical volumes belong to (looking at the names, I would guess qa2vg).
Code:
lslv sapdata5qa
lslv ... etc for each

Run lsvg <volume group name>. Perhaps the space you need is already available.
Code:
lsvg $(lsvg) | grep -E "VOLUME|FREE"

2. Use chfs to add space to a filesystem
Code:
chfs -a size=+X ...
chfs -a size=X

where +X is to increase by an amount (like +1G, +100M, etc. and =X is to increase it to X (like =1G, 100M, etc.). Read the man page for chfs.

3. Have the disks been added? Did you run cfgmgr, then have a look with lspv. You should change the healthcheck interval to 60 using chdev. Extend the volume group(s) with the new disk(s). Read man extendvg. You may need to run chlv -x to increase the maximum LV's for the logical volumes. If chfs fails because of that, it will tell you what the value should be. Are the logical volumes striped (lslv will show this.)?

4. df -g should be sufficient.

Here are some more information:

1. YES, all are in qa2vg volume group.

2. Understood. Thanks!

3. This is the output of lsvg qa2vg:
Code:
$ lsvg qa2vg
VOLUME GROUP:       qa2vg                    VG IDENTIFIER:  00072f5a0000d400000001257ec070fc
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      13564 (1736192 megabytes)
MAX LVs:            256                      FREE PPs:       282 (36096 megabytes)
LVs:                32                       USED PPs:       13282 (1700096 megabytes)
OPEN LVs:           32                       QUORUM:         19 (Enabled)
TOTAL PVs:          36                       VG DESCRIPTORS: 36
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         36                       AUTO ON:        yes
MAX PPs per VG:     32768                    MAX PVs:        1024
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable

4. Understood.

Does the information in number 3 helps to explain a bit better what to do or check in number 3?

Thanks again!

---------- Post updated at 13:03 ---------- Previous update was at 12:58 ----------

Quote:
Originally Posted by aix-guy
what version of AIX are you running?
By the names of the File systems I would say they are all qa so a lsvg of qa2vg to see if free space is there
then a
Code:
 lsvg -p qa2vg

to get a look at the distrbution.
Now is this san disk, or SSA or local scsi?
but the command to extend could be different if say AIX 5.2 or AIZ 5.3 ML8
maybe a
Code:
 oslevel -s

so we know.

Lets start with some of this info first.
Output of lsvg -p qa2vg:
Code:
$ lsvg -p qa2vg
qa2vg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk30           active            399         0           00..00..00..00..00
hdisk31           active            399         0           00..00..00..00..00
hdisk32           active            399         0           00..00..00..00..00
hdisk33           active            399         0           00..00..00..00..00
hdisk34           active            399         0           00..00..00..00..00
hdisk35           active            399         0           00..00..00..00..00
hdisk36           active            399         0           00..00..00..00..00
hdisk37           active            399         0           00..00..00..00..00
hdisk38           active            399         0           00..00..00..00..00
hdisk39           active            399         0           00..00..00..00..00
hdisk40           active            399         0           00..00..00..00..00
hdisk41           active            399         0           00..00..00..00..00
hdisk42           active            399         0           00..00..00..00..00
hdisk43           active            399         0           00..00..00..00..00
hdisk44           active            399         0           00..00..00..00..00
hdisk45           active            399         0           00..00..00..00..00
hdisk46           active            399         0           00..00..00..00..00
hdisk47           active            399         0           00..00..00..00..00
hdisk48           active            399         0           00..00..00..00..00
hdisk49           active            399         0           00..00..00..00..00
hdisk50           active            399         0           00..00..00..00..00
hdisk51           active            399         0           00..00..00..00..00
hdisk52           active            399         0           00..00..00..00..00
hdisk53           active            399         0           00..00..00..00..00
hdisk54           active            399         0           00..00..00..00..00
hdisk55           active            399         0           00..00..00..00..00
hdisk56           active            399         0           00..00..00..00..00
hdisk57           active            399         0           00..00..00..00..00
hdisk58           active            399         0           00..00..00..00..00
hdisk59           active            399         0           00..00..00..00..00
hdisk60           active            399         0           00..00..00..00..00
hdisk61           active            399         0           00..00..00..00..00
hdisk64           active            199         70          00..00..00..30..40
hdisk65           active            199         71          00..00..00..31..40
hdisk66           active            199         70          00..00..00..30..40
hdisk67           active            199         71          00..00..00..31..40

2. Disk is allocated to SAN

3.
Code:
$ oslevel -s
5300-11-02-1007

Thanks!

Last edited by Scott; 02-10-2011 at 04:07 AM.. Reason: Please use code tags
# 5  
Old 02-10-2011
Ok with the AIX5.3ML11 (> ML8 is were you need to be)
you have 36096 megabytes (36GB) free in the vg to allocate without requiring the need to more disk.
you said you needed approximate 36GB to add so you are going to add it and it will go to these disk drives.

hdisk64 active 199 70 00..00..00..30..40
hdisk65 active 199 71 00..00..00..31..40
hdisk66 active 199 70 00..00..00..30..40
hdisk67 active 199 71 00..00..00..31..40

Since this is SAN disk I will assume that all the raid is handled by the back end. and you are not doing mirroring

with all that said we are going to let AIX find and place the required PP's as needed. But I do have 1 more question.
Why are the disk drives we are going to use only 199 PP's but all the others are 399 PP's.
The SAN should have allocated the same disk size to you for usage.
SO is this correct disk for the system?

Anyway you can do this in smit or
Code:
chfs -a size=+9G /sapdata5qa  (I am also assuming that this is the File System Mount and not the LV)

I would probably just round the 7.75 and the 7.50 GB's to 8.
But if you want the exact you will do the GB size the another for Meg size.

And like all things be sure you have a valid backup before you do this.
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question