AIX extend VG error


Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
Operating Systems AIX AIX extend VG error
# 8  
Quote:
Originally Posted by Phat
I copy here again. Note that below info is taken from another machine which has big VG and scalable VG.
Big VG it has 2 parameters: Max PPs per VG and Max PPs per PV
OK, now i understand what you mean - sorry, my bad.

Yes, big VGs have still a limitation of how many PPs can reside on a single PV AND they have a restriction of how many PVs can be in a VG, although these limits are higher than in a classic VG. The scalable VG only has one upper limit and that is the number of PPs overall, in the whole VG. There is no limit of how many PPs can be in a single PV any more. You can set the maximum number of PPs for the whole VG at the creation of the VG and my suggestion is to set it to the maximum possible of ~2 million PPs as i told you already.


Quote:
Originally Posted by Phat
Like you said, we can increase LUNs in size at storage by adding 1 or more disks to the LUN.
ahem, no. A "LUN" consists already of many disk snippets (that is done inside the storage box) but it is presented as a single homogenous disk device to the OS. You can make such LUNs bigger (at least with certain storage systems) and this will - to the OS - look like the hard disk it has attached just grew in size. You do not "add another disk" or something such. To make use of such a grown disk first run cfgmgr to make the OS aware of the new size, then run chvg -g to make the LVM aware.

Quote:
Originally Posted by Phat
I have 1 concern here, currently, the max PP of PV is limited at 2032 PPs x 128 MB = 260 GB. Because of this limitation, I cannot add the 1 TB PV whose PPs are greater than 2032 PPs.

If we grow the LUN in size example 500GB in total, it will breach the limits of 2032 PPs. Still acceptable from VG side?
This is why i told you to recreate the VG: a PP size of 128MB is just ridiculous. Do yourself a favour and when you recreate the VG select a PP size of 1GB or even 2GB. I mean, is there any chance you may want to change (increase or shrink) a filesystem on that VG in steps smaller than 1GB? Certainly not, i'd reckon. Therefore there is no reason to have such a small PP size at all.

Such a recreation of the VG (and the filesystems it contains) will give you the opportunity to rectify the filesystems too: if you still have JFS filesystems recreate them with JFS2, if you still use external log volumes change the new FSes to use inline logs.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
# 9  
Hi Bakunin,
Quote:
Yes, big VGs have still a limitation of how many PPs can reside on a single PV AND they have a restriction of how many PVs can be in a VG, although these limits are higher than in a classic VG. The scalable VG only has one upper limit and that is the number of PPs overall, in the whole VG. There is no limit of how many PPs can be in a single PV any more. You can set the maximum number of PPs for the whole VG at the creation of the VG and my suggestion is to set it to the maximum possible of ~2 million PPs as i told you already.
So we can convert it to scalable VG and then we can add the 1 TB disk later?

Regarding the PP size yes it's ridiculous, it was created by the ex-admin and now I inherited all the legacy Smilie
# 10  
Quote:
Originally Posted by Phat
So we can convert it to scalable VG and then we can add the 1 TB disk later?
NO!! Again, for the umpteenth time now: you SHOULD NOT - even if you can!! You should recreate the VG on as few as possible LUNs, create new filesystems, then restore the contents of the old filesystems to the new VG, then delete the old VG, then remount the FSes. If you add another "1TB disk later" you will then have 30 disks in the VG (instead of the already 29 that are in it). This is unmanageable in the long run (and even on short term). Instead of learning ways how to more effectively use a crutch you should consider learning how to walk.

Of course you can do whatever you want, but ask yourself: does it make sense to even ask if you are going to disregard what you are being told anyways?

I hope this helps.

bakunin
# 11  
Hi Bakunin,

Understand your recommendation. My aim is to know if we can go this way technically Smilie
For the current status, there is no need to add new disk to that VG, we just need to create new VG and that's all. The scalable VG with PP size 1 GB is created Smilie

I have 1 more point, can you explain to me the in-band and calculation of the percentage? In the docs it says this is used to calculate the usage percentage of disk, but somehow I can see 0%, 100% but the disk has data already on it and still has free PPs.

Code:
[root@xxx] / > lslv -l fslv03
fslv03:/export/images
PV                COPIES        IN BAND       DISTRIBUTION
hdisk19           1599:000:000  20%           320:320:319:320:320
hdisk20           1599:000:000  20%           320:320:319:320:320
hdisk21           1599:000:000  20%           320:320:319:320:320
hdisk22           1599:000:000  20%           320:320:319:320:320
hdisk23           1599:000:000  20%           320:320:319:320:320
hdisk24           1599:000:000  20%           320:320:319:320:320
hdisk25           1599:000:000  20%           320:320:319:320:320
hdisk26           1599:000:000  20%           320:320:319:320:320
hdisk17           968:000:000   18%           320:178:319:151:000

