[mythtv] [mythtv-commits] Ticket #8199: backend lockup on recording expiry
Michael T. Dean
mtdean at thirdcontact.com
Wed Mar 17 17:41:05 UTC 2010
On 03/17/2010 01:29 PM, MythTV wrote:
> #8199: backend lockup on recording expiry
> -------------------------------------+--------------------------------------
> Reporter: michael_zanetti | Owner: danielk
> Type: defect | Status: infoneeded_new
> Priority: trivial | Milestone: unknown
> Component: MythTV - Recording | Version: 0.22-fixes
> Severity: medium | Mlocked: 0
> -------------------------------------+--------------------------------------
>
> Comment(by anonymous):
>
> I check the backend log on nearly every lockup. So far I can tell you that
> there is nothing suspicious in there. But I ran the backend with the
> default loglevel. The backend just stops logging at some point. Sometimes
> the logs stop completely after the hangup. Sometimes there are still some
> messages logged.
>
> I have attached two example logs:
>
> mythbackend.log.1 shows the last lockup I had. It happened directly after
> exiting LiveTV.
> mythbackend.log.2 shows a somewhat older failure. It happened on an
> autoexpire event
>
> Please note that in mythbackend.log.2 there are still some frontend
> connect events from a frontend logged. Those entries happened _after_ the
> backend locked up. The entries are there because I started and killed the
> frontend a few times, which for obvious reasons hung too. The last entry
> while the backend was working was the autoexpire one.
>
> Those logs are created using the default log level. I just have
> reconfigured my backend to log "all" messages and I will post future
> lockups with hopefully more detailed informations.
>
Which file system are you using for your recordings? Is it ext3? If
so, did you not enable "Delete files slowly" in mythtv-setup? A large
I/O wait could conceivable cause the backend to hang sufficiently long
to cause problems with the backend connections.
Mike
More information about the mythtv-dev
mailing list