topic Re: problem with a logical volume in Operating System - HP-UX

problem with a logical volume

Alan Casey — Thu, 22 Jan 2004 07:12:49 GMT

I recently restored my rootvg from ignite tape, and in the process didn't restore one of the logical volumes, called monitor.
When I try and run make_recovery -A I get:

save_config: error - cannot determine lv "/dev/vg00/monitor" usage via fstyp

And if I try and remove the UNUSED logical volume I get:

image1(root)/opt/ignite/bin> lvremove /dev/vg00/monitor
lvremove: Couldn't delete logical volume "/dev/vg00/monitor":
The supplied lv number refers to a non-existent logical volume.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.con
f

Anyone know what I need to do to get rid of this lvol?

Re: problem with a logical volume

G. Vrijhoeven — Thu, 22 Jan 2004 07:15:15 GMT

Hi Alan,

Does a lvreduce -f -k do the job?

Gideon

Re: problem with a logical volume

Pete Randall — Thu, 22 Jan 2004 07:17:29 GMT

Alan,

Check with "strings /etc/lvmtab" to see if this lvol is still in your lvmtab. If it is, make a new lvmtab:

mv /etc/lvmtab /etc/lvmtab.bak
vgscan -a

Pete

Re: problem with a logical volume

Sunil Sharma_1 — Thu, 22 Jan 2004 08:03:46 GMT

Hi,

Check /etc/lvmconf/vg00.conf and see wheather monitor logical volume is there ?
please check /dev/vg00/ for device file of monitor logical voulme.

post the o/p of
#ll /dev/vg00

Sunil

Re: problem with a logical volume

T G Manikandan — Thu, 22 Jan 2004 08:08:05 GMT

first remove the device files of that lvol present in the /dev/vg00 VG.

That should take care,

Re: problem with a logical volume

Alan Casey — Thu, 22 Jan 2004 08:08:55 GMT

vgscan or lvreduce didn't work.

image1(root)/dev/vg00> ls -l *monitor*
brw-r----- 1 root sys 64 0x000010 Oct 29 11:12 monitor
crw-r----- 1 root sys 64 0x000010 Oct 29 11:12 rmonitor

Re: problem with a logical volume

Steven E. Protter — Thu, 22 Jan 2004 08:14:47 GMT

Note: make_recovery is obsolete, use make_tape_recovery

You might even get a better error message.

If /etc/lvmtab is valid, the script I'm attaching should tell you which physical volume is giving you trouble.

Ignite is now a pretty good tool for finding missing disks because it won't work when one is messed up or turned off.

You may need to deactivate the volume groupo, vgexport the volume group and import it back in.

Then activate it and see if the problem is fixed. Any issues that come up during this process will help you identify and correct the actual problem.

SEP