Linux – How to check what takes disk space in /tmp

At a command line, type

df -a

This will list each device and usage information.

You might find

df -h

more readable, since it gives quantities in Gb or Mb, etc.

You have a VZFS filesystem, which means that your VPS is a Parallels Virtuozzo virtual machine. In Virtuozzo the hosting provider can set limits on many parameters, including what allocations you get with VZFS.

Cause: Out of Inodes (Most Common)

After years of working with hundreds of Virtuozzo VPS customers who have had the issue of being unable to create files, even though there appeared to be plenty of free space, the vast majority of them had reached their inode limit. Run this command to see the inode allocation (Inodes), inodes used (IUsed), remaining inodes (IFree), and the percentage of inodes used (IUse%):

df -i

Having 100% inode usage happens a lot. Common causes in my experience:

• Spam email bouncebacks
• Outbound spam emails queued
• A lot of inbound emails stored
• Some user setting their PHP session garbage collection (session.gc_maxlifetime) to over a hundred years
• Way too many general cache files
• Object cache enabled in the WordPress plugin W3 Total Cache
• Magento error log (a new file is generated for every error)
• Other poorly configured or poorly designed programs/scripts that make a bunch of files and forget to delete them

Troubleshooting

If you find that you are low or out of inodes but don't know where most of the them are, I have this Bash one-liner that searches the current directory and counts the inodes in at a folder depth of 1:

for i in $(find $(pwd) -maxdepth 1 -type d | sort); do echo -e "$(find "$i" | wc -l)\t: $(readlink -f "$i")"; done | sort -nr

You can keep changing the current working directory starting from / until you find the culprit using up your inode allocation.

Explanation

Your VPS is on a VZFS filesystem, which is part of Parallels Virtuozzo (not OpenVZ, which is similar and based on the same technology, but OpenVZ wouldn't be using VZFS).

Due to the way Virtuozzo stores files in VZFS, inodes are often limited more so than they would be on other filesystems like ext4 or XFS. The host tracks all these files, and it would be advantageous to the hosting provider not to let a single VPS take up hundreds of millions of inodes. As a result, the hosting provider may set the inode limit to be low, like 1,000,000 inodes.

After years of working with hundreds of customers who exhausted their inode allocation on Virtuozzo, these "mysterious" disk quota issues don't surprise me anymore.

Cause: Other Virtuozzo Limits

A very small percentage of the Virtuozzo VPS customers I've worked with had filesystem issues because they hit other limits. You can see some (but not all) of the limits with this command:

cat /proc/user_beancounters

Troubleshooting

If the failcnt column has a value greater than 0 or a held column value is equal to the corresponding limit value, you have hit a limit.

You can look up what each parameter is on OpenVZ's wiki here. A parameter may be "primary", "secondary", or "auxiliary".

You should contact your hosting provider for further assistance if you find that you cannot decrease the held count for a limit that your VPS has reached.

This answer can be expanded a lot depending on which beans were maxed out, as different limits being reached cause different symptoms.

Cause: Limit(s) Decreased After Being Hit

Regarding /proc/user_beancounters or df -i, sometimes, a Virtuozzo system administrator may decrease the limit of a parameter below the held value.

For example, if the original limit of the diskinodes parameter was 1,500,000 and you hit the limit then someone at your hosting provider sets your inode limit to 1,000,000, you would see a bizarre inode report from df -i that makes no sense.

On your end, you could see an unreasonably large number, like 18,446,744,069,620,218,961.

I consider this to be a sinister behavior from the hosting provider, especially if they don't inform you, because the unusual values you see go against the knowledge of super users who don't have experience with Virtuozzo/OpenVZ, which leads to misleading advice (example, another example).

Troubleshooting

Contact your hosting provider. Show them what you found and work with them to get your held beans below the limit.

If they refuse to help you, ditch your hosting provider and find another one that doesn't use Virtuozzo/OpenVZ virtualization. KVM virtualization, VMware virtualization, Xen virtualization, or bare metal servers would be subject to far fewer limits than Virtuozzo/OpenVZ.

Explanation

Your hosting provider may have been auditing or responding to an alert and found that your VPS was using up too much of a specific resource (almost always the inodes limit, which is the diskinodes parameter on their end).

An inexperienced Virtuozzo admin at the hosting provider believes that they can cap the issue by reducing the limit to something lower than the actual resource usage. In the case of inodes, you may have a lower allocation, like 1,000,000, even though your actual current usage may be higher, like 1,500,000.

The Virtuozzo admin in their control panel would see your actual usage and the new limit, but you would see bogus numbers that are possibly very unreasonably high due to the way that Virtuozzo virtualizes.

A negligent Virtuozzo admin would not inform you of this change, which is why you should contact your hosting provider if this happens to you.