Hi!!!

I just tried to download a file and it gave me an I/O error - failed writing, i did a df -h and this is what I got:
Filesystem Size Used Avail Use% Mounted on

/dev/hda5 16G 16G 0 100% /
none 125M 0 124M 0% /dev/shm
/dev/hda1 16G 13G 3.6G 78% /mnt/winc
/dev/hda7 5.4G 4.0G 1.3G 75% /mnt/debian
/dev/cdrom 620M 621M 0 100% /mnt/cdrom

/dev/hda5 is what I am on and it had 10 GB of free space last time I checked. I tried to search folder by folder, and there was a hidden file .xserv_errors in my home dir which was just 9.3GB large ... that's a helluva an error file.... Anyway after deleting it it I did another df -h and it still gives me the same result with no free space and there is no way it could have written another 9GB file in that short amount of time. Just to make sure I checked all the folders and they add up to 4.5 GB and my partition is obviously 16Gb largre, no hidden files, nothing in the Trash, or tmp. Whats eating up my memory??? Please HELP

Ok .. there is smth I found: the .xsession_errors file was written to by a utility called Konqueror from the java runtime environment. Seems like that guy can write to the .xsession_errors file with 20mb/s resulting in a extremely big 9gb file. The recommendation is to delete the .xsession_errors and forget about it but I already did that with rm -rf... what did I do wrong?

This has nothing to do with your memory but taking up actual hard disk space. Can you make out anything in the file your deleting? Have you even opened it to see if you can't make out anything on why its being created?

Yes of course i opened it first but it was empty (i opened it from command line and a window - there was nothing in it) however in the properties of the file it said 9.5GB .. i mean come on that's the size of 2 dvds. I deleted it but acts up like the space is still taken, and now if I delete some other file it just starts eating up space like crazy until it runs out of it just like its still writing to that file. I have no idea what to do i will post u any info want..

When you open a file from command line into text editor, it reads the entire file into memory -- that is why the file looks empty -- I doubt you have 9.5 gigs of ram

Try using the cat command for it, and see if you can't glean something.


-Shade