Fedora – /tmp directory size in Fedora

fedoratmpfs

I am using Fedora 26 and have some troubles with /tmp on tmpfs. By default Fedora sets the /tmp size to a half of RAM size. In my case it is 4/2=2GB. But I noticed this causes faults during some software updates which need to unzip large distribution files.

I have set the /tmp size to 4GB and it solves the problem but I am not sure that was the right strategy, because it is looking stupid to fulfill the unzip task in the single step using all the RAM available and crash when reaching the limit.

Best Answer

Issuing # mount -o remount,size=4G,noatime /tmp when you need to do large file operations, adjusting size to fit the task, is one of the correct strategies in your situation, along with being the simplest solution. It will revert to normal on next reboot.

More information, including how to make this permanent, can be found here: https://wiki.archlinux.org/index.php/Tmpfs

Related Solutions

Fedora 16 strange /tmp permissions: thesqld will not start

This was a bug with mysqld starting with systemd when they made a change to use ServicesPrivateTmp for additional security. When you performed a yum update, the mysql package was updated to mysql-5.5.22-1.fc16 or greater which corrected the issue.

Move /tmp to RAM

You don't have to do all that, you can just mount /tmp as tmpfs by using a line like the following in /etc/fstab:

tmpfs /tmp tmpfs mode=1777,nosuid,nodev 0 0

You can also do it live (but bear in mind stuff that is currently in /tmp on your current filesystem will not be able to be accessed except through the inode and currently open file descriptors, so you should really do this by modifying /etc/fstab and rebooting):

mount -o mode=1777,nosuid,nodev -t tmpfs tmpfs /tmp

Note that a tmpfs can swap. If you want a truly RAM-only filesystem, use ramfs.

Best Answer

Related Solutions

Fedora 16 strange /tmp permissions: thesqld will not start

Move /tmp to RAM

Related Question