[mythtv-users] MythTV, seeking ahead / behind, NFS, and bandwidthusage

[Blammo[doh]]

Good call, that's what it turned out to be. Odd because it was one of the
only two things not working right, would have expected more to break.



----- Original Message ----- 
From: "David" <myth at dgreaves.com>
To: "Discussion about mythtv" <mythtv-users at mythtv.org>
Sent: Thursday, August 05, 2004 3:22 PM
Subject: Re: [mythtv-users] MythTV, seeking ahead / behind, NFS, and
bandwidthusage


> I think this may be because your frontend doesn't see the backend mysql
> and can't read the recordedmarkup table which stores the GOP info that
> allows quick seeking?
>
> When you hit pause/unpause does the osd show a varying (and wrong) length?
>
> I fixed this once ages ago and didn't know why!
> Now I do :'-(
>
> David
> PS subject close to my heart ATM :)
>
> Blammo[doh] wrote:
>
> >Update:
> >
> >problem not solved. Still happening.
> >
> >Think it's a frontend problem. Load on the front end goes to 1.5 - 1.6
> >during a 16x seek, while the load on the backend, NFS server, is.. well,
> >nothing.. 0.00
> >
> >thanks all for posting hdparm speeds. Gives me something to compare /
> >justify upgrading:
> >
> >root at backend1:~ # hdparm -t /dev/hda4
> >
> >/dev/hda4:
> > Timing buffered disk reads:  64 MB in  1.16 seconds = 55.17 MB/sec
> >
> >
> >
> >----- Original Message ----- 
> >From: "Blammo[doh]" <blammo at dohboys.com>
> >To: <mythtv-users at mythtv.org>
> >Sent: Monday, August 02, 2004 8:25 AM
> >Subject: Re: [mythtv-users] MythTV, seeking ahead / behind, NFS,and
> >bandwidth usage
> >
> >
> >
> >
> >>Thank you all for your feedback, both emailed, and on the list.
> >>
> >>The backend has a single 160gig UDMA6 HD (dma on), hooked on the onboard
> >>
> >>
> >IDE
> >
> >
> >>controller on the A7N8X deluxe. hdparm -t /dev/hda gives about 55 meg,
> >>
> >>
> >which
> >
> >
> >>should be more than enough for a single frontend.
> >>
> >>On a whim, I tried changing the file system last night, and VOILA!!
> >>
> >>It was EXT3, it's now XFS. Problem solved.
> >>
> >>I guess, in an odd way, it makes sense, but it sure presented in an
> >>
> >>
> >unusual
> >
> >
> >>way.
> >>
> >>Out of curiousity, can a couple of you with multi-drive backends, run
the
> >>hdparm -t so I can see how much of a difference it makes? I'm sure other
> >>people are curious about it as well.
> >>
> >>thanks
> >>
> >>----- Original Message ----- 
> >>From: "Jim Sager" <jim.sager at turner.com>
> >>To: "Discussion about mythtv" <mythtv-users at mythtv.org>
> >>Sent: Monday, August 02, 2004 6:58 AM
> >>Subject: Re: [mythtv-users] MythTV, seeking ahead / behind, NFS,and
> >>bandwidth usage
> >>
> >>
> >>
> >>
> >>>I had this same problem when I created a frontend system and connected
> >>>
> >>>
> >it
> >
> >
> >>to
> >>
> >>
> >>>my masterbackend system. I found that my settings in myth were the
> >>>
> >>>
> >>problem. I
> >>
> >>
> >>>have a NFS share created on my masterbackend and mounted it to
> >>>
> >>>
> >/mnt/store
> >
> >
> >>on
> >>
> >>
> >>>my frontend. I had to run mythsetup on the frontend and change the "IP
> >>>address for <frontend hostname>" to my frontend's ip address and
"Master
> >>>server ip address" to the masterbackend's ip address. I also changed
the
> >>>"Directory to hold recordings" setting to point to my mounted NFS
share,
> >>>"/mnt/store". Once I made these changes I no longer had the seek delays
> >>>
> >>>
> >>that
> >>
> >>
> >>>I had been experiencing. I am streaming my video from the backend to
the
> >>>frontend using wireless-g (54Mbps - approx.).
> >>>
> >>>Hope this helps.
> >>>
> >>>-- 
> >>>jim
> >>>_______________________________________________
> >>>
> >>>
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
>
>


----------------------------------------------------------------------------
----


_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users