Very Computer

Hi,

Can anyone point out how I can overcome this problem?  I've recently installed an additional 2.2GB disk in my RS/6000 C10, and I wanted it to be included in the rootvg volume group.  I followed through the SMIT screen to add this disk to rootvg (the fast path is "extendvg rootvg hdisk1" where hdisk1 is my new disk.  By the way, volume group rootvg has currently 1 PV of size 2 GB.  However, the command was not performed successfully and the error message that was displayed is:  

0516-050 linstallpv: Not enough descriptor area space left in this volume group.  Either try adding a smaller PV or use another volume group.
0516-628 extendvg: Warning, cannot install PV hdisk1 in VG rootvg.

I think I need to increase the VGDA (volume group descriptor area) size somehow.  But how?  Any advice is greatly appreciated.

Thanks!
Jayne Peter-Jaua
Brunei

the only way is to make a mksysb tape and reinstall AIX from this tape using both disks.

Klaus

--
This is my personal opinion. I'm not speaking
for my company.

To reply, please remove the NOSPAM from the address.

Quote:>Hi,

>the only way is to make a mksysb tape and reinstall AIX from this tape
using both disks.

>Klaus

>--
>This is my personal opinion. I'm not speaking
>for my company.

>To reply, please remove the NOSPAM from the address.

|> If he makes a mksysb tape which writes a raw image to 2 tapes, how will
|> restoring this enable him to add another hdisk which was not there before?
|> I thought mksysb image is block by block write retaining all physical info,
|> and not flexible as in the case of a filesystem restore

|>

|> >Hi,
|> >
|> >the only way is to make a mksysb tape and reinstall AIX from this tape
|> using both disks.
|> >
|> >Klaus

No, you misunderstand the capabilities of mksysb.  There is one
option to mksysb that says to do an exact disk block mapping.
That does NOT mean that the raw data partitions are written to disk;
it means that the logical volumes, which the jfs filesystem sits on
top of, will be recreated in the same locations as they were previously.
How the data lays within those recreated locations is another matter.

Doing a mksysb and restoration with the new disk added is the
best way to add the new disk in this case.

--
-----------------------------------------------------------
The views expressed are my own.  They do not represent IBM.

Later

Andrew Sinclair-Hall
AIX Systems Administrator

One thing that catches people is that if they originally had AIX 3.2, and
then did a "migration" or "preservation" upgrade, they are stuck with the
AIX 3.2 limits for rootvg.

Reinstalling from a mksysb will fix this problem.  If still using 3.2, then
you need to specify both disks at restore time in order to add them to
rootvg.

However, unless necessary, I would recommend against having multiple drives
in rootvg (unless for mirroring).  This is because a mksysb will backup
everything in rootvg, and means mksysbs will take a long time.  Also, it
limits system flexibility because you can't export your data to a new system.

Cheers, Andreas

--
Andreas Dilger   University of Calgary  \"If a man ate a pound of pasta and
                 Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \   cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/       hungry?" -- Dogbert