My junior Deleted vdisk without removng LV

[chindi]

Hi Duncan,

I have 50 lun's presented to this system...

[Kapil Jha]

do you have lvol device file
if yes try to remove lv!!

if nothing is happening try to mount it back and umount
else try to forcefully umount it with vxumount

and then deactivate the vg and export it.

BR,
Kapil+

[Duncan Edmonstone · Accepted solution]

khapil jha...

it's cleanly unmounted - I'm guessing the junior forgot to run "vgchange -a n" before removing the vdisk...

chindi,

50 LUNs - that's a bummer... To be honest I'd be tempted to just leave it as it is until the next reboot... if you really want to fix it now:


1. Run vgdisplay -v on every VG to look at what the primary/alternate paths are to each LUN - you'll need to save this output somewhere to refer to later.

2. Now run the vgscan:

mv /etc/lvmtab /etc/lvmtab.old
vgscan -v

3. Now use vgdisplay -v to look at each VG in turn - you'll see all the primary/alternate paths have been switched around with everything now going down the same path.

4. Now _carefully_ use vgreduce/vgextend to remove the incorrect primary paths out & then back in to the VG - you'll see the next alternate path in the list becoming the new primary path... you are aiming to get the vgdisplay output to look like it did before...

That's a lot of work! I'd be tempted just to leave the whole thing until you can reboot - then you'll be able to remove the (now inactive) VG using vgexport as I originally indicated.

HTH

Duncan

[chindi]

Hi Duncan,

Thanx for the explaination, i think i will wait for the next reboot.....


Regards,
Chindi .