Yes, the /run partition is full because of systemd filling it up with 414MB
of files.

What is systemd process doing?!?! This box was absolutely fine before
I started upgrading, and now it is bricked. Grrrr. Hours of my life wasted.
Isn't this code tested before it is released? 

Here's what my box now looks like:

root@bb-linux64-1:/run/systemd# df
Filesystem                 Size  Used Avail Use% Mounted on
/dev/sda1                   60G   13G   44G  23% /
none                       4.1k     0  4.1k   0% /sys/fs/cgroup
udev                       2.1G  4.1k  2.1G   1% /dev
tmpfs                      415M  415M     0 100% /run
none                       5.3M     0  5.3M   0% /run/lock
none                       2.1G     0  2.1G   0% /run/shm
none                       105M     0  105M   0% /run/user

root@bb-linux64-1:/run# du -s systemd
414M    systemd

root@bb-linux64-gcc-snapshot-build-1:/run/systemd# du -s *
4.1k    seats
414M    sessions
4.1k    users
0       was-enabled

root@bb-linux64-1:/run/systemd# ls -1 sessions/* | wc -l
101070

root@bb-linux64-1:/run/systemd# dmesg -T | head -20
[Wed May  6 10:50:44 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:50:44 2015] systemd-logind[1653]: Failed to save session data 
for c323133: No space left on device
[Wed May  6 10:50:44 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Existing logind session ID 1 
used by new audit session, ignoring
[Wed May  6 10:50:54 2015] systemd-logind[1653]: New session c323134 of user 
buildbot.
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Failed to save session data 
for c323134: No space left on device
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Failed to save session data 
for c323134: No space left on device
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Failed to save session data 
for c323134: No space left on device
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:50:54 2015] systemd-logind[1653]: Failed to save session data 
for c323134: No space left on device
[Wed May  6 10:50:55 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:51:04 2015] systemd-logind[1653]: Existing logind session ID 1 
used by new audit session, ignoring
[Wed May  6 10:51:04 2015] systemd-logind[1653]: New session c323135 of user 
buildbot.
[Wed May  6 10:51:04 2015] systemd-logind[1653]: Failed to save session data 
for c323135: No space left on device
[Wed May  6 10:51:04 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:51:04 2015] systemd-logind[1653]: Failed to save session data 
for c323135: No space left on device
[Wed May  6 10:51:05 2015] systemd-logind[1653]: Failed to save session data 
for c323135: No space left on device
[Wed May  6 10:51:05 2015] systemd-logind[1653]: Failed to save user data for 
buildbot: No space left on device
[Wed May  6 10:51:05 2015] systemd-logind[1653]: Failed to save session data 
for c323135: No space left on device

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452227

Title:
  unpacking deb fails with I/O error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1452227/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to