[mythtv-users] truncated recording

[Preston Crow]

On 02/18/2014 09:48 AM, George Mari wrote:
>
> On 2/18/14, 12:45 AM, Mark Wedel wrote:
>> On 02/17/14 07:42 PM, George Mari wrote:
...
>>> Feb 11 23:06:36 poseidon mythbackend: 2014-02-11 23:06:36.478976 E
>>> TFW(/video/recordings/2021_20140212043500.mpg:75): Maximum buffer 
>>> size exceeded.
>>> Feb 11 23:06:36 poseidon mythbackend: file will be truncated, no 
>>> further writing
>>> will be done.
>>> Feb 11 23:06:36 poseidon mythbackend: This generally indicates your 
>>> disk
>>> performance
>>> Feb 11 23:06:36 poseidon mythbackend: is insufficient to deal with 
>>> the number of
>>> on-going
>>> Feb 11 23:06:36 poseidon mythbackend: recordings, or you have a disk 
>>> failure.
...
I'm having the same issue.  Only with the Olympics on a HDPrime. Nothing 
else is recording, but they are very long recordings, so any 
intermittent issues will be more likely to show up.  The local file 
system is btrfs on a rather slow 3TB drive.  The OS and database are on 
a flash drive.

>>  But this leads to a few other related questions:
>>
>> 1) How bug is the bugger size that the recorder uses, and can that be 
>> increased?  Might not do any good, but it probably wouldn't hurt.
>>
I did a grep in the source for the log message, and it's in 
threadedfilewriter.cpp.  "kMaxBufferSize" is 8M, but it's multiplied by 
8, giving a size of 64M.  I think that's in bytes.

I'm going to rebuild with a patch to bump this up a good bit. (Another 
win for Gentoo -- just put the patch in 
/etc/portage/patches/media-tv/mythtv and build like normal!)

>> 2) Shouldn't mythtv do a better job at informing the user of this 
>> failure? Having to dig in the mythbackend logs hardly seems correct.  
>> If the tuner fails to tune it, the recording status will say as such
Yes, if a recording fails, it would be nice if whatever message goes in 
the log would also be displayed to the user when trying to watch the 
recording.  This is an issue for all recording failures, not just this one.