#11127: deadlock in backend after recording device failure
------------------------+--------------------------------------------
Reporter: brian@… | Type: Bug Report - Hang/Deadlock
Status: new | Priority: minor
Milestone: unknown | Component: MythTV - General
Version: 0.25-fixes | Severity: medium
Keywords: | Ticket locked: 0
------------------------+--------------------------------------------
I have been noticing a pattern here. My backend deadlocks and needs to be
restarted after a recording failure presumably due to a device failure.
This really should not happen.
Yes, I understand that trying to deal with hardware failure is not always
easy, but hardware does fail, sadly. Having the backend become moribund
when this happens is tragic, to put it nicely. Hardware failure should
result in at most, a failed recording at the time. The backend should
simply pick itself up and get on with life instead of lying down like a
dead dog.
I will attach a backend log as well as a stack trace of this situation.
P.S. I am really trying to resist the urge to set the Priority and/or
Severity on this ticket. This issue is very severe and should have the
utmost priority, IMHO. WAF is nosediving fast and hard due to an entire
night of favourite show season premiers for a whole night not recording
due to a dual (multirec at the same time) recording failure.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/11127>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
_______________________________________________
mythtv-commits mailing list
mythtv-commits@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-commits
------------------------+--------------------------------------------
Reporter: brian@… | Type: Bug Report - Hang/Deadlock
Status: new | Priority: minor
Milestone: unknown | Component: MythTV - General
Version: 0.25-fixes | Severity: medium
Keywords: | Ticket locked: 0
------------------------+--------------------------------------------
I have been noticing a pattern here. My backend deadlocks and needs to be
restarted after a recording failure presumably due to a device failure.
This really should not happen.
Yes, I understand that trying to deal with hardware failure is not always
easy, but hardware does fail, sadly. Having the backend become moribund
when this happens is tragic, to put it nicely. Hardware failure should
result in at most, a failed recording at the time. The backend should
simply pick itself up and get on with life instead of lying down like a
dead dog.
I will attach a backend log as well as a stack trace of this situation.
P.S. I am really trying to resist the urge to set the Priority and/or
Severity on this ticket. This issue is very severe and should have the
utmost priority, IMHO. WAF is nosediving fast and hard due to an entire
night of favourite show season premiers for a whole night not recording
due to a dual (multirec at the same time) recording failure.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/11127>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
_______________________________________________
mythtv-commits mailing list
mythtv-commits@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-commits