/run/lock/ not created

[Daniel Richard G.]

This concerns mountall 2.31 in Ubuntu Oneiric.

When I run update-grub(8) in recovery mode, I see an error concerning /var/lock/lvm:

    # update-grub
    Generating grub.cfg ...
    Found linux image: /boot/vmlinuz-3.0.0-12-generic
    Found initrd image: /boot/initrd.img-3.0.0-12-generic
    Found memtest86+ image: /boot/memtest86+.bin
    File descriptor 13 (socket:[6182]) leaked on lvs invocation. Parent PID 2421: /bin/sh
      /var/lock/lvm: mkdir failed: No such file or directory
      File-based locking initialisation failed.
    Found Debian GNU/Linux (wheezy/sid) on /dev/sda6
    done

    # mkdir /run/lock

    # update-grub

    Generating grub.cfg ...
    Found linux image: /boot/vmlinuz-3.0.0-12-generic
    Found initrd image: /boot/initrd.img-3.0.0-12-generic
    Found memtest86+ image: /boot/memtest86+.bin
    File descriptor 13 (socket:[6182]) leaked on lvs invocation. Parent PID 3248: /bin/sh
      No volume groups found
    Found Debian GNU/Linux (wheezy/sid) on /dev/sda6
    done

/run/lock/ is present when the system is running normally, so I presume that something creates it along the way. Given that /var/lock now exists as a symlink to /run/lock, however, the latter should probably be created at the point that /run is mounted.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[martin suchanek (martin-suc)]

this happened to me after distr-upgrade to precise from oneiric but not on all distr-upgrade precise instances.