topic Re: vgdisplay -v shows .... in Operating System - HP-UX

vgdisplay -v shows ....

f. halili — Tue, 21 Mar 2006 16:10:50 GMT

vgdisplay -v shows " Cannot lock "/etc/lvmconf//lvm_lock" still trying ..."

Any thoughts.

Thanks,
f. halili

Re: vgdisplay -v shows ....

A. Clay Stephenson — Tue, 21 Mar 2006 16:16:12 GMT

This file means that another LVM process is running.

The safest approach is to reboot. If you can gracefully kill any running LVM commands that might fix you. You could remove the file but that is generally less than wise because it could lead to corrupted data.

Re: vgdisplay -v shows ....

Carlos Roberto Schimidt — Tue, 21 Mar 2006 16:16:31 GMT

Him

If you run:

# fuser -u /etc/lvmconf/lvm_lock

Can you see any process?

If you can, try discover who lock the file

Re: vgdisplay -v shows ....

Kent Ostby — Tue, 21 Mar 2006 16:18:04 GMT

ps -ef | grep -e lvsync -e vgsync -e lvchange -e lvextend

It means one of two things. Either there is another process using that resource or you rebooted at some point in time in the past when you were doing something to that VG.

Best to reboot if you can, but also do:

ll /etc/lvmconf/lvm_lock

and see if it is before your current reboot (uptime). If it is then you can probably remove it and continue.

Re: vgdisplay -v shows ....

Sanjay_6 — Tue, 21 Mar 2006 16:20:19 GMT

Hi,

too may vg / lv (eg. vgdisplay / lvdisplay) commands already running on the system.

Your command will complete after a delay.

Do a "ps -ef" and grep for lv / vg commands.

Hope this helps.

regds

Re: vgdisplay -v shows ....

James R. Ferguson — Tue, 21 Mar 2006 16:23:38 GMT

Hi:

You may have another LVM process running. Seach the process table for other commands (e.g. 'pvcreate', 'vgcfgbackup', 'lvextend' etc).

If that is the case, and you can gracefully terminate the command, then this should solve your problem. Do *not* kill a 'pvmove'. This could leave a logical volume in an inconsistent state.

If these graceful measures don't resolve the problem a reboot may be required.

Regards!

...JRF...

Re: vgdisplay -v shows ....

Mark Greene_1 — Tue, 21 Mar 2006 16:45:48 GMT

Run fuser /etc/lvmconf/lvm_lock to get the process ID holding the lock. Alternatively run strings /etc/lvmconf/lvm_lock if the fuser doesn't return anything and the file size is greater than zero.

Then you can kill the process or talk to whomever else is running it.

mark

Re: vgdisplay -v shows ....

Joshua Scott — Tue, 21 Mar 2006 17:30:41 GMT

Hmm...

/etc/lvmconf//lvm_lock

I notice that there is 2 slashes here, is this a typo?

Just checking,
Josh

Re: vgdisplay -v shows ....

Sanjay_6 — Tue, 21 Mar 2006 17:36:44 GMT

Hi,

It is not a typo mistake

The error message had two "//" before lvm_lock

Hope this helps.

regds

Re: vgdisplay -v shows ....

f. halili — Wed, 22 Mar 2006 14:15:10 GMT

thanks!