<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/07/14 12:21, Steve Hodge wrote:<br>
</div>
<blockquote
cite="mid:CAKQyFDYgzfrYvRYycE0Or7FevrtXaW4mTtCLtkHn46Dk995NJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Jul 7, 2014 at 12:08 PM,
Aaron Pelly <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:apelly@monkeymasters.co.nz" target="_blank">apelly@monkeymasters.co.nz</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 07/07/14 11:23, Steve Hodge wrote:<br>
</div>
<div class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
If it's not consistently happening with simultaneous
recordings it's probably not a throughput issue. You
could try recording say 6 things at once to test this.<br>
</blockquote>
</div>
You made me watch some Home and Away. Damn you!<br>
<br>
Inconclusive results. iotop shows about 2MB/sec to two
storage groups.<br>
gnome-system-monitor shows mythbackend and mount.ntfs both
ranging from 3 to 6% CPU. Both cpus running about 15-20%<br>
some recordings OK. Some show corruption. Corrupt shows
are on Sommet and Prime. This is not always the case.<br>
</blockquote>
<div><br>
</div>
<div>Probably not a HD or RAM bottleneck if they're not all
corrupt.</div>
</div>
</div>
</div>
</blockquote>
Yes, and IO looks trivial.<br>
<br>
<blockquote
cite="mid:CAKQyFDYgzfrYvRYycE0Or7FevrtXaW4mTtCLtkHn46Dk995NJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Maybe do some testing with commercial detection off in
case that is corrupting them somehow.</div>
</div>
</div>
</div>
</blockquote>
Can do. Surely it doesn't run for live tv though?<br>
<br>
<blockquote
cite="mid:CAKQyFDYgzfrYvRYycE0Or7FevrtXaW4mTtCLtkHn46Dk995NJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> Might also be worth looking into whether one tuner in
particular is the source of corrupt recordings.<br>
</div>
</div>
</div>
</div>
</blockquote>
Do you know if the tuner that was used stored in the DB anywhere?
Might save me some time.<br>
<br>
<blockquote
cite="mid:CAKQyFDYgzfrYvRYycE0Or7FevrtXaW4mTtCLtkHn46Dk995NJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Interesting backend log entry:<br>
11:55:39 zeus mythbackend: mythbackend[2503]: W
DeviceReadBuffer recorders/DeviceReadBuffer.cpp:555 (Poll)
DevRdB(/dev/dvb/adapter1/frontend1): Poll took an
unusually long time 2547 ms<br>
<br>
Last 2000 lines of the backend log:<br>
cat /var/log/mythtv/mythbackend.log | tail -2000 |
pastebinit<br>
<a moz-do-not-send="true"
href="http://paste.ubuntu.com/7757924/" target="_blank">http://paste.ubuntu.com/7757924/</a><br>
<br>
I'll investigate that log entry further.</blockquote>
</div>
</div>
</div>
</blockquote>
Makes me wonder if I should try different firmware. Cant remember
where I got the current version from. Probably via the linux tv
wiki. I recall there were multiple versions.<br>
<br>
<blockquote
cite="mid:CAKQyFDYgzfrYvRYycE0Or7FevrtXaW4mTtCLtkHn46Dk995NJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Have a look at the kernel log too.<br>
</div>
</div>
</div>
</div>
</blockquote>
Nothing shows up around the time I tested multiple recordings.<br>
</body>
</html>