Question

Cannot find what is filling up disk space /dev/vda1 is 100% full

  • Posted August 14, 2014

Here is what I have:

df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        40G   38G     0 100% /

However, I cannot find what is using the space up with du -sh *

Any ideas how to find what is using up all that space?

Subscribe
Share

@mslinn thanks it really worked for me and let me find which is using up my space till now. in my case it was “./Trash-0000”

This is better:

sudo du -h --max-depth=1 -x

This is better:

sudo du -h --max-depth=1 -x

This is better:

sudo du -h --max-depth=1 -x

This is better:

sudo du -h --max-depth=1 -x

In response to

“And do du -h [dir] for each of them”

du -h --max-depth=1 will achieve this much quicker without having go into each folder. look for the once that looks suspicious then perform the same max depth in that folder.

@josualeonard Hello, I ve sent a request as well to them, and similar to fix it your self with those links …

I don’t think I have as much knowledge as you do, can you explain to me in a bit more detail how to solve this ?

Problem is the same :

Filesystem Size Used Avail Use% Mounted on /dev/vda1 30G 28G 0 100% /

I am not quite sure what you mean by cd / ect… ect… It was all working fine until yesterday. Thanks for your help !!

After sending a support ticket about this issue, they point me to a direction of solving it myself.

For me there’s actually a log file that stacked up until the disk is full. Here’s how I solve it: I go to root dir: cd / list dirs and files: ls And do du -h [dir] for each of them When you see something suspicious you go inside that dir, or see from the du result. For me it’s a du -h home When I trace, it points me to my laravel app storage/logs.

On a sidenote, on my issue here is caused by job queue php artisan. And on those job queue there’s an error and it keeps logging and repeating, the php process also hogging the cpu. This solved me two issues altogether.

There you go. I hope it helps.

After sending a support ticket about this issue, they point me to a direction of solving it myself.

For me there’s actually a log file that stacked up until the disk is full. Here’s how I solve it: I go to root dir: cd / list dirs and files: ls And do du -h [dir] for each of them When you see something suspicious you go inside that dir, or see from the du result. For me it’s a du -h home When I trace, it points me to my laravel app storage/logs.

On a sidenote, on my issue here is caused by job queue php artisan. And on those job queue there’s an error and it keeps logging and repeating, the php process also hogging the cpu. This solved me two issues altogether.

There you go. I hope it helps.

Same issue here!


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

outside of other answers here what I did was:

navigate through subfolders with ncdu and finding large folders. Among them one can delete:

/var/logs https://bbs.archlinux.org/viewtopic.php?id=158510 // /var/logs/journal http://askubuntu.com/questions/100004/how-can-i-free-space-from-a-massive-39-5gb-var-log-folder // other already archived (GZ-ipped) files;

and compress .git folders of projects by shrinking them with this command: git repack -a -d --depth=250 --window=250 http://stackoverflow.com/questions/5613345/how-to-shrink-the-git-folder

outside of other answers here what I did was:

navigate through subfolders with ncdu and finding large folders. Among them one can delete:

/var/logs https://bbs.archlinux.org/viewtopic.php?id=158510 // /var/logs/journal http://askubuntu.com/questions/100004/how-can-i-free-space-from-a-massive-39-5gb-var-log-folder // other already archived (GZ-ipped) files;

and compress .git folders of projects by shrinking them with this command: git repack -a -d --depth=250 --window=250 http://stackoverflow.com/questions/5613345/how-to-shrink-the-git-folder

Googled and found this question which had the same problem.

@TonyTsang That command helped me find what it was

Apparently it was a hidden log folder set by pm2.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.

Another option that might help you find out what is using up space is ncdu Install it with:

sudo apt-get install ncdu

If you still can’t find anything, try running:

lsof / | grep deleted

Sometimes if a file is deleted while it is opened by a process, it will not actually free up the disk space until the process is ended. This command will show if there are any files in that state.