Author |
Message |
Gibble
|
Posted: Sat Nov 24, 2007 11:12 pm |
|
Joined: Thu Sep 30, 2004 12:26 pm
Posts: 468
Location:
Canada
|
Code: Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 4828768 4584396 0 100% / /dev/hda3 149422336 60854088 88568248 41% /myth /dev/sda1 721075720 496669352 187777768 73% /myth/tv
Code: root@mythtv:/var# cd /var/log;du -ch | grep total 8.2M total root@mythtv:/var/log# cd /tmp;du -ch | grep total 36K total
Not sure what is going on!?
HELP! I can't start the front end, don't know if anything works at the moment.
_________________ "The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me
KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb
|
|
Top |
|
|
Gibble
|
Posted: Sat Nov 24, 2007 11:26 pm |
|
Joined: Thu Sep 30, 2004 12:26 pm
Posts: 468
Location:
Canada
|
Two areas that stick out are:
Code: root@mythtv:/nfsroot# cd /proc;du -ch | grep total 902M total
root@mythtv:/tftpboot# cd /usr;du -ch | grep total 1.5G total
_________________ "The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me
KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb
|
|
Top |
|
|
Gibble
|
Posted: Sat Nov 24, 2007 11:37 pm |
|
Joined: Thu Sep 30, 2004 12:26 pm
Posts: 468
Location:
Canada
|
Interesing...so I killed wine, and the program it was running (it had crashed and I thought it was because it ran out of disk...which is partially true...but only because it caused it)...and all of a sudden, I have 49% of my / partition free again...not sure what it did...
_________________ "The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me
KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb
|
|
Top |
|
|
mac
|
Posted: Sun Nov 25, 2007 2:57 pm |
|
Joined: Tue Feb 21, 2006 7:24 am
Posts: 396
Location:
Dushanbe, Tajikistan
|
/proc is physical memory -- it takes up no hard drive space except for an inode.
One thing to remember is that you can remove messages and syslog and the disk space that they are using will not be freed until you restart the syslog/klog daemon. The reason is that syslog process will be holding an open file handle for those files. Looking at disk utilization something that is useful to do is cd to / and do a "su -sh *" and continue that process in the directories that hold the most promise.
|
|
Top |
|
|
tjc
|
Posted: Sun Nov 25, 2007 6:04 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Top |
|
|
MisoSoup777
|
Posted: Tue Nov 27, 2007 1:17 pm |
|
Joined: Sun May 23, 2004 1:50 pm
Posts: 78
Location:
Palmdale, CA
|
Probably some sort of pagefile or temp memory that Wine was using...
Gibble wrote: Interesing...so I killed wine, and the program it was running (it had crashed and I thought it was because it ran out of disk...which is partially true...but only because it caused it)...and all of a sudden, I have 49% of my / partition free again...not sure what it did...
|
|
Top |
|
|
mogator88
|
Posted: Tue Nov 27, 2007 1:35 pm |
|
Joined: Tue Jan 30, 2007 1:27 am
Posts: 299
|
This happened to me a few months ago. Full root partition, wasn't the logs or anything like that. IIRC, after hours of looking for any file to delete I think I was down to about 98% full. I think I rebooted and then everything was "magically" OK again and I was back to my typical free space. The details are fuzzy, just another late night/early morning with the myth box.
|
|
Top |
|
|
cfr131
|
Posted: Mon Dec 10, 2007 2:05 pm |
|
Joined: Wed May 31, 2006 8:19 pm
Posts: 19
|
mogator88 wrote: This happened to me a few months ago. Full root partition, wasn't the logs or anything like that. IIRC, after hours of looking for any file to delete I think I was down to about 98% full. I think I rebooted and then everything was "magically" OK again and I was back to my typical free space. The details are fuzzy, just another late night/early morning with the myth box.
I have had this happen twice now; the last just yesterday. I ended up deleting several old logs, this gave me a little space. Once I rebooted, I was back to 48% free on the root partition. I looked and looked but never found anything that consumed the space. I even had a DU of the root before and after the reboot and I don't see any difference?
|
|
Top |
|
|
mogator88
|
Posted: Mon Dec 10, 2007 3:39 pm |
|
Joined: Tue Jan 30, 2007 1:27 am
Posts: 299
|
Last night I again had a full root partition. Deleted the logs and went down to 98%. Rebooted and was back down to 50%. This never used to happen. The only changes I can think of are that I've been doing a ton of transcoding, and I've added an HD Homerun. I set up both tuners on the HDHR, but I'm only using one at the moment, maybe that's triggering an error file I can't find.
|
|
Top |
|
|
tjc
|
Posted: Mon Dec 10, 2007 7:05 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Have you tried just restarting the FE and BE servers or whichever ones are associated with the logfiles you're having problems with? As I mentioned in passing above, Unix has sanity preserving file semantics. If you "delete" (actually "unlink") a file while someone is still using it, for example deleting the FE logfile while the FE still has it open, the space is not released until the last user closes the file. In this case, that most likely won't be until the FE process itself exits. A script running "tail -f" on the file, or anything like that, will also keep it in use.
What's _really_ happening under the covers is that the FS is essentially doing reference counting garbage collection of the inodes. The space is freed when the reference count for the inode (which includes the number of references in both the directory tree and process tables) goes to zero.
|
|
Top |
|
|
mogator88
|
Posted: Mon Dec 10, 2007 10:55 pm |
|
Joined: Tue Jan 30, 2007 1:27 am
Posts: 299
|
I'll try to remember that next time and report back.
|
|
Top |
|
|
tjc
|
Posted: Mon Dec 10, 2007 11:14 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
The fuser command will show you what processes have a file in use. E.g.:
Code: root@black2:~# fuser -v /home/mythtv/.xsession-errors
USER PID ACCESS COMMAND /home/mythtv/.xsession-errors: mythtv 20110 F.... x-window-manage mythtv 27034 F.... mythfrontend
|
|
Top |
|
|
mogator88
|
Posted: Fri Dec 14, 2007 7:53 pm |
|
Joined: Tue Jan 30, 2007 1:27 am
Posts: 299
|
A couple of days ago root filled up and I deleted the logs, and I went down to 50%. Tonight I was full again, deleted the logs, and stayed at 100% (maybe 27MB freed up.) I restarted the BE and the FE, and no change is disk usage. So I rebooted.
I have another problem. I have an error or errors on my disk. Its hard to read because there is a lot of overscan during boot. I'll do my best to transcribe the messages.
Code: checking file systems...fsck 1.40-WIP (14-Nov-2006) ???h contains a file system with errors, check forced. ???h: inodes that were part of a corrupted orphan linked list found.
???h: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) ???v/sdb1: clean, 1921/39075840 files, 71974313/87142160 blocks fsck died with exit status 4 ???led (code 4). <<<--- this line in red ???ile system check failed. ???og is being saved in /var/log/fsck/checkfs if that location is writable. please repair the file system manually. maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. >>>e root password for maintenance This is the contents of /var/log/fsck/checkfs, similar to the output above Code: Log of fsck -C -R -A -a Fri Dec 14 19:12:20 2007
fsck 1.40-WIP (14-Nov-2006) myth contains a file system with errors , check forced. myth: Inodes that were part of a corrupted orphan linked list found.
myth: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/sdb1: clean, 1921/39075840 files, 71974313/87142160 blocks fsck died with exit status 4
Fri Dec 14 19:12:21 2007
Maybe this has something to do with it? Its been happening for a while and I've been ignoring it, hitting Ctrl-D to continue to boot up.
|
|
Top |
|
|
BluesBrian
|
Posted: Thu Feb 14, 2008 6:27 pm |
|
Joined: Fri Jul 29, 2005 1:22 am
Posts: 232
Location:
SF East Bay, CA
|
|
Top |
|
|
tjc
|
Posted: Thu Feb 14, 2008 11:05 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
mogator88 wrote: Maybe this has something to do with it? Its been happening for a while and I've been ignoring it, hitting Ctrl-D to continue to boot up.
Yikes!!! You really need to fix that ASAP. When you're done check /lost+found/ and /myth/lost+found/ to make sure there's no leftover cruft there.
|
|
Top |
|
|