[mythtv-users] Trashed file system after "Video frame buffering failed too many times"

[John Pilkington]

The GUIGuy wrote:
> I'm running mythbuntu 9.10 (0.22), Assume combined front/backend.
> 
> 
> A couple of weeks ago "Video frame buffering failed too many times" 
> errors started to pop up. Logs complained that files couldn't be written 
> because the FS was read only. On a reboot I had to fsck /dev/sda1. A 
> number of files finished up being trashed so I suspected the HDD was on 
> its way out.
> 
> I replaced the HDD (new) and did a fresh install. All was well until a 
> few days ago. Same "Video frame buffering failed too many times". Logs 
> again suggested something was very sick on the HDD. Tried to reboot and 
> it tells me it couldn't because the file system was read only!!??
> 
> I held the  big button down for a few seconds. On the boot had to do the 
> fsck /dev/sda1 again. The feed back wasn't good lots of "corrupted file" 
> messages.
> 
> Another HDD, another clean install, another week, same problem started 
> again tonight.
> 
> Is there something in MythTV that could be trashing the file system?
> 
> 
I've had a few occasions recently when my system was affected by a 
creeping paralysis and couldn't reboot properly because most devices 
were busy.  Only way out by power-off.  Does your backend log show any 
IOBOUND messages?  My events seemed to be caused by multirecording plus 
disk-intensive processing.  I've changed the kernel scheduler 
(escalator=deadline), used 'nice' and 'ionice' where I could and tried 
to avoid processing at peak times, but I'm not entirely happy. 
0.22-fixes, f10.x86_64.

John P