[mythtv-users] recording not starting on time - one cause

[John Drescher]

On Dec 16, 2007 4:09 PM, Chris Isip <cmisipster at gmail.com> wrote:
> In my effort to get rid of the ivtv buffers full errors in dmesg, I have
> made a couple of conclusions.  Running optimize_mythdb.pl and backing up the
> mythtv database will result in this error.   Furthermore, backing up the
> myth database with mysqldump causes the server to be unresponsive for the
> duration of the backup which means no playback possible on any frontends and
> no recording will start.  The backend does not actually crash.  It seems any
> playback or recording is "queued" and starts immediately after mysqldump
> finnishes.  Hence the missing 8 minutes at the beginning of my recordings at
> 1 AM.  Just thought I'd let the list know, in case somebody else is having
> these problems.
>

Why not schedule this at 3:00AM or some other time that you know you
will not be recording? The other way around this is to have the
database on a second machine or even a different hard drive than the
controller. Both of these database operations are very hard drive and
interrupt intensive (because they end up causing a lot of hard drive
thrashing) and the problem with that is that it ends up the you
filesystem is not able to keep up with the datarate that ivtv needs.

John