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?
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
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. schroot/ union/underlay/ vivid-amd64- 5d4f7453- 9a95-4a6a- 9aee-9394923bf7 34... schroot/ union/underlay/ vivid-amd64- 5d4f7453- 9a95-4a6a- 9aee-9394923bf7 34: target is busy schroot- union-underlay- vivid\x2damd64\ x2d5d4f7453\ x2d9a95\ x2d4a6a\ x2d9aee\ x2d9394923bf734 .mount mount process exited, code=exited status=32 schroot/ union/underlay/ vivid-amd64- 5d4f7453- 9a95-4a6a- 9aee-9394923bf7 34. 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. schroot/ union/underlay/ vivid-amd64- 5d4f7453- 9a95-4a6a- 9aee-9394923bf7 34... schroot/ union/underlay/ vivid-amd64- 5d4f7453- 9a95-4a6a- 9aee-9394923bf7 34. schroot- union-underlay- vivid\x2damd64\ x2d5d4f7453\ x2d9a95\ x2d4a6a\ x2d9aee\ x2d9394923bf734 .mount entered failed state.
Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/
Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/
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-
Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/
Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-
Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/
Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/
Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-
looping constantly for the duration of any builds in sbuild.
Why is systemd trying to do this?
laney@vivid> apt-cache policy systemd sherwood/ ubuntu/ vivid/main amd64 Packages dpkg/status
systemd:
Installed: 219-7ubuntu1
Candidate: 219-7ubuntu1
Version table:
*** 219-7ubuntu1 0
500 http://
100 /var/lib/