12

On Ubuntu Precise, I'm low on space in /run:

admin@foo:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        19G  6.6G   12G  38% /
udev             10M  8.0K   10M   1% /dev
none             50M   40M   11M  79% /run
none            5.0M     0  5.0M   0% /run/lock
none            249M     0  249M   0% /run/shm

Should I allocate more? How?

EDIT: Here's my fstab:

admin@foo:~$ cat /etc/fstab
proc            /proc       proc    defaults    0 0
/dev/sda1       /           ext3    defaults,errors=remount-ro,noatime    0 1
/dev/sda2       none        swap    sw          0 0
lgarzo
  • 272
Brian
  • 797

5 Answers5

15

In a post on Ask Ubuntu, korrident suggested a possible workaround:

Adding a mount command to the /etc/rc.local file:

mount -t tmpfs tmpfs /run -o remount,size=85M

Make sure that the script will "exit 0" on success or any other value on error. (Excerpt from the file.)

Community
  • 1
lgarzo
  • 272
4

I do not think that increasing the size of /run is necessary, but in case you do need to increase it try editing your /etc/fstab file. All mountpoints and most partitions are listed there. If your /run partition is a tmpfs(which it should be, at least according to https://askubuntu.com/questions/57297/why-has-var-run-been-migrated-to-run, I would confirm before following these instructions) then you can simply change the fstab line of your /run mount to something akin to the following:

none /dev/shm tmpfs defaults,size=8G 0 0

See how the size is declared right after defaults? Try doing that. You can use megabytes as well by using M:

none /dev/shm tmpfs defaults,size=100M 0 0

Reboot the computer after this and the changes should take place.

Edit: Scratch that, looks like Ubuntu creates the run partition using files in /etc/init and /etc/init.d and not via fstab. You'd have to look through those files and find the mount command that it uses to create run and edit it manually. I don't have a box to test this on right now, but try running this:

find /etc/init* -type f | xargs grep "mount"

OR

find /etc/init* -type f | xargs grep "run"

If it's being mounted via a bash script then this should find the file and line that does the mounting.

Community
  • 1
Marcos Velazquez
  • 441
2

Temporary increase tmpfs filesystem

1) Open /etc/fstab with vi or any text editor of your choice,

2) Locate the line of /dev/shm and use the tmpfs size option to specify your expected size,

e.g. 512MB:
tmpfs      /dev/shm      tmpfs   defaults,size=512m   0   0

e.g. 2GB:
tmpfs      /dev/shm      tmpfs   defaults,size=2g   0   0

after then

mount -o remount /dev/shm
stambata
  • 1,734
Mansur Ul Hasan
  • 272
0

I had this error due to journald.conf misconfiguration where I had used Storage=volatile and RuntimeMaxUse=1G, where /run was only 200M in size. /run partition is an in-memory partition. Storage=volatile tells journald to store logs in-memory in /run/log/journal, and with RuntimeMaxUse=1G we get easy >200M logs overflow.

The options prefixed with "System" apply to the journal files when stored on a persistent file system, more specifically /var/log/journal. The options prefixed with "Runtime" apply to the journal files when stored on a volatile in-memory file system, more specifically /run/log/journal.

-- From journald.conf documentaion

Solution for me was to configure journald.conf with:

[Journal]
Storage=persistent
RuntimeMaxUse=50M
SystemMaxUse=1G

More details:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           199M  199M    0M 100% /run

$ du -sh /run/log/journal
199.0M  /run/log/journal


$ cat /etc/systemd/journald.conf


[Journal]
Storage=volatile
RuntimeMaxUse=1G
Jan Święcki
  • 101
0

This doesn't strictly answer the question as asked because this feature wasn't in Ubuntu 12.04, but in case it helps people with similar questions, as of Debian buster or Ubuntu 18.10 you can use the initramfs.runsize= boot parameter; the default is initramfs.runsize=10%, but you might use e.g. initramfs.runsize=20% or initramfs.runsize=128M instead.

This feature was added in response to Debian bug #862013.

Colin Watson
  • 1