[mythtv-users] Issues with 0.25

[Michael Watson]

On 1/03/2012 11:54 PM, Terjesen Jens Peder wrote:
> I have been on pre-0.25 since early December because I kept getting missed or zero byte recordings.
Im seeing the recording much more reliable than under 0.24.2, but I have 
had a couple of times where a couple of my tuners will fail to respond, 
thus causing a failed recording
>
> The main functionality of scheduling, recording and playing the recordings have usually been working OK.
>
> About two weeks ago I started getting periodically long startup times for the frontend, usually 30 - 120 seconds.
> I can't see anything in the frontend or backend logs.
I have not seen anything like this.  Im currently upgrading each day to 
the latest Mythbuntu 0.25 debs
> I also get periodic freezes in the frontend also usually 30 - 120 seconds.
> I get the freezes when marking a recording as watched, when deleting a recording, when opening the EPG, when navigating the EPG and when scheduling recordings.
Not seeing this, but have read many times on here that EXT4 barriers 
enabled will cause this sort of behavior
>
> With about 500 channels on two satellites the scheduler uses about 20 - 25 seconds when I add a recording.
> This combined BE/FE has a three year old AMD dual core 45 or 65 watt CPU.
Im running a P4 3.4Ghz, 2Gb RAM on the backend OS / DB is on ext3, 
recording on 7x Drives with XFS, I have 5x DVBT Tuners, with only 12 
channels. (I have around 130 recording rules)
Scheduling averages at 11 Secs, (I have had two occasions where 
scheduling took over 500 secs (when system was under next to no load)

> The database and OS is on an EXT4 partition on one drive, and the recordings go to four drives with XFS using storage groups.
>
> Now that I have got my new UPS working, would it be (reasonably) safe to disable barriers on the EXT4 partition?
I would imagine so.
>
> Is it possible that the CPU could be causing this?
>
> Have anyone else seen this, or have any suggestions where to look?
>
> Jens
>
>