<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Nov 19, 2013 at 1:22 PM, Dave Hill <span dir="ltr"><<a href="mailto:myth@davidrhill.com" target="_blank">myth@davidrhill.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5"><span style="color:rgb(34,34,34)">I believe I was running without NFS at first when the problem
started and I thought NFS mounting the recordings might help. But I
can certainly try it again and see if I see any different, more
interesting messages.</span><br></div></div>
<br>
It happened again last night and stopping commercial flagging seemed
to clear it up. After that, it played smoothly for the rest of the
game. It seems like mythcommflag is somehow "locking out" the rest
of the system from reading the current recording.<span class="HOEnZb"><font color="#888888"><br>
</font></span></div><div bgcolor="#FFFFFF" text="#000000"><br></div></blockquote><div>FWIW, my recordings are also with real-time commflagging enabled. All the file systems are ext4, in case that makes a difference.</div>
<div><br></div><div>Jim</div></div></div></div>