/tmp folder has reached maximum capacity on Solaris.
 

Hi Folks,

I am working on Oracle Solaris 10 8/11 s10x_u10wos_17b X86 box.

The /tmp folder has reached maximum capacity on Solaris.
Here is the output of df -h command :

bash-3.2# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t5000CCA022257BD0d0s0
7.9G 3.9G 4.0G 50% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 57G 1008K 57G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap1.so.1
7.9G 3.9G 4.0G 50% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
/dev/dsk/c0t5000CCA022257BD0d0s3
12G 87M 12G 1% /var
/dev/dsk/c0t5000CCA022257BD0d0s5
91M 91M 0K 100% /tmp
swap 57G 36K 57G 1% /var/run
/dev/dsk/c0t5000CCA022257BD0d0s4
249G 6.0G 241G 3% /gsn
bash-3.2#

The /dev/dsk/c0t5000CCA022257BD0d0s5 filesystem mounted on /tmp folder has reached its full capacity, so I am unable to run commands like 'ping', dhtadm or pntadm commands on Solaris system.

Is it possible to increase the filesize of /tmp folder?

Thank you for your help in advance.

It looks as if you have an actual disk providing /tmp rather than using memory.

You can increase the size (details depend on your disk layout) but it will be easier to remove some of the unwanted junk under /tmp and monitor the free space in future.

Hi linosaurusroot,

Thank you for your reply.
Can you please let me know how can I check the disk layout and determine whether some filespace from another filesystem can be used to increase the size on /tmp folder as a workaround?

Thank you.

Do you have unused disk (not allocated to a partition in use)? If so make a partition of a suitable size and make a filesystem on it. Copy what you want from /tmp/ into this new tmp and replace the old /tmp with the new one.

If you haven't got space like that you'd want to add disk or reduce the size of some existing partition.

Or if you had logical volumes rather than partitions the sizing is more flexible.

Or if you were using ZFS storage pools and had free space it should be easy to add some where you want it.
http://docs.oracle.com/cd/E19253-01/819-5461/index.html

You are using a 100 MB disk slice on SAN for /tmp storage. This is an unusual configuration.

By default, Solaris uses tmpfs as /tmp backend storage area. Tmpfs stores its data on virtual memory, which is much faster than disk as long as you have enough RAM available.

According to df output, there are 57 GB of virtual memory available which looks more than enough to accommodate your 100 MB+ /tmp data.

In any case, as /tmp is (or should be) ephemeral, if there are no critical services running on it, the simplest way to fix the issue is to reboot your machine.