/tmp running out of inodes

[Dan Nelson]

In the last episode (Dec 18), Tankko said:
> For the second time in 2 weeks my server has gone down due to running
> out of inodes in /tmp.  The first time it did this /tmp was filled
> with files, so that made sense.  I delete all the files from /tmp and
> all was well for a few weeks.  Just this morning it did it again
> (keep in mind that this sever is currently 700 miles away) and had to
> be rebooted.
> 
> But when I looked at /tmp, it was empty except for a couple of files,
> but running df shows the follow:
> 
> Filesystem     Size    Used   Avail Capacity iused    ifree %iused  Mounted on
> /dev/ad4s1a    496M     59M    398M    13%    1535    64255    2%   /
> devfs          1.0K    1.0K      0B   100%       0        0  100%   /dev
> /dev/ad4s1e    496M     69M    387M    15%   65790        0  100%   /tmp
> /dev/ad4s1f    221G    5.2G    198G     3%  337742 29596848    1%   /usr
> /dev/ad4s1d    1.9G    757M    1.0G    42%    1632   280990    1%   /var
> /dev/md0        19M     12K     18M     0%       9     2805    0%   /tmp
> /dev/ad5s1c    289G     49G    217G    18%   27779 39115643    0%   /bigdrive

You seem to have two filesystems mounted on /tmp at the moment, which
could be affecting your ability to see files in the one that got
overlayed.

-- 
	Dan Nelson
	dnelson at allantgroup.com