Cur PV

[Mike_21]

I am still getting some references to a bad disk that I am trying to remove from mirrored vg00. There is still a reference when I do a vgdisplay.

Cur PV 2

However, the size of the vg00 is still showing only the single 9G drive. There was originally 2 9G drives making up vg00! Can I get rid of all relations to this drive?

Thanks

[Mike_21]

Well I did the following that seemed to correct the problem!

vgreduce -f vg00
PV with key 1 sucessfully deleted from vg vg00
Repair done, please do the following steps.....:
1. save /etc/lvmtab to another file
2. remove /etc/lvmtab
3. use vgscan(1m) -v to re-create /etc/lvmtab
4. NOW use vgcfgbackup(1m) to save the LVM setup

[Abel Berger]

Hi Mike,

VG00 is a system vg.
First you have remove the copyes from the bad disk, after this, you have use a reducevg and later you change it and return the mirror or
return a makerecory tape.

I hope help you.
Regards
Abel Berger

[Carsten Krege]

Mike, you took the correct step by using "vgreduce -f". You experienced most likely this situation since one disk has not been properly removed from the VG with the "vgreduce /dev/vg00 /dev/dsk/" command.

In this case the LVM header of the other disk will still have information about the disk. This reference to the missing disk can only removed by using "vgreduce -f".

Please note that nowadays it is not always possible to temporary (re)move the lvmtab file without causing problems (e.g. the EMS monitor diskmond - if configured - relies on the existence of this file). It is recommended to have a quiet system prior to lvmtab being moved.

Carsten

[Vincenzo Restuccia]

# Shutdown your system and replace the disk that is failing.

Boot into single user mode and override the quorum, as:

# ISL> hpux -is -lq /stand/vmunix

# vgcfgrestore -n /dev/vg00 /dev/rdsk/cXtYdZ

# mkboot /dev/rdsk/cXtYdZ

# mkboot -a "hpux -lq /stand/vmunix" /dev/rdsk/CXtYdZ

# lvlnboot -Rv

# vgchange -a y /dev/vg00

# vgsync /dev/vg00

# shutdown -ry 0