Sage 2.2 afraid of large disks?

[jhkoenig]

After 9 months of joy with Sage 2.2.8, I started running out of disk space (I know, I'm the only one who EVER had this problem!) I added a second SATA 250GB hard drive, and everything looked great.

Sadly, SageTV.exe lurks in the background behaving nicely, then after about 24-36 hours, jumps out and takes 99% of the CPU, effectively hanging the machine. I can CTRL-ALT-DEL to bring up the task manager, kill the process and launch it again. Because of the great architecture of Sage, the Sage service keeps on running, so I don't lose anything that is currently recording. The WAF takes a big hit, though, so I'm pretty anxious for a fix.

Any ideas? Things were going so great....

TIA
--John

[laurenglenn]

Originally Posted by jhkoenig

After 9 months of joy with Sage 2.2.8, I started running out of disk space (I know, I'm the only one who EVER had this problem!) I added a second SATA 250GB hard drive, and everything looked great.

Sadly, SageTV.exe lurks in the background behaving nicely, then after about 24-36 hours, jumps out and takes 99% of the CPU, effectively hanging the machine. I can CTRL-ALT-DEL to bring up the task manager, kill the process and launch it again. Because of the great architecture of Sage, the Sage service keeps on running, so I don't lose anything that is currently recording. The WAF takes a big hit, though, so I'm pretty anxious for a fix.

Any ideas? Things were going so great....

TIA
--John

Upgrade to version 4. It's free

Lauren

[jhkoenig]

Originally Posted by laurenglenn

Upgrade to version 4. It's free

Lauren

I plan to upgrade, but hope for a few more months with other people finding bugs and Frey fixing bugs before I jump in. Sage 2.2.8 has been stable as any other appliance in the house, until now. With all respect to the Sage programming team, any application of size has bugs, and bugs take time to work out. An upgrade is risky, and sleeping on the couch is a very possible outcome of a botched upgrade. Sage has become *very* embedded into the household's quality of life and I will work for weeks on test upgrades and roll-backs before attempting a production upgrade. Shuttle launches are done with less stress.

Is it better to carve that big drive into several smaller volumes? What am I overlooking? If it matters, I'm running Malore.stv, Girder for remote control and no other enhancements.

--John

[dblaine2]

I have several 250 gig SATA drives setup on a RAID5 controller with no issues. I am also running 2.2.8 and waiting for the bugs to be worked out of 4.1.x before upgrading (also I'll miss my cayars interface).

I fully understand about the shuttle launches tho. It would be a massive effort in my household too.

[ben_95sl1]

when I started having problems with 2.2.8 that I couldn't figure out, I decided it was time to see if upgrading would fix it. Well, for some reason it has. But adding a 300gb drive to my system started some problems again. Now they have stopped for a few days; don't know why.

I've always had problems with the backend going 100% cpu....I've crashed the front end, but it has to do with video stuff and I know exactly why. I don't see how the extra disc would affect the front end???

try the debug logging entry in the properties file.

[dblaine2]

Maybe the drives are not really the cause maybe a coincidence....

Have you tried testing the memory using memtool?