[mythtv-users] .25 - "Maximum buffer size exceeded"

[Michael T. Dean]

On 03/29/2012 10:57 PM, Phil Bridges wrote:
> On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean wrote:
>> On 03/29/2012 10:32 PM, Phil Bridges wrote:
>>
>>> On Thu, Mar 29, 2012 at 10:32 PM, Phil Bridges wrote:
>>>> I noticed that I had the mysterious "yellow dots" beside some of my
>>>> recordings this evening.  At second glance, I realized that the two
>>>> shows I was recording at 9PM had two files.  Not good.  One of the
>>>> shows was split into two halves, approximately 30 minutes each.  The
>>>> other though, had only about 11 minutes in it's first half.
>>>>
>>>> I looked at the log, and found this:
>>>>
>>>>
>>>> 2012-03-29 21:12:30.800845 E [7151/23462] HDHRStreamHandler
>>>> ThreadedFileWriter.cpp:216 (Write) -
>>>> TFW(/mnt/recordings2/1461_20120329210000.mpg:99): Maximum buffer size
>>>> exceeded.
>>>>                         file will be truncated, no further writing will be
>>>> done.
>>>>                         This generally indicates your disk performance
>>>>                         is insufficient to deal with the number of
>>>> on-going
>>>>                         recordings, or you have a disk failure.
>>>>
>>>> It also appeared that mythbackend restarted at the bottom of the hour
>>>> - at least, there was a new logfile generated.
>>>>
>>>> I was only recording two shows at the time, and I have plenty of space
>>>> on each of my recording mountpoints (this was recorded to a local
>>>> drive).  Any tips at how to further troubleshoot the issue?
>>> As a quick addition, my mounts are formatted XFS.
>>
>> any clues in dmesg or system logs?
>>
>> Mike
> Unfortunately, yes:
>
>
> Mar 29 22:51:46 kernel: hdd: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> Mar 29 22:51:46 kernel: hdd: possibly failed opcode: 0xa0
> Mar 29 22:51:46 kernel: hdd: drive not ready for command

Yep, that would do it--I can guarantee, since I've seen similar problems 
when I had failing HDDs.

> Crap.

Yeah, and especially now--when prices still haven't gotten back to where 
they were before the flooding.  :(

Good luck finding something--and recovering as much as possible from the 
failing drive.

Mike