[root@xxx] / > lspv -l hdisk21
hdisk21:
LV NAME               LPs     PPs     DISTRIBUTION          MOUNT POINT
fslv03                1599    1599    320..320..319..320..320 /export/images

[root@xxx] / > lspv hdisk21
PHYSICAL VOLUME:    hdisk21                  VOLUME GROUP:     vg_3
PV IDENTIFIER:      00fa6d12ed215e81 VG IDENTIFIER     00c1cc1400004c0000000128174b7c57
PV STATE:           active
STALE PARTITIONS:   0                        ALLOCATABLE:      yes
PP SIZE:            64 megabyte(s)           LOGICAL VOLUMES:  1
TOTAL PPs:          1599 (102336 megabytes)  VG DESCRIPTORS:   1
FREE PPs:           0 (0 megabytes)          HOT SPARE:        no
USED PPs:           1599 (102336 megabytes)  MAX REQUEST:      256 kilobytes
FREE DISTRIBUTION:  00..00..00..00..00
USED DISTRIBUTION:  320..320..319..320..320
MIRROR POOL:        None

Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #620
Difficulty: Medium
Python implicitly assumes that each physical line corresponds to a logical line.
True or False?

10 More Discussions You Might Find Interesting

1. Red Hat

Is it possible to extend PV

Hello, I have redhat and centos systems that I've only been able to grow the VG by adding more disks. I've been searching the web for a way to extend a volume group by growing the physical disk only and not having to add a second disk. Is it possible? I can do this with AIX, by just... (0 Replies)
Discussion started by: bbbngowc
0 Replies

2. Linux

Unable to extend LV

Hi all. I have a Logical volume that I can't extend, with this error message: server171:root:/root# lvextend -L +1024M -v /dev/aplic_vg/siteminderwa_lv Finding volume group aplic_vg Archiving volume group "aplic_vg" metadata (seqno 75). Extending logical volume siteminderwa_lv to... (0 Replies)
Discussion started by: Gabriander
0 Replies

3. AIX

How to extend mirrored VG?

Hi all, I need to extend a lv, but unfortunately I do not have enough space on my mirrored Volume group. I've planned to add 2 more disks to this vg (for mirroring) But ... what's the next steps to extend my lv using these 2 disks with a valid mirroring ? 1. extendvg myvg disk1 disk2... (3 Replies)
Discussion started by: unclefab
3 Replies

4. Red Hat

Can't extend lv

Hi, I have recently increased the size of my pv and I am now attempting to increase the lv but I get the following error: # vgdisplay --- Volume group --- VG Name VolGroup00 System ID Format lvm2 Metadata Areas 1 Metadata... (7 Replies)
Discussion started by: Duffs22
7 Replies

5. Solaris

Filesystem - error when extend the filesystem

Hi all, currently , my root filesystem already reach 90 ++% I already add more cylinder in the root partition as below Part Tag Flag Cylinders Size Blocks 0 root wm 67 - 5086 38.46GB (5020/0/0) 80646300 1 swap wu 1 - ... (11 Replies)
Discussion started by: SmartAntz
11 Replies

6. Filesystems, Disks and Memory

How to extend a filesystem??

OK I'm sure this question has been posed far too many times. I have solaris 10 x86 with NO Veritas or Disksuite filesystems. Below is the output of df -k # df -k Filesystem kbytes used avail capacity Mounted on / 10485760 547513 9317128 6% / /dev... (1 Reply)
Discussion started by: jackiebaron
1 Replies

7. Solaris

How to extend a filesystem

I am running solaris 10 with Veritas. I want to extend a filesystem. It's an oracle partition (/ora12). How can I find out if there is space available to expand the filesystem and then how does one extend it. I'm from the HPUX world and so LVM was always how I did things. Thanks jackie (5 Replies)
Discussion started by: jackiebaron
5 Replies

8. AIX

Extend a Filesystem with other LV

Hi Everybody, Is it possible to extend a Filesystem by adding a new LV that exist on different VG to this Filesystem? Thanks in advance. (6 Replies)
Discussion started by: aldowsary
6 Replies

9. HP-UX

how to extend a vg on the same disk

on the disk array (EMC Clariion cx300): we added 3 disk and extended the LUN corresponding to HP-9000 (rp7410) on HP-UX 11.11: diskinfo /dev/rdsk/c10t0d0, show more disk space, but vgdisplay vg13 does not show more space So the problem is the disk had increased, but vgdisplay does not... (6 Replies)
Discussion started by: pedro_lezaeta
6 Replies

10. UNIX for Advanced & Expert Users

extend /usr on AIX

Hi! How to extend /usr partition in rootvg on AIX 4.3.3-09? I guess first I'll have to decrease the size of other partition(s) in rootvg? Thank you! (2 Replies)
Discussion started by: steve99
2 Replies

Featured Tech Videos