G'day all,

I have an issue where NFS fails after a while.
I have some disks that I mount from another machine over NFS, they mount OK and are useable but after awhile the mounts hang when trying to access them.

Any suggestions?

_________________
--
stinga

as of 17-May-2018
R8.2 - sort of working.
MB: gigabyte GA-P43-ES3G | RAM: 2GB
VGA: PNY Nvidia GT240 1GB
4 x Technisat skystar 2 dvb | 1 x TBS6981 dvb-s2
pata: 1x300Gb | sata: 2x1Tb 2x2Tb
Problems:
TBS6981 Does not work.

I would start by looking at your log files and see if there are any clues there.

Martian

_________________
ABIT NF-M2 nView | Athlon 64 X2 3800+ | 2GB DDR2 800 | HDHomerun | GeForce 6150 (onboard) | WD 640 GB SATA HD | DVD-RW (sata) | StreamZap IR receiver with Logitech Harmony remote

Vizio 37" LCD HDTV (1080p)

You could try using automount to control NFS mounts so they are only mounted when needed.

https://wiki.archlinux.org/index.php/Autofs

_________________
The Atomic Ant.

G'day all,

Nothing in the logs.

automount is an abomination and should be avoided at all costs!
Would not help, since it fails during use.

I solved the problem, brought a bigger disk and moved it locally so I no longer need to NFS mount.

I think there must be an incompatibly between version somewhere since I have another box with nfs mounted disks and that does exibit the same problem. That box is a lot older.

_________________
--
stinga

as of 17-May-2018
R8.2 - sort of working.
MB: gigabyte GA-P43-ES3G | RAM: 2GB
VGA: PNY Nvidia GT240 1GB
4 x Technisat skystar 2 dvb | 1 x TBS6981 dvb-s2
pata: 1x300Gb | sata: 2x1Tb 2x2Tb
Problems:
TBS6981 Does not work.

That first statement is not correct, but I suppose it depends on your definition of "the problem"

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************

Gee bob my car keeps stalling so I bought a new engine.
Yep that fixed it your car wont stall anymore.
In terms that I deal with (SAF) that was a fix for the problem.

_________________
My System

Just thought that I would post that I have a similar issue sometimes while access my FreeNAS NFS mount. I only tend to get this freezing problem when I am doing a lot of copying to and from my NAS server. My Myth box is the only PC making an NFS connection to the NAS so I had always assumed it was a problem with the NAS. No real reason for that assumption, other than I didn't have any other problems with the Myth box. Though I also haven't had any other problems with the NAS.

_________________
Tim

LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT

I'm having NFS connection failures using R6.03.00

Looking back through "messages.log" this entry is the first one about two hours after the last reboot.

messages.log:Feb 13 20:03:37 Mythtv-LR nfs: server 192.168.1.15 not responding, still trying

Can't find anything significant in any other logs except I notice a commercial flagging job started shortly before.

mythtv/mythbackend.log:2011-02-13 20:03:28.280 JobQueue: Commercial Flagging Starting for CSI: Miami "Going Under" recorded from channel 65031 at Sun Feb 13 20:00:00 2011

In my previous R5F1 system the comflag jobs didn't start until after the recording finished. The recordings are on the local HD. the NFS mounts are only used for Videos & Music. Here's my fstab :-

# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sr0 /media/cdrom auto ro,user,noauto,unhide 0 0
UUID=33d197dd-a8ab-4d59-a3b0-55f1d05d6d38 / auto defaults,noatime 0 1
UUID=3ff11744-11fa-4dda-bd11-f6b7f1ca24e1 /myth auto defaults,noatime 0 1
UUID=405a5a3b-728f-426d-bc5f-b0ef2a817024 swap swap defaults 0 0
# mountpoints on ReadyNAS
192.168.1.15:/Media/mythtv/video /myth/video nfs nfsvers=3,tcp,noatime,intr
192.168.1.15:/Media/mythtv/music /myth/music nfs nfsvers=3,tcp,noatime,intr
#STARTSCRUB --------------anything in this block will be scrubbed
#ENDSCRUB

Could the comflag job be the problem, or is there somthing wrong with my NFS mount statements ? The NFS is a ReadyNAS NV+ with plenty of space.


Pete

After a bit more searching on ReadyNAS forums I have changed the NFS server config to "async" mode, and increased the NFS threads from 1 to 4.

So far seems to keep the connection up, but will see over the next day or so.

UPDATE - still getting NFS failures. Not sure if it's the Myth box or the ReadyNAS.

Pete