Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

.25 - "Maximum buffer size exceeded"

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


gravityhammer at gmail

Mar 29, 2012, 7:32 PM

Post #1 of 18 (2739 views)
Permalink
.25 - "Maximum buffer size exceeded"

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?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gravityhammer at gmail

Mar 29, 2012, 7:32 PM

Post #2 of 18 (2685 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Thu, Mar 29, 2012 at 10:32 PM, Phil Bridges <gravityhammer [at] gmail> 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.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Mar 29, 2012, 7:49 PM

Post #3 of 18 (2680 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

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
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Mar 29, 2012, 7:50 PM

Post #4 of 18 (2682 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On 3/29/2012 22:32, Phil Bridges wrote:
> 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?

How old a version of 0.25 are you running? There was an issue fixed in
the recording quality monitor a couple weeks ago that caused excessive
amounts of context switches in HDHR recordings. Those could potentially
cause problems such as filesystem stalls, and the inability to flush to
disk in a timely manner, resulting in terminated recordings.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gravityhammer at gmail

Mar 29, 2012, 7:57 PM

Post #5 of 18 (2681 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean
<mtdean [at] thirdcontact> 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
http://www.mythtv.org/mailman/listinfo/mythtv-users


gravityhammer at gmail

Mar 29, 2012, 7:58 PM

Post #6 of 18 (2689 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Thu, Mar 29, 2012 at 10:50 PM, Raymond Wagner <raymond [at] wagnerrp> wrote:
> On 3/29/2012 22:32, Phil Bridges wrote:
>>
>> 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?
>
>
> How old a version of 0.25 are you running?  There was an issue fixed in the
> recording quality monitor a couple weeks ago that caused excessive amounts
> of context switches in HDHR recordings.  Those could potentially cause
> problems such as filesystem stalls, and the inability to flush to disk in a
> timely manner, resulting in terminated recordings.
>

MythTV Version : v0.25pre-4673-g89c34ef
Library API : 0.25.20120223-1
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Apr 1, 2012, 6:43 PM

Post #7 of 18 (2644 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

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
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


scram69 at gmail

May 1, 2012, 11:09 AM

Post #8 of 18 (2546 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Thu, Mar 29, 2012 at 7:57 PM, Phil Bridges <gravityhammer [at] gmail> wrote:
> On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean
> <mtdean [at] thirdcontact> 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
> 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
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gravityhammer at gmail

May 1, 2012, 8:22 PM

Post #9 of 18 (2535 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Tue, May 1, 2012 at 2:09 PM, scram69 <scram69 [at] gmail> wrote:
> On Thu, Mar 29, 2012 at 7:57 PM, Phil Bridges <gravityhammer [at] gmail> wrote:
>> On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean
>> <mtdean [at] thirdcontact> 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
>> 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
http://www.mythtv.org/mailman/listinfo/mythtv-users


scram69 at gmail

May 1, 2012, 10:20 PM

Post #10 of 18 (2538 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Tue, May 1, 2012 at 8:22 PM, Phil Bridges <gravityhammer [at] gmail> wrote:
> On Tue, May 1, 2012 at 2:09 PM, scram69 <scram69 [at] gmail> wrote:
>> On Thu, Mar 29, 2012 at 7:57 PM, Phil Bridges <gravityhammer [at] gmail> wrote:
>>> On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean
>>> <mtdean [at] thirdcontact> 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
>>> 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
> 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
http://www.mythtv.org/mailman/listinfo/mythtv-users


monkeypet at gmail

May 3, 2012, 8:13 PM

Post #11 of 18 (2528 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

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> wrote:

> On Tue, May 1, 2012 at 8:22 PM, Phil Bridges <gravityhammer [at] gmail>
> wrote:
> > On Tue, May 1, 2012 at 2:09 PM, scram69 <scram69 [at] gmail> wrote:
> >> On Thu, Mar 29, 2012 at 7:57 PM, Phil Bridges <gravityhammer [at] gmail>
> wrote:
> >>> On Thu, Mar 29, 2012 at 10:49 PM, Michael T. Dean
> >>> <mtdean [at] thirdcontact> 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
> >>> 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
> > 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
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>


sicrb25 at bigpond

May 3, 2012, 8:44 PM

Post #12 of 18 (2537 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

