Hi @BreizhoO
I thought it wasn’t related to my code, I thought it might be a server problem that create new partition. Apparently I’m wrong, that /dv/vda1 / is the main partition, only this time filled with some huge files, the log files.
First, stop any queue or running cron job as it might be the cause your log files is full.
I solve this by removing some log files that keeps building up when there’s an error, and that error was caused by a failed job queue which is keep repeating (keep trying to run the job) and store an error log line everytime it runs. I wasn’t aware until my disk was full and got a notification from newrelic.
You can follow my instructions there. Imagine you’re going into a room and check the content of each room. :) Basically I’m just trying to find which dir is it. That’s why I’m starting from the very top.
Go to root dir by cd /
List dirs and files: ls so you can go to each one of it.
Example results:
/usr
/var
/lib
/home
/dev
...
And do du -h [dir] for each of them:
du -h /usr
du -h /var
...
du -h /home <-- suspicious, contains couple of GBs of size
From each one of it see which one is suspicious (with largest dir size), that’s why I said mine was on /home
Then I’m doing cd /home, do the same from here: ls, do du -h /home/vagrant
Then I’m doing cd /home/vagrant, do the same from here: ls, do du -h /home/vagrant/mylaravelproject
Then I’m doing cd /home/vagrant/mylaravelproject, do the same from here: ls, do du -h /home/vagrant/mylaravelproject/storage
Then I’m doing cd /home/vagrant/mylaravelproject/storage, do the same from here: ls, do du -h /home/vagrant/mylaravelproject/storage/logs
Until you finally sure that directory was the culprit.
For me it was on /home/vagrant/mylaravelproject/storage/logs
On that /logs dir there was a huge 8 to 15gb of log files X_x
I remove it.. and voila!
Does it makes sense? Some people here might have better way of finding it though.
I’m having the same issue. Did you find a resolution?
Same issue here!
I am also seeing this
But
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:
lsAnd do
du -h [dir]for each of themWhen you see something suspicious you go inside that dir, or see from the du result.
For me it’s a
du -h homeWhen 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.
@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 !!
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.
This is better:
@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”