[mythtv-users] NFS and remote backend

Patrick Ouellette pat at flying-gecko.net
Mon Jan 14 18:05:15 UTC 2008

On Mon, Jan 14, 2008 at 12:03:43PM -0500, Ryan Steffes wrote:
> Date: Mon, 14 Jan 2008 12:03:43 -0500
> From: Ryan Steffes <rbsteffes at gmail.com>
> Subject: Re: [mythtv-users] NFS and remote backend
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> >
> > Are you running two NICs in the master box (one on the gigabit lan and
> > one on the 100 mega bit lan) or are you relying on a combination switch
> > (10/100/1000) to handle the different bit rate conversion?
> >
> > Pat
> > --
> I'm running through a D-Link firewall/router to handle it.

So you are expecting an NFS client set for 8K blocks to work well on a
network with a server and another client set at 32K blocks.  I wonder if
that has anything to do with it.

Then there is the latency for the switch to fragment the gigabit traffic
for the 100 megabit client, and the overhead of the 100 megabit client
reassembling the fragmented traffic.  While these might be small amounts
of time per packet, they add up.

I know the older NFS client/servers had issues with block sizes over 8K, but I
admit I haven't checked into it recently.

Personally, I'd try adding a separate 100 megabit nic to the server for
the slower network and configuring an NFS server on that interface for
8K blocks. 


Patrick Ouellette                 pat at flying-gecko.net
kb8pym at arrl.net                   Amateur Radio: KB8PYM 
Living life to a Jimmy Buffett soundtrack
"Crank the amp to 11, this needs more cowbell - and a llama wouldn't hurt either"

More information about the mythtv-users mailing list