Operating System - HP-UX
1833390 Members
3047 Online
110052 Solutions
New Discussion

problem with a logical volume

 
SOLVED
Go to solution
Alan Casey
Trusted Contributor

problem with a logical volume

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?
6 REPLIES 6
G. Vrijhoeven
Honored Contributor

Re: problem with a logical volume

Hi Alan,

Does a lvreduce -f -k do the job?

Gideon
Pete Randall
Outstanding Contributor

Re: problem with a logical volume

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

Pete
Sunil Sharma_1
Honored Contributor

Re: problem with a logical volume

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
*** Dream as if you'll live forever. Live as if you'll die today ***
T G Manikandan
Honored Contributor

Re: problem with a logical volume

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

That should take care,

Alan Casey
Trusted Contributor

Re: problem with a logical volume

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

Steven E. Protter
Exalted Contributor
Solution

Re: problem with a logical volume

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
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com