My Myth box is working quite well, except for this one problem. I have my HD partitioned into a 2.5GB root dir, 3GB /cache dir, a 300MB or so swap, and the rest (6GB or so) for /myth. (I'm planning on upgrading to a 120GB in the near future). When I leave it watching live TV for an extended period of time (usually overnight if I forget to exit) it will freeze up. Not the whole system, mind you, because I can still SSH in from whereever and reboot, but just Myth. The odd part is, if I do a df, it shows that the /cache partition is at 100%, as well as the / partition, which I would not expect. Playing with du, I can find NO files that are extremely large, but mysteriously, when I reboot, there is free space again on that partition. Has anyone else had this problem?

-Mike

Well if /cache is full that is probably why it is locking. you can define how much of the ring buffer to use in mythtv-setup. Since you can ssh in, have you checked the logs?

_________________
cesman

When the source is open, the possibilities are endless!

Yeah, usually the .1.gz log is old (well before the freeze) and the .log is empty. I'll monitor the /cache size and how much should be left free, but why would that cause the root dir to fill up (or apparently fill up)?

Decreasing the live TV buffer size to 2GB (on a 3+GB partition) seems to have stopped the freezes. Thanks! Still strange that the root part. fills up as well...

Hi,

yes, why should anything be written to the root instead of the /cache dir? Can we get it moved into either /cache or /myth?

jason

_________________
Jason L. Froebe

HealthyPals (http://www.healthypals.com)
Bookcrossing (http://www.bookcrossing.com)
WebBlog http://www.livejournal.com/users/jfroebe

I could never verify that something was indeed being written to root - I could find no large files or anything...I just know that a substantial amount of space was freed up after reboot. I'm rebuilding with a larger hard drive this week; it will be interesting to see if I have the same error.