<div><span class="gmail_quote">On 10/21/05, <b class="gmail_sendername">Steve Pugh</b> <<a href="mailto:stevepugh@yahoo.com">stevepugh@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all,<br><br>I am running my Myth system with a PVR-250 for<br>capture, and a PVR-350 for capture and playback<br>through the 350's framebuffer.<br><br>Things are gorgeous, and I am thrilled to report that<br>since upgrading ivtv to
0.4.0 I have yet to see a hard<br>freeze during playback (previously, I would have to<br>hard reset once per "viewing evening" because the<br>framebuffer froze up solid, even though the OSD<br>display showed life).
<br><br>However, I am still experiencing a solid framebuffer<br>freezeup when, after watching a show, I choose either<br>of the two delete options available to me. The<br>machine itself is still running, and mythbackend<br>
continues to record, but the frontend locks up.<br><br>A search of the archives turned up some old (2003)<br>posts which leaned toward ivtv as the issue - however,<br>I've not had any reply from that list so I am begging<br>
your indulgence.<br><br>If any kind souls can offer guidance or suggestions, I<br>would be most appreciative. The output is beautiful,<br>so the sooner I can rock-solidify it, the quicker I<br>can bask in the exceptionally high WAF that the system
<br>deserves ;-)<br><br>Thoughts? Recommendations? Good curry recipes?<br><br></blockquote></div>Deleting
a recording while recording is underway, or while some other I/O is
active, MAY result in the system hanging. The system may recover
in a few seconds, or it may seem to be permanently hung. You can
search the archives for the terms "IOBOUND" and/or "discontinuity" and
read about more difficulties when a recording is deleted.<br>
<br>
Some may claim that using a particular filesystem can avoid the IOBOUND
condition, but the filesystem might have some other risks associated
with it.<br>
I use ext3 filesystem because it is reliable and stable, but if I
forget to manually delete old Letterman, Leno, etc., shows, then I get
corrupted recordings. The backendlog shows IOBOUND messages that
correspond exactly with the times of the corruption.<br>
<br>
I would like to (someday) ask for MythTV to provide support for
scheduling "UN-recording" of programs. Instead of
AutoExpire happening immediately within two minutes of the start of
recording a program, the delete would be deferred until the time when
the backend determines that it is idle. At that time, the backend
has nothing to do, and usually shuts down the system just after
scheduling the system to power-on in time for the next recording.<br>
<br>
Besides scheduling the next power-on, the backend could check if there
had been any "UN-recordings" requested, delete those recordings, and
then shut down.<br>
<br>
You might want to check the backendlog on your system for any IOBOUND
messages that correspond to the times when your system hung.<br>
<br>
-- <br>
MM<br>
<br>