FS#30515 - [lvm2] Uses /var/lock/lvm as default lock dir instead of /run/lock/lvm

Attached to Project: Arch Linux
Opened by Rémy Oudompheng (remyoudompheng) - Tuesday, 03 July 2012, 06:21 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 03 July 2012, 20:26 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Eric Belanger (Snowman)
Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
lvm2 uses /var/lock/lvm by default as its locking directory. /etc/lvm/lvm.conf specifies that the locking directory should not itself be on LVM. When /var is a separate LVM partition, the default setting is incorrect, and /var will not be mounted when lvm is invoked from initscripts.

The default directory should be /run/lock/lvm.

Additional info:
* lvm2 2.02.96-2
* Default config from package


Steps to reproduce:
* Have /var on a separate LVM partition
* observe at boot: "mkdir: /var/lock/lvm: no such file or directory
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 03 July 2012, 20:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  lvm2-2.02.96-3
Comment by Tom Gundersen (tomegun) - Tuesday, 03 July 2012, 11:59 GMT
I committed a fix in svn. I didn't push a new package to testing, but could do that too if the maintainers want me to.
Comment by Eric Belanger (Snowman) - Tuesday, 03 July 2012, 17:15 GMT
Tom: You can push a fixed package in testing. I assume here that you use lvm otherwise it might be better if I do it to make sure the fix didn't break anything.
Comment by Tom Gundersen (tomegun) - Tuesday, 03 July 2012, 17:21 GMT
I do use it, but I never noticed this bug in the first place, so if you could do it that would probably be best.

If you are busy, I can test and push tonight.
Comment by Eric Belanger (Snowman) - Tuesday, 03 July 2012, 17:35 GMT
I also never noticed this bug even though my /var is in a seperate lvm volume. Maybe it's because my root partition is also on a lvm volume in the same group. I'll push the fixed package this afternoon.

Loading...