root file system full

[Ralf Puchner]

check /dev for "big" devices created by wrong handling.... (as written in my previous answer).

[Michael Schulte zur Sur]

Hi,

how did it work out?

Michael

[Mohamed K Ahmed]

Well, I didn't get a chance to reboot the system this last weekend.
I have another question, In the /etc directory, there are a set of files that starts with #.mrg.. and another set starts with .new.. and a third set starts with .proto..
Can I delete the files starting with #.mrg..?

[Hein van den Heuvel]

> Can I delete the files starting with #.mrg..?

Time to check the doc!

At any rate. Do NOT just delete.
At the very least make a parallel structure under /usr, maybe called /usr/backup_root and load that with say
cp -pR /etc /usr/backup_root
cp -pR /dev /usr/backup_root
and so on...

But you 'owe' us much more feedback.
Many more concrete question were asked.
We believe that as you try to answer them you will stumble into the rigth solution eventually.

Cheers,
Hein.

[Ralf Puchner]

Hein,

cp is not a valid choice, use vdump, vrestore instead (as described within the admin guide).

[Michael Schulte zur Sur]

Hi,

I would not fiddle with the system files and delete what you suggested. I wonder, if you could save much space with that?
Could you post
du -kx /
please.

thanks,

Michael

[Michael Schulte zur Sur]

as attachment please!

forgot to say that.

Michael

[Ralf Puchner]

maybe time to study previous postings....

du counts the real filelength not the minimum space reserved (e.g. file with 900 bytes will use 1024 bytes on disk as minimum, but du counts 900).

df uses the allocated size (1024 bytes).

so you have a difference. If the disklabel size differ from df size there must be a "hidden" file somewhere (as explained by other forum members). So killing the process or reboot with single user mode is the only chance to get rid of it.

If disklabel and df have equal sizes look for unnecessary file or new files created. /dev is a good starter....

[Mohamed K Ahmed]

Here is the output for the du -kx / and the df -k output
I will post a summary at the end, when I solve this problem.
I am starting to believe that whe I reboot, this will clear the problem, but I would like to go to the end to find out what made it happened and where is the big files (if there is any)

tell me what do you think regarding the outputs attached

MO

[Michael Schulte zur Sur]

Hi,

if it still takes time for a shutdown and reboot, there is one thing, you may do.
move /sys/binary to antother place and replace it with a link to that place.
Ralf, correct me, but I think this dir is only used for kernel built.

hth,

Michael