ROOT PARTITION 100% FULL

[stovie]

Help!!!
My employer has just made me responsible for the SCO Openserver 5 machine in our office. The server was partitioned
wrong by the previous admin newbie, and the / partition he
created is 100% full. What are my options? Here is the output
from the df -ivk command.

mount dir filesystem blocks used free %used

/ /dev/root 563201 563173 28 100%

/stand /dev/boot 15361 9224 6137 67%

/u /dev/u 16510782 8837574 763208 54%

 

[edfair]

You will need to clean stuff out. By rebooting into single user mode or using the emergency boot set and mounting the drive for the duration or the cleanout.

With that little free I suspect that the floppies are going to be critical.

You only need to post once. Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[magnacomp]

This is a common problem we encounter and fix rather quickly.

You have not told us what applications are running on this machine so it will be hard to find the log files and such to get some space back.

Looks like you made it to the command line, that's great. If you want to get some faster information on what is left try using 'df -v' all by itself.

What you want to do is remove some really large files fast. We need to review the command that will help us first. Whenever I say dus something I mean this command :
'du -s -- * | sort -n' . This will give you the largest object in the current directory as the last item, file or directory.

First you probably have a huge requests file for your print requests. Go to /usr/spool/lp
and type the dus command. You will most likely notice that logs is big. Cd to logs. Run dus. You will most likely see requests is huge. type 'cp /dev/null requests' to zero out the file. type df -v and see if that made a difference.

Repeat this procedure in other problem areas. Some things will be removed some will be nulled out. DO not remove or null out if you do not know what it is for. The requests file is just a log of all print requests ever done since it was nulled out.

Next look at /lost+found you should remove all the files in that directory.

Next look in /tmp. We have a rule that if the system gets to be so low as 100% used then all files in /tmp are fair game. Change to the /tmp directory and do the dus command. The last item could be something huge. If so remove it. If you can't see that much there you could just cd to /tmp and type rm * (make darn sure that you are in the /tmp directory by using pwd before that).

If you don't use email services on this machine your mail boxes should not be huge. CD to the /var/spool/mail directory and run the dus command.

A really cute trick is to go to the /dev/ directory. DO NOT remove files here unless they are obvious mistakes. Run dus and there should be NO big files. If there is a big file someone may have made a backup and miss typed the /dev file name an MADE a file rather than archiving to tape or disk.

Let me know what you find.

jim