Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hi, I had hdisk1 mirroring hdisk

Status
Not open for further replies.

MoshiachNow

IS-IT--Management
Feb 6, 2002
1,851
IL
Hi,

I had hdisk1 mirroring hdisk0 in rootvg VG.
AFter exercising with mirroring stuff I'm left with hdisk1 without a volume groupe,but the system still remembers that rootvg VG was mirrored.
I can not make the system forget it - unmirror or reducevg does not work,thay fail due to some residues of hdisk1 written somwhere on hdisk0 (system disk).
What can be done without reloading the system from scratch ?


lspv
hdisk0 0056c8facc6857ed rootvg
hdisk1 0056c8faf5b5dd17 None


lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/stale N/A
hd6 paging 66 132 2 open/syncd N/A
hd8 jfslog 1 2 2 open/stale N/A
hd4 jfs 1 2 2 open/stale /
hd2 jfs 16 32 2 open/stale /usr
hd9var jfs 4 8 2 open/stale /var
hd3 jfs 1 2 2 open/stale /tmp
hd1 jfs 1 2 2 open/stale /home
scitexlv jfs 42 84 2 open/stale /scitex
scitemplv jfs 8 16 2 open/stale /scitex/version/temp
psfontslv jfs 4 8 2 open/stale /scitex/version/usr/local/es/psfonts
scimarkerslv jfs 4 8 2 open/stale /scitex/version/markers
scistoredblv jfs 1 2 2 open/stale /scitex/version/storedb
SharedItemslv jfs 4 8 2 open/stale /scitex/version/SharedItems
mngr_DBRoot jfs 8 16 2 open/stale N/A
backuplv jfs 13 26 2 open/stale /backup

unmirrorvg rootvg hdisk1
0516-320 getlvodm: Physical volume hdisk1 is not assigned to
a volume group.
0516-1135 unmirrorvg: The unmirror of the volume group failed.
The volume group is still partially or fully mirrored. "Long live king Moshiach !"
h
 
wab62 had a problem similar to this back in May. Have a look in the index for:
How to fix mirrored lvs when a drive is replaced?

HTH
Mark
 
It sounds as though the ODM has got confused , and the VGDA does not match the ODM ,

one thing you can do is try re-defining the physical volume
so you are telling the volume group that the disk hdisk1 belongs to the volume group rootvg

redefinevg -d hdisk1 rootvg
( try it with -d first then use the pvid it it fails )
( if successfull , then try unmirror , remove disk and re-mirror)


Also have a look at this page 10 putlvodm , i.e. puts an entry in the ODM for the rootvg for the disk hdisk1 , that it thinks is missing . If successful then unmirror it , replace disk etc.)


Also haev you tried to reduce the copy manually
rmlvcopy LVname 1 hdisk?
then remove disk from vol group reducevg
 
After your redefinevg, then do a synclvodm -Pv rootvg. Also, do a `chpv -c hdisk1` to clear any boot record that may exist on hdisk1.
 
Does it works ?
If not what does bring you the lsvg -p rootvg ?
If there is a PVID, with no hdisk assignet in the Output, do the following steps.
for each lv do:
rmlvcopy lvname 2 "PVID in lsvg -p rootvg"
Controll with lsvg -l rootvg PV=1 !
syncvg -v rootvg
synclvodm -v rootvg
extendvg rootvg hdisk1
mirrorvg rootvg hdisk1
lsvg -l rootvg PV=2

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top