I am getting the "No space left on device" error for pretty much anything i try to do. Even using tab to autocomplete a command!
but when i do df -h i get:
ubuntu@ip-10-0-2-108:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda1 99G 6.5G 88G 7% / udev 3.7G 8.0K 3.7G 1% /dev tmpfs 1.5G 184K 1.5G 1% /run none 5.0M 0 5.0M 0% /run/lock none 3.7G 0 3.7G 0% /run/shm none 100M 0 100M 0% /run/user /dev/xvdb 414G 199M 393G 1% /mnt overflow 1.0M 1.0M 0 100% /tmp
which to me looks like there is tons of space. df -i also looks similar:
ubuntu@ip-10-0-2-108:~$ df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/xvda1 6553600 94227 6459373 2% / udev 951353 393 950960 1% /dev tmpfs 953649 274 953375 1% /run none 953649 3 953646 1% /run/lock none 953649 1 953648 1% /run/shm none 953649 1 953648 1% /run/user /dev/xvdb 27525120 11 27525109 1% /mnt overflow 953649 12 953637 1% /tmp
I am on an Amazon EC2 ubuntu 12.04 instance.
Here are some examples of the error popping up:
ubuntu@ip-10-0-2-108:~$ sudo crontab -e /tmp/crontab.RvYjrR/crontab: No space left on device ubuntu@ip-10-0-2-108:~$ ls /va (hit tab for autocomplete) -bash: cannot create temp file for here-document: No space left on device -bash: cannot create temp file for here-document: No space left on device
however the server seems to be running and everything seems to be working. what on earth is going on??
Such difference between the output of du -sh and df -h may happen if some large file has been deleted, but is still opened by some process. Check with the command lsof | grep deleted to see which processes have opened descriptors to deleted files. You can restart the process and the space will be freed.
No space left on device Print No space left on device error often means you are over quota in the directory you're trying to create or move files to. 1. If you are trying to move a file from another location, change the group ownership of the file before moving it or use the copy command instead.
Open the System Monitor application from the Activities overview. Select the File Systems tab to view the system's partitions and disk space usage. The information is displayed according to Total, Free, Available and Used.
Your local folder does not have enough space available for the operation. In your environment, update the 'TEMP', 'TMPDIR' or 'TMP' environment variable to a location with additional free space. Validate the updated location: Windows - command-prompt 'set'
It's possible that you've run out of memory or some space elsewhere and it prompted the system to mount an overflow filesystem, and for whatever reason, it's not going away.
Try unmounting the overflow partition:
umount /tmp
or
umount overflow
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With