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

[Monkey Pet]

I have dual HDhomerun tuners.  Mythtv 0.25 was recording two HD shows.  One
got truncated with the buffer exceeded error.  No other errors in dmesg or
/var/log/messaages, i looked for hard drive errors and found none.  To make
the matter worst, mythtv showed me that it was still recording (definately
a bug), the file was truncated.  Mythtv also lied about the file size and
recording duration (also bugs).  If the recording is truncated, don't lie
to the user.  Also this never happend with 0.24 which seems more robust.

On Tue, May 1, 2012 at 10:20 PM, scram69 <scram69 at gmail.com> wrote:

> On Tue, May 1, 2012 at 8:22 PM, Phil Bridges <gravityhammer at gmail.com>
> wrote:
> > On Tue, May 1, 2012 at 2:09 PM, scram69 <scram69 at gmail.com> wrote:
> >> On Thu, Mar 29, 2012 at 7:57 PM, Phil Bridges <gravityhammer at gmail.com>
> wrote:
> >>> On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean
> >>> <mtdean at thirdcontact.com> 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
> >>>
> >>> Crap.
> >>> _______________________________________________
> >>> mythtv-users mailing list
> >>> mythtv-users at mythtv.org
> >>> http://www.mythtv.org/mailman/listinfo/mythtv-users
> >>
> >> Phil-
> >> I am seeing the exact same error from HDHRStreamHandler on my backend.
> >>  Not only does it freeze the backend, but I have to reboot the machine
> >> to recover.  I am running an 0.25 Mythbuntu build from April 22nd.
> >> Were you able to definitively determine the cause was a failing HDD?
> >>
> >> Thanks,
> >> Steve
> >
> >
> > Steve - my problem did end up being related to a failing hard drive.
> > Replaced it, and I haven't gotten this error.
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://www.mythtv.org/mailman/listinfo/mythtv-users
>
> Thanks for the update.  That's what I was afraid of.  Mine is a 5-disk
> raid 5 array.  I tested each drive with the WD utility, and all five
> passed.  So now, my plan is to hot remove one drive at a time until I
> can get the error to go away...
>
> Steve
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20120503/3a87f5f5/attachment.html>