[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Mon, 9 Dec 2013, Martijn Grooten wrote:
On Mon, 9 Dec 2013, Tom wrote:But sda8 is to all intents and purposes full so do an analysis of it.Indeed. (And it's not an issue with the number of inodes.) Running du /gives you a list of all the files on the partition and its sizes in bytes. You can pipe that to "sort -n" to get a list of the biggest files.A quick way to find all files whose size is measured in gigabytes is du -h /|grep -E "G\s"(I'd run the latter first to see if it gives you one single file that is the issue. And then the former.)Note that both will also give the amount of disk space used by directories and their subdirectories. That's probably useful, but also something to be aware of.
du -sm . | sort -rn | head -10 is my favourite...But there's a handy old program called xdu that takes as its input the output of the du command, so:
sudo du -m / > /tmp/du.out xdu /tmp/du,outthen you can see graphically directory sizes and navigate through them. You might need the -x flag if you have remotely mounted things though.
(and you might need to install xdu - it doesn't seem to come as standard with Debian at least)
Gordon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq