Recently I started getting /tmp directory full error although it's not an individual partition.
root@ubuntu:~# df -h Filesystem Size Used Avail Use% Mounted on udev 7.9G 4.0K 7.9G 1% /dev tmpfs 1.6G 700K 1.6G 1% /run /dev/mapper/ubuntu--vg-root 38G 22G 14G 62% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 7.9G 0 7.9G 0% /run/shm none 100M 0 100M 0% /run/user **overflow 1.0M 1.0M 0 100% /tmp** /dev/sda1 236M 44M 180M 20% /boot
There were some files named "hsperfdata_elasticsearch", "hsperfdata_root" and "hsperfdata_logstash". I checked their size but it was zero.
root@ubuntu:~# du -sh /tmp/* 32K /tmp/hsperfdata_elasticsearch 0 /tmp/hsperfdata_logstash 0 /tmp/hsperfdata_root 0 /tmp/jna--1985354563 884K /tmp/mkinitramfs_jf2yUF 0 /tmp/mkinitramfs-OL_uoE6Jd
I did a graceful system reboot and the issue got fixed.
I know that hsperfdata files are generated by Java but are they kinda critical for ELK stack operations? Why would it cause /tmp to go into overflow state in df command output?