vgdisplay -v shows ....

[f. halili]

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

Any thoughts.

Thanks,
f. halili

[A. Clay Stephenson · Accepted solution]

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.

[Carlos Roberto Schimidt]

Him

If you run:

# fuser -u /etc/lvmconf/lvm_lock

Can you see any process?

If you can, try discover who lock the file

[Kent Ostby]

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.

[Sanjay_6]

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

[James R. Ferguson]

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...

[Mark Greene_1]

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

[Joshua Scott]

Hmm...

/etc/lvmconf//lvm_lock

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

Just checking,
Josh

[Sanjay_6]

Hi,

It is not a typo mistake

The error message had two "//" before lvm_lock

Hope this helps.

regds

[f. halili]

thanks!