vgreduce

[Mark Mitchell]

If you have 2 disks in the root VG, 1 is a 1 gig and the other is a 2 gig. Can you vgreduce the 1 gig drive out without causing damage to the VG

[Rita C Workman]

Well alot more would need to be answered here...
First the 1 gb...is it the boot disk? Was this 1gb just an addon that was not really allocated out for anything?
Is this 1gb being used by root / now? and for what?

If this was just a disk that got added on to vg00, but not used for anything...than yes. But ... before doing anything you need to check on what this disk is/was doing????

Just a thought to get you started,
/rcw

[MARTINACHE]

Hi,

This will corrupt your vg but be sure that the 2GB disk is bootable ...

And perharps modify the primary boot device during the next reboot ...

Regards,

Patrice.

[Joseph C. Denman]

I agree with Rita, there are several unanswered questions. One point though...

Before doing anything with this vg, I would surely create an ignite tape!!!!!!!!!!

[Pedro Sousa]

Along with Rita too...
do you have all the information of vg00 on that disk of 2gb?
do "lvlnboot -v" to check configurations and "setboot".

[Cherie Galloway]

do a pvdisplay -v on the disk you want to remove to find out what file system are on it. Make sure there are no physical extents that are in use and which logical volumes are using it. If it is being used you need to move them first.

[Bruce Regittko_1 · Accepted solution]

Hi,

First, determine if the 1GB drive is the boot drive or if it has the dump and/or primary swap with

lvlnboot -v

If so, then let us know since it will take more work.

If the one GB disk passes the above test, you will have to move its data to the two GB disk. First though, see if there is enough space. Issue pvdisplay commands for each disk and see if the "Free PE" on the 2GB equals or exceeds the "Allocated PE" on the 1GB drive. If there is not enough room you will have to reduce the size of your logical volumes to accomodate.

To move the data, use the pvmove command. The syntax is

pvmove /dev/dsk/<1GB drive> /dev/dsk/<2GB drive>

Verify the move with pvdisplay. If the 1GB drive has 0 allocated extents, then use vgreduce on it.

--Bruce

[Mark Mitchell]

lots of good stuff here, let me give it a whirl and I'll be back with points and what
the outcome looks like.

[Mark Mitchell]

Well after using you instruction to see what was on each disk, I found out that I can't get it onto the 2 gig disk because the swap space put the numbers over the top. Looks like I will be getting some new disks. Sure that HP will be happy to hear it. Thanks everyone.

[Rita C Workman]

Mark,

Just a little tip here....when a box is ignited lvol2 is created, thus allowing for dumps in the event of a system panic. lvol2 also provides minimal device swap.
Any additional swap, which is what your other disk may have been used for, should never be put back onto the main boot disk. You always want to add additional device swap to a seperate disk. Otherwise, you defeat the whole purpose of device swap.

Just a thought,
/rcw

[Mark Mitchell]

The goal here is to have a self-contained disk that can boot in case of a seperate failure and a mirror copy incase that device fails.

[Pedro Sousa]

I think You'll need to use Mirror/UX.
You want to have redundancy on bootable devices, is that correct?

[Mark Mitchell]

correct

[Mark Mitchell]

Didn't quite hit the question, but useful to some. I however like to enter
mkboot -a "hpux -lq" /dev/dsk/c0t0d0
to make sure that its set up to boot without quorum. Then the lifcp /dev/dsk/c0t0d0:AUTO -
to check. A very important step, without that a mirror does you no good without interupting a boot to get it going again.