<div dir="ltr"><br><div class="gmail_quote">On Tue, Sep 9, 2008 at 1:25 PM, John Drescher <span dir="ltr"><<a href="mailto:drescherjm@gmail.com">drescherjm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> I have been doing this same thing for a while and have not noticed any<br>
> missed portions of recordings.<br>
><br>
<br>
</div>Same here with 4 Seagate SATA drives and storage groups since late<br>
2006 / early 2007 with SVN 0.21.<br>
<font color="#888888"><br></font></blockquote></div><br>I have been monitoring recording activity and saw the following errors in the MythTV backend log.<br><br>[root@mythtv mythtv]# fgrep "IOBOUND" mythbackend.log*<br>
2008-09-09 15:00:18.393 TFW, Error: Write() -- IOBOUND begin cnt(9400) free(4535)<br>
2008-09-09 15:00:22.325 TFW, Error: Write() -- IOBOUND end<br>
2008-09-09 15:00:22.341 TFW, Error: Write() -- IOBOUND begin cnt(9400) free(8959)<br>
2008-09-09 15:00:22.347 TFW, Error: Write() -- IOBOUND end<br>
<br>The Backend log goes back nearly 4 months with no occurrences of IOBOUND errors until I configured the drives to sleep using 'hdparm' yesterday. Also, the IOBOUND errors occur only in the first few seconds of recording. Do these messages indicate that the recording will be corrupted, or are they just a warning that the IO is not responding quickly?<br>
<br>Thanks,<br><br>--<br>Scott Kidder<br></div>