Background:

I've got my /var directory set up as an LVM2 logical volume. During system boot, the lvm lock file in /var/lock/ gets nuked when the logical volume gets mounted on the /var mountpoint, LVM has a fit about this and refuses to mount any logical volumes.

My solution:

I edited /etc/lvm/lvm.conf to use locking type 2 (external shared library locking_library) rather than the default file-based locking.

It seems to be working OK for me, but I wonder if anyone out there can foresee that this would cause a problem.

Note:

Yes, I know that /var as a logical volume does screw me a bit with not being able to have boot logs under /var, but I really do need for /var to be on a logical volume.

${BADWORD}, my above solution didn't quite work out like I thought.

So, I edited /etc/lvm/lvm.conf again and reverted back to using file-based locking, and for the time being I am having the LVM lockfile live under /lock/lvm
I'd rather not throw additional junk directly under / but I don't think that it would be such a good idea to place the lvm lockfile under /etc, either.

Can anyone give me some brief arguments against having the LVM lockfiles under / and /etc ?