** Description changed: I recently hit ENOSPC which turned out to be the result of various syslogs from the current and previous boots totalling up to 30G. They were filled with messages like Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734: target is busy Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about processes that Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or fuser(1).) Apr 15 11:22:35 vivid systemd[1]: var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount mount process exited, code=exited status=32 Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount entered failed state. looping constantly for the duration of any builds in sbuild. Why is systemd trying to do this? + SRU TEST CASE: + -------------- + - Create a vivid container, and set "lxc.aa_profile = unconfined" and "lxc.mount.auto = sys:rw cgroup" in its config. (Note that the latter is not supported!) + - Start the container + - Run "mount -v -o bind /bin /mnt" + - Observe that it doesn't stay mounted, but "sudo journalctl" says + + Mai 06 09:17:08 test systemd[1]: Unit mnt.mount is bound to inactive unit dev-sda3.device. Stopping, too. + Mai 06 09:17:08 test systemd[1]: Unmounting /mnt... + Mai 06 09:17:08 test systemd[1]: Unmounted /mnt. + + - With the fixed package bind mounts stay mounted. + + REGRESSION POTENTIAL: This could potentially break cleanup of stale + mount points of either hotplug devices which disappear, or media which + get forcefully ejected (like CDs). Testing should include that these + still work. + laney@vivid> apt-cache policy systemd systemd: - Installed: 219-7ubuntu1 - Candidate: 219-7ubuntu1 - Version table: - *** 219-7ubuntu1 0 - 500 http://sherwood/ubuntu/ vivid/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 219-7ubuntu1 + Candidate: 219-7ubuntu1 + Version table: + *** 219-7ubuntu1 0 + 500 http://sherwood/ubuntu/ vivid/main amd64 Packages + 100 /var/lib/dpkg/status
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444402 Title: LXC with r/w sys and udev keeps trying to unmount bind mounts To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1444402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
