Timeline for What's eating my disk space?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2020 at 5:20 | comment | added | Techie | This is amazing stuff. Up-voted | |
| Oct 22, 2018 at 14:18 | comment | added | Derek | Worth a note that this requires root privileges. Also, I used sudo lsof -s | grep deleted | sort -hk7 to get a numerical sort. Without -h, sort does funny lexical things with numbers. | |
| Jul 24, 2015 at 14:49 | comment | added | aviggiano | I had a process writing an append-only-file that grew indefinitely and eventually filled my disk. Then I decided to rm that file but the process didn't close its file descriptor, so it was somehow still being used. Restarting the process and limiting the AOF size solved my problem. | |
| Mar 25, 2015 at 21:00 | comment | added | aemus | This was a great suggestion and it indeed helped me solve a problem similar to the parent question. I had a huge discrepancy between df and du commands. In my specific case, I have rotating logs and a service that forwards the logs (logstash in this example). The logstash service was keeping the rotated logs open, even when deleted. This was causing the discrepancy between du and df. Once the logstash service was restarted disk space showed up correctly. | |
| Feb 8, 2014 at 12:24 | comment | added | Arry | Good suggestion, but on my machine this command reports only 2 open deleted files with size of 2k, which is a far cry from 2.7G consumed over time by some stray process. | |
| Feb 6, 2014 at 14:12 | history | answered | angus | CC BY-SA 3.0 |