Good spot, thanks: /var/lock is on /, not a symlink to /var/run. These machines are provisioned from OVH.com templates. I have raised a support request with them to see if they are aware of this or are doing anything strange on purpose.
-- $ cat /proc/self/mountinfo | fgrep lock 27 20 0:19 / /run/lock rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=5120k $ df -h /var/lock Filesystem Size Used Avail Use% Mounted on /dev/disk/by-uuid/56f53efc-[..] 20G 3.2G 15G 18% / $ ls -ld /var/lock drwxrwxrwt 2 root root 4096 Nov 12 10:42 /var/lock $ df -h /run/lock Filesystem Size Used Avail Use% Mounted on none 5.0M 0 5.0M 0% /run/lock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391452 Title: lxc-net fails to start properly after system crash: lock file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1391452/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
