After a couple years of reliable service, my SLES10/OES2 file server is about to run out of space on the operating system partition. The files I’m hosting are on another partition and this partition has lot of space so I’m very confident that it’s the operating system files and folders that are the problem.
I’m assuming that this problem has slowly snuck up on me over the last couple years it’s been in service. Log files, accumulation of temp files? Due to my limited linux experience this server has many/most of the default settings since installation.
Sorry for my ignorance but I need a couple quick solutions to resolve this problem before the last 2GB of space is gone!
Any advice to configure the system so this won’t happen again is also appreciated.
How is your partitioning currently setup? The output from df -h could
be useful.
Cleaning out /tmp during a reboot can sometimes help on a plain SLES
box. Cleaning /var/log somewhat is often valid. Both of those options’
validity depend on your partitioning setup, though, so let’s start with
that df -h command output to see your space issues directly.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
[QUOTE=ajensen;3331]After a couple years of reliable service, my SLES10/OES2 file server is about to run out of space on the operating system partition. The files I’m hosting are on another partition and this partition has lot of space so I’m very confident that it’s the operating system files and folders that are the problem.
I’m assuming that this problem has slowly snuck up on me over the last couple years it’s been in service. Log files, accumulation of temp files? Due to my limited linux experience this server has many/most of the default settings since installation.
Sorry for my ignorance but I need a couple quick solutions to resolve this problem before the last 2GB of space is gone!
Any advice to configure the system so this won’t happen again is also appreciated.[/QUOTE]
As Aaron stated it would good to know more about the current partition setup and uses of the server.
You mention this system has been running for a couple of years, could be you just need some cleanup maintenance and the partitioning is fine.
To have a quick overview of the biggest directories in volume, and only for the root partition, try this command (as root):
du / -kx | sort -nr | head -n 30
The above runs the “du” command and specifies to look in root, the “k” option lists everything in kilobytes - as to be able to sort correctly, and the “x” option stays within the partition defined for the root (/) mount point.
Then that output is sorted on largest numbers downwards and finally the head command snips off the first 30 lines.
Not sure how much space you spec’d when you installed SuSE but
be sure to account for updates.
As for buying time, look for any out of control log files in /var/log, clean
them out.
You can look for large files in general by doing a
find . -size +10000 -print | more
You can specify different byte sizes. This command will start
looking in the current directory you are in. Obviously root
access is required to search some folders.
[QUOTE=GofBorg;3364]Not sure how much space you spec’d when you installed SuSE but
be sure to account for updates.
As for buying time, look for any out of control log files in /var/log, clean
them out.
You can look for large files in general by doing a
find . -size +10000 -print | more
You can specify different byte sizes. This command will start
looking in the current directory you are in. Obviously root
access is required to search some folders.[/QUOTE]
I ran into the same issue,
used these commands
du -h --max-depth=1 see what is in dirs 1 level down tin dir tree
ps -eo ppid,pid,user,stat,pcpu,comm,wchan:32
the problem ended being dsrmenu.sh was running on the server multiple times and ate 11G of space on my 16G root partition. there are no TIDs on this but running top and killing the PIDs instantly my server space was back