LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Distributions (https://www.linuxquestions.org/questions/linux-distributions-5/)
-   -   /home directory is full :S .xsession-errors (https://www.linuxquestions.org/questions/linux-distributions-5/home-directory-is-full-s-xsession-errors-268250/)

carl0ski 12-19-2004 10:34 PM

/home directory is full :S .xsession-errors
 
i have a 20gig /home partition
with 2gig of files on it yet all 20gig is used
0bytes remaining

i deleted a HUGE file that was 18gig (.xsessions-errors) yet my free spave hasn't come back.

How can i search for what file(s) are using all my space
i tried
ls -s -h
but it wouldnt show hidden files and xsession-error showed up as a 0byte file where as right click properties said it was 18gig


thanks for the help i'm immensly lost :(

paulsm4 12-19-2004 10:40 PM

It sounds like :.xsessions-errors" was probably the culprit. Please:

1. Reboot your PC into single-user mode and run "fsck".

That will probably fix the "missing space" problem. Running "fsck" could also clear up some other side-effects of the crash that you might not even be aware of ... yet.

2. Have you fixed whatever it was that caused .xession errors?
What was it, out of curiousity?

3. Finally, run "du -s" on other main directories (especially "/var/log") to see if any other directories might be suspiciously large. My guess is that you're probably OK...

'Hope that helps .. PSM

carl0ski 12-19-2004 10:54 PM

i have no idea what caused it.

but konquerer was randomly started closing and Mozilla Firefox kept saying insufficient space on drive.

so i checked free space and welll the partition was full.

i'm hoping there is a way to turn off the logging considering 18 gig isn't very useful information wise noone could ever read trough it all.

i'm try your suggestions now though

trickykid 12-20-2004 08:24 AM

Quote:

Originally posted by carl0ski
i have no idea what caused it.

but konquerer was randomly started closing and Mozilla Firefox kept saying insufficient space on drive.

so i checked free space and welll the partition was full.

i'm hoping there is a way to turn off the logging considering 18 gig isn't very useful information wise noone could ever read trough it all.

i'm try your suggestions now though

Well, you deleted the file and the space did not go away as X was probably trying to write to that file still, had it open, etc. You don't necessarily have to shutdown and reboot, but kill X and or restart it.

Secondly, after restarting, if it starts writing to the log, maybe you should take a look and see what the problem might be, before it gets too big and whether its a problem you don't want to ignore, before turning off the logging, cause that is what logs do for us, report system and software issues, so we know what's going on.

carl0ski 12-20-2004 04:01 PM

nah the file didnt come back at all :)

anyone know how disable the X output log?
i'm not going to ever use it so i midas well disable the log :)

paulsm4 12-20-2004 04:46 PM

Hi, again -

1. "X Windows" is your GUI - I'm guessing that you probably don't want to disable it.

If you do, the easiest way is to change your default run level. For now, let's not discuss "What's a runlevel?" or "How do I change it?"

2. Back to the problem at hand:
It looks like you're using your X Windows GUI, and that one of your GUI programs went berserk and max'ed out your filesystem with an 18GB log.

There are many ways for this to happen.
EXAMPLE:
http://www.linuxpackages.net/view_co...=3554&cid=1656

3. What you need to do is:
a) be aware of what programs you're using
b) Keep an eye on the .xsession-errors log to make sure it stays a reasonable size

4. If the problem *does* recur, then:
c) See if the .xsession-errors log identifies the culprit
d) Otherwise, run "top". The odds are good that the culprit will be doing the most I/O and/or using the most CPU time.
e) Fix, disable or update the culprit (for example, get a new copy of "mplayer").

X Windows is not the culprit; the enormous log was just a side-effect of the root problem.

'Hope that helps .. PSM

PS:
No, you don't need to reboot the PC for an X Windows error. But you should *always* cold-boot the PC and run "fsck" if you ever have a disk-related crash (as you did when your filesystem became full).


All times are GMT -5. The time now is 03:21 AM.