This also happened to me (still showing as recording when it's not bug) however my setup is completely different. 1x HDHR & 1x HD-PVR. Recording was from the HD-PVR, another thing I noted was if I am watching live TV on the HD-PVR and a recording is scheduled from the HD-PVR the usual "we need this tuner" message doesn't pop up, it didn't record but inserted the entry that wouldn't go away.

-rF

On 04/05/2012, at 1:13 PM, Monkey Pet wrote:

> 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> wrote:
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users


ron at ronfrazier

May 9, 2012, 6:09 PM

Post #13 of 18 (2450 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Thu, Mar 29, 2012 at 10:32 PM, Phil Bridges <gravityhammer [at] gmail> 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.


I also just got this same error now. I've got plenty of free space on
the recording drive (29GB, which is about where it always stays). I
can't find any info about any errors in dmesg or any of the logs.
smartctl is indicating no errors on any of the drives. I can't find
any sign of anything actually being wrong. There were only 2 shows
recording, and I routinely have 4 without issue.

Also, I experienced the same issue as Monkey Pet. After it failed,
myth continued to report that it was recording in the watch recordings
screen. The reported file size continued to increase, and when playing
it, myth continued to report the show growing longer. Now that the
recording is over, myth is reporting the entire 67 minutes, even
though it stopped after 29 minutes.

I'm running 0.25 fixes from Sunday morning.

So what could be causing this when I see absolutely no signs of any
issues other than myth claiming there were issues?


--
Ron Frazier
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dheianevans at gmail

Jul 6, 2012, 2:05 AM

Post #14 of 18 (2307 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Wed, May 9, 2012 at 9:09 PM, Ronald Frazier <ron [at] ronfrazier> wrote:
> Also, I experienced the same issue as Monkey Pet. After it failed,
> myth continued to report that it was recording in the watch recordings
> screen. The reported file size continued to increase, and when playing
> it, myth continued to report the show growing longer. Now that the
> recording is over, myth is reporting the entire 67 minutes, even
> though it stopped after 29 minutes.
>
> I'm running 0.25 fixes from Sunday morning.
>
> So what could be causing this when I see absolutely no signs of any
> issues other than myth claiming there were issues?

Seeing the same issue here...funnily enough it happened to the same
show (a midnight recording) over a three day period. All other
recordings throughout the days were fine.

Updated my 25-fixes this morning. Same issue with the file size/time
as above. Said I had a 31 minute 3.93 gig recording when it was a 14
minute 1.8 gig recording. Also, both times the show crapped out at 14
minutes. Again these were the only 2 recording to have this happen.

Jul 4 00:14:59 buster mythbackend[1552]: E HDHRStreamHandler
ThreadedFileWriter.cpp:216 (Write)
TFW(/storage1/video/1231_20120704000000.mpg:88): Maximum buffer size
exceeded.#012#011#011#011file will be truncated, no further writing
will be done.#012#011#011#011This generally indicates your disk
performance #012#011#011#011is insufficient to deal with the number of
on-going #012#011#011#011recordings, or you have a disk failure.
Jul 6 00:15:05 buster mythbackend[23096]: E HDHRStreamHandler
ThreadedFileWriter.cpp:216 (Write)
TFW(/storage1/video/1231_20120706000000.mpg:62): Maximum buffer size
exceeded.#012#011#011#011file will be truncated, no further writing
will be done.#012#011#011#011This generally indicates your disk
performance #012#011#011#011is insufficient to deal with the number of
on-going #012#011#011#011recordings, or you have a disk failure.

Bizarre that it's the same show/channel at the same time: 00:14.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


monkeypet at gmail

Jul 6, 2012, 8:30 PM

Post #15 of 18 (2282 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Fri, Jul 6, 2012 at 2:05 AM, Ian Evans <dheianevans [at] gmail> wrote:

> On Wed, May 9, 2012 at 9:09 PM, Ronald Frazier <ron [at] ronfrazier> wrote:
> > Also, I experienced the same issue as Monkey Pet. After it failed,
> > myth continued to report that it was recording in the watch recordings
> > screen. The reported file size continued to increase, and when playing
> > it, myth continued to report the show growing longer. Now that the
> > recording is over, myth is reporting the entire 67 minutes, even
> > though it stopped after 29 minutes.
> >
> > I'm running 0.25 fixes from Sunday morning.
> >
> > So what could be causing this when I see absolutely no signs of any
> > issues other than myth claiming there were issues?
>
> Seeing the same issue here...funnily enough it happened to the same
> show (a midnight recording) over a three day period. All other
> recordings throughout the days were fine.
>

Anything in your crontab launching to consume your disk bandwidth or cpu?


>
> Updated my 25-fixes this morning. Same issue with the file size/time
> as above. Said I had a 31 minute 3.93 gig recording when it was a 14
> minute 1.8 gig recording. Also, both times the show crapped out at 14
> minutes. Again these were the only 2 recording to have this happen.
>
> Jul 4 00:14:59 buster mythbackend[1552]: E HDHRStreamHandler
> ThreadedFileWriter.cpp:216 (Write)
> TFW(/storage1/video/1231_20120704000000.mpg:88): Maximum buffer size
> exceeded.#012#011#011#011file will be truncated, no further writing
> will be done.#012#011#011#011This generally indicates your disk
> performance #012#011#011#011is insufficient to deal with the number of
> on-going #012#011#011#011recordings, or you have a disk failure.
> Jul 6 00:15:05 buster mythbackend[23096]: E HDHRStreamHandler
> ThreadedFileWriter.cpp:216 (Write)
> TFW(/storage1/video/1231_20120706000000.mpg:62): Maximum buffer size
> exceeded.#012#011#011#011file will be truncated, no further writing
> will be done.#012#011#011#011This generally indicates your disk
> performance #012#011#011#011is insufficient to deal with the number of
> on-going #012#011#011#011recordings, or you have a disk failure.
>
> Bizarre that it's the same show/channel at the same time: 00:14.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>


dheianevans at gmail

Jul 7, 2012, 2:30 AM

Post #16 of 18 (2280 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Fri, Jul 6, 2012 at 11:30 PM, Monkey Pet <monkeypet [at] gmail> wrote:
> On Fri, Jul 6, 2012 at 2:05 AM, Ian Evans <dheianevans [at] gmail> wrote:
>> On Wed, May 9, 2012 at 9:09 PM, Ronald Frazier <ron [at] ronfrazier> wrote:
>> > Also, I experienced the same issue as Monkey Pet. After it failed,
>> > myth continued to report that it was recording in the watch recordings
>> > screen. The reported file size continued to increase, and when playing
>> > it, myth continued to report the show growing longer. Now that the
>> > recording is over, myth is reporting the entire 67 minutes, even
>> > though it stopped after 29 minutes.
>> >
>> > I'm running 0.25 fixes from Sunday morning.
>> >
>> > So what could be causing this when I see absolutely no signs of any
>> > issues other than myth claiming there were issues?
>>
>> Seeing the same issue here...funnily enough it happened to the same
>> show (a midnight recording) over a three day period. All other
>> recordings throughout the days were fine.
>
>
> Anything in your crontab launching to consume your disk bandwidth or cpu?

There's an rsync that runs every five minutes to check for updates to
a website I run. That's been running for about 8 months without any
issues. Last night's recording went off without a hitch. I guess I'll
watch over the next few days. It's a green drive...maybe my live TV
drive should be a faster one?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gravityhammer at gmail

Aug 15, 2012, 7:39 PM

Post #17 of 18 (2115 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Wed, May 9, 2012 at 9:09 PM, Ronald Frazier <ron [at] ronfrazier> wrote:
> On Thu, Mar 29, 2012 at 10:32 PM, Phil Bridges <gravityhammer [at] gmail> 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.
>
>
> I also just got this same error now. I've got plenty of free space on
> the recording drive (29GB, which is about where it always stays). I
> can't find any info about any errors in dmesg or any of the logs.
> smartctl is indicating no errors on any of the drives. I can't find
> any sign of anything actually being wrong. There were only 2 shows
> recording, and I routinely have 4 without issue.
>
> Also, I experienced the same issue as Monkey Pet. After it failed,
> myth continued to report that it was recording in the watch recordings
> screen. The reported file size continued to increase, and when playing
> it, myth continued to report the show growing longer. Now that the
> recording is over, myth is reporting the entire 67 minutes, even
> though it stopped after 29 minutes.
>
> I'm running 0.25 fixes from Sunday morning.
>
> So what could be causing this when I see absolutely no signs of any
> issues other than myth claiming there were issues?
>

Looks like I'm having these problems again. This time, Myth is trying
to write to a NFS-mounted drive. There is no notice of anything in my
messages log on either the master backend (which was recording) or the
slave backend (which had the physical drive).

As a side note - I've been running Myth for quite some time, and I
still have recording directories mounted on my master backend that
physically reside on my slave backend. Should I *not* have these in
the master backend's recording storage group, and only put them in the
slave backend's storage group?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gravityhammer at gmail

Aug 15, 2012, 7:43 PM

Post #18 of 18 (2117 views)
Permalink
Re: .25 - "Maximum buffer size exceeded" [In reply to]

On Wed, Aug 15, 2012 at 10:39 PM, Phil Bridges <gravityhammer [at] gmail> wrote:
> On Wed, May 9, 2012 at 9:09 PM, Ronald Frazier <ron [at] ronfrazier> wrote:
>> On Thu, Mar 29, 2012 at 10:32 PM, Phil Bridges <gravityhammer [at] gmail> 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.
>>
>>
>> I also just got this same error now. I've got plenty of free space on
>> the recording drive (29GB, which is about where it always stays). I
>> can't find any info about any errors in dmesg or any of the logs.
>> smartctl is indicating no errors on any of the drives. I can't find
>> any sign of anything actually being wrong. There were only 2 shows
>> recording, and I routinely have 4 without issue.
>>
>> Also, I experienced the same issue as Monkey Pet. After it failed,
>> myth continued to report that it was recording in the watch recordings
>> screen. The reported file size continued to increase, and when playing
>> it, myth continued to report the show growing longer. Now that the
>> recording is over, myth is reporting the entire 67 minutes, even
>> though it stopped after 29 minutes.
>>
>> I'm running 0.25 fixes from Sunday morning.
>>
>> So what could be causing this when I see absolutely no signs of any
>> issues other than myth claiming there were issues?
>>
>
> Looks like I'm having these problems again. This time, Myth is trying
> to write to a NFS-mounted drive. There is no notice of anything in my
> messages log on either the master backend (which was recording) or the
> slave backend (which had the physical drive).
>
> As a side note - I've been running Myth for quite some time, and I
> still have recording directories mounted on my master backend that
> physically reside on my slave backend. Should I *not* have these in
> the master backend's recording storage group, and only put them in the
> slave backend's storage group?

I have to alter this. The recording was being directed to a local
hard drive on the master backend.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.