[mythtv-users] strange NFS problem

[Jason G.]

Hi Jack,

(ooh, don't say that at an airport... :)

I've got a NFS based system for my myth box.  I had quite a few NFS related
troubles along the way.  There were some settings that seemed important (at
least for NFS root) to my setup.  My notes are here:
    http://home.comcast.net/~sredni.vashtar/mythtv/myth.html#nfs

You may find some (or none) of the information helpful.  I'm betting that
Keith was correct in suggesting that it was the commercial flagging that was
inducing what you were seeing, but I figured I'd chime in with my
NFS-related experiences.

Jason



> Hi everyone
>
> Finally got my Mythbox working.
> Very impressive piece of work!
>
> Using Myth 0.14 on Fedora 1
> Fileserver runs freebsd 4.8
>
> I store my recordings using NFS.
> Mounting line in /etc/fstab :
>
> 192.168.2.111:/muziek1  /mnt/nfs                nfs
> udp,rsize=8192,wsize=8192,hard,nfsvers=3
>
> This works fine with normal file copying...
>
> But NOT when using Myth:
> When A scheduled recording ends my network stays under heavy load.
> (10 base T 80 -90%). I checked and Mythbackend says 'changing from
> recordingonly to none.
>
> BTW Recorded file is fine!
>
> This heavy network activity stops when I close Mythbackend.
> Then everything is back to normal.
>
> I used Ethereal to do some sniffing, and this is wat it sees:
> 192.168.2.104 = MythMachine
> 192.168.2.111 = BSD server
>
> First during NORMAL recordings.
>
> 0.007241 192.168.2.104 -> 192.168.2.111 IP Fragmented IP protocol
> (proto=UDP 0x11, off=1480)
...
> 0.046993 192.168.2.111 -> 192.168.2.104 NFS V3 WRITE Reply (Call In
> 26) Len:8192 UNSTABLE
>
> And then AFTER recording has finished:
>
> 116.897668 192.168.2.104 -> 192.168.2.111 NFS V3 READ Call,
> FH:0x0589ad16 Offset:34922496 Len:8192
...
> 116.906223 192.168.2.104 -> 192.168.2.111 NFS V3 READ Call,
> FH:0x0589ad16 Offset:34938880 Len:8192
>
> This doesn't stop :-(
>
> It gets even stranger:
> When I decide to stop an ongoing recording by hand, there is no
> problem. Networkactivity stops.
>
> Does anyone know this problem?
> It seems Myth related because copying a file works fine?
> Maybe there's a sort of a work around, restart the backend if a
> recording finished?
>
> TIA Jack