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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mirrored disk removed incorrectly

Status
Not open for further replies.

normntwrk

MIS
Aug 12, 2002
336
US
IBM came in and removed hdisk0 which was mirrored with hdisk1 (rootvg) without breaking the mirror and reducing the vg and now i can't do anything with it. There are a couple of posts in here with the exact same situation but I tried what they did and it just fails. I can't reducevg rootvg , can't remove the mirrored LV's using the PVID....nothing seems to work
# lsvg -p rootvg
0516-304 : Unable to find device id 000b70dc5408433d in the Device
Configuration Database.
rootvg:
PV ID PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
000b70dc5408433d removed 542 253 109..99..00..00..45
hdisk1 active 542 252 108..99..00..00..45
#
 
I know this isn't very helpful, but surely IBM are responsible for fixing what they broke?

The internet - allowing those who don't know what they're talking about to have their say.
 
The customer has hardware but no software maintenance and the hardware guys say it's a software problem. IBM software won't hardly talk with the IBM hardware guys

Thanks
Norm
 
Well he's lying. IBM service representatives *should* know what procedure to follow when replacing a disk.

Have you tried the hi-level command unmirrorvg rootvg, perhaps it is smart enough to deal with a crummy situation like this.

If not, then one by one for each mirrored LV:

[tt]rmlvcopy lvname 1 hdisk1[/tt]


HTH,

p5wizard
 
Tried all of that and more, just get errors

It's running fine off hdisk1 but it certainly isn't right.

I've got it to this point but it isn't really mirrored
fort44p2# lsvg -p rootvg
0516-304 : Unable to find device id 000b70dc5408433d in the Device
Configuration Database.
rootvg:
PV ID PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
000b70dc5408433d removed 542 253 109..99..00..00..45
hdisk1 active 542 252 108..99..00..00..45
hdisk0 active 542 542 109..108..108..108..
109


Thanks
 
[tt]reducevg -d rootvg 000b70dc5408433d[/tt]

HTH,

p5wizard
 
# reducevg -d rootvg 000b70dc5408433d
0516-914 rmlv: Warning, all data belonging to logical volume
loglv00 on physical volume 000b70dc5408433d will be destroyed.
rmlv: Do you wish to continue? y(es) n(o)? y
0516-1008 rmlv: Logical volume loglv00 must be closed. If the logical
volume contains a filesystem, the umount command will close
the LV device.
0516-884 reducevg: Unable to remove physical volume 000b70dc5408433d.
#
 
It's the same procedure you'd use if the disk had, had a total failure.

You'll have to do an odmdelete. See


For good walk through.

Like P5 I don't really believe IBM would make that mistake....

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."
 
So you have an LV on that removed drive that wasn't mirrored?

show lsvg -l rootvg please?

HTH,

p5wizard
 
# lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 8 16 2 open/stale N/A
hd8 jfslog 1 2 2 open/stale N/A
hd4 jfs 1 2 2 open/stale /
hd2 jfs 33 66 2 open/stale /usr
hd9var jfs 1 2 2 open/stale /var
hd3 jfs 1 2 2 open/stale /tmp
hd1 jfs 1 2 2 open/stale /home
hd10opt jfs 2 4 2 open/stale /opt
loglv00 jfs2log 1 2 2 open/stale N/A
fslv00 jfs2 240 480 2 open/stale /work
#
 
very odd
# lslv -l hd5
hd5:N/A
PV COPIES IN BAND DISTRIBUTION
hdisk1 001:000:000 100% 001:000:000:000:000
hdisk0 001:000:000 100% 001:000:000:000:000

# lslv -l hd6
0516-304 : Unable to find device id 000b70dc5408433d in the Device
Configuration Database.
hd6:N/A
PVID COPIES IN BAND DISTRIBUTION
000b70dc5408433d 008:000:000 100% 000:008:000:000:000
hdisk1 008:000:000 100% 000:008:000:000:000
 
tried this
# rmlvcopy hd6 1 000b70dc5408433d
0516-304 : Unable to find device id 000b70dc5408433d in the Device
Configuration Database.
0516-922 rmlvcopy: Unable to remove logical partition copies from
logical volume hd6.
 
reducevg should take care of that one, but it is complaining about loglv00 and failing before it gets to hd6.

lslv -m loglv00 ?

HTH,

p5wizard
 
reducevg fails

# lslv -m loglv00
0516-304 : Unable to find device id 000b70dc5408433d in the Device
Configuration Database.
loglv00:N/A
LP PP1 PVID1 PP2 PVID2 PP3 PVID3
0001 0118 000b70dc5408433d 0118 hdisk1
 
perhaps

rmlvcopy loglv00 1 000b70dc5408433d



HTH,

p5wizard
 
very frustrating

# rmlvcopy loglv00 1 000b70dc5408433d
0516-304 : Unable to find device id 000b70dc5408433d in the Device
Configuration Database.
0516-922 rmlvcopy: Unable to remove logical partition copies from
logical volume loglv00.
 
If I put the PVID back in the ODM I get this with a lspv on the PVID
# lspv -l 000b70dc5408433d
pvid=000b70dc5408433d:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
loglv00 1 1 01..00..00..00..00 N/A
fslv00 240 240 109..108..23..00..00 /work
hd9var 1 1 01..00..00..00..00 /var
hd2 33 33 33..00..00..00..00 /usr
hd4 1 1 01..00..00..00..00 /
hd8 1 1 01..00..00..00..00 N/A
hd6 8 8 08..00..00..00..00 N/A
hd10opt 2 2 02..00..00..00..00 /opt
hd1 1 1 01..00..00..00..00 /home
hd3 1 1 01..00..00..00..00 /tmp

Take it out of the ODM I get this
# lspv -l 000b70dc5408433d
0516-304 : Unable to find device id 000b70dc5408433d0000000000000000 in the Dev
ce
Configuration Database.
#
 
try the reducevg after you put the PVID back in the ODM?

HTH,

p5wizard
 
Tried that, I'm about ready to tell them to flatten it and start over
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top