Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You might want to check your partitions using "du -sh"
mingdao@james:~$ du -sh
This gives you a summary of the disk usage of each FILE, recursively for directories. And the switches -- s is for summarize and h for human readable. There are many more options which might suit your needs more ... read "man du" to check.
I don't have an .xsession-errors file, or any other .xsession* files on this box. However, I run Fluxbox and not a desktop environment, which might be the reason. But on other boxen here running KDE, there were no .xsession* files, either. Perhaps it's only generated when there is an error.
That is for windoze, not Linux. You need to go wash your mouth out for saying that. LOL
I doubt that will fix it. That is strange and there is something there that is taking up the space. Maybe check and see what is mounted and where it is mounted. Maybe there is a typo in your fstab file.
Oh, empty your trash too. I know when I delete things in Konqueror as root, it puts them in the root trash can instead of the user that KDE is logged in as. Maybe your trash can is the hog. May want to check both.
Did you check to see if anything else may be mounted in it by mistake? Just type in mount and it should list the partitions and where they are mounted. You can mount partitions twice or have them mounted in two places. I have done that before.
I have two users in my /home and it uses only about 720Mbs of space and I use reiserfs as well. I'm running out of ideas. We need a real guru.
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda6 on /home type reiserfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
1) df and du do their calculations slightly differently so won't give you exactly the same results but should be close enough most of the time so that likely wasn't your issue.
2) The most probable issue was that a file got deleted while it was still open by a process. When this occurs the file NAME gets deleted but not the file INODE. A reboot will always cure this because it kills all processes (including the one that held the file open).
However you don't have to reboot as pointed out above. Instead you can do "lsof /home" to see all open files and associated processes using /home. Typically in this situation you'd see a very large size file open but no name. If you kill the process associated with that it will free up the INODE and the deletion will complete.
lsof will show you things tha fuser often won't as far as what is busying out a filesystem. It has many other uses including examining open network connections and associating those with processes so is better than netstat in that regard.
Distribution: Mint Xfce, Korora Gnome3, Ubuntu Server NoGui,
Maye the reboot fixed it because it was a logfile and deleting it probably created a tmp backup that was being used till you shut down or its loaded in ram at the beginning of the session so until it left ram it was being used. Just guesses don't know for sure. But I do also think journaled fs's like reiserfs don't show all you unallocated space accurately because some is reserved for backups of recently deleted files. I don't know how the journal gets reported by df or du but keep that in mind. That's why shred is unreliable with journaled fs's. The percentage of yours is odd though but maybe because the partition is so small and the journal is based on mb's not percentage of drive space available. Again just a guess.