The only NFS problems I've really ever had w/ OpenBSD, is if our NFS server goes down or is rebooted, the NFS mount never comes back and will essentially hang (especially if you try to unmount the stale link)... I've never tried a mount -u or a unmount -f tho...

Federico Giannici wrote:
I have an MX mail server that receives email messages and saves them to
an email storage server via NFS.

Both pc are OpenBSD i386, version 3.7 for the NFS client (MX server) and
3.4 for the NFS server (the storage server).

 From time to time the connections from the NFS clients seem to freeze
(at least the new ones).

I applied the famous NFS patch that disables write gathering for v3
(http://marc.theaimsgroup.com/?l=openbsd-misc&m=110676811107986&w=2),
but the problem remains (perhaps a little less frequent).

I have also raised the number of nfsd processes and "vfs.nfs.iothreads" to 20.

The server uses a fxp interface and the client an sk one. From "netstat -i" I have seen that there are no errors or collisions.

Here is the nfsstat output for the client and the server after almost a day of uptime:

Client Info:
Rpc Counts:
Getattr Setattr Lookup Readlink Read Write Create Remove 136400 12 429651 0 13653 178549 25790 25819 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 5415 20016 0 16 0 336388 0 1359316
    Mknod    Fsstat    Fsinfo  PathConf    Commit
        0     27008         1         0     42530
Rpc Info:
 TimedOut   Invalid X Replies   Retries  Requests
        4         0       139     28889   2600564
Cache Info:
Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 1669083 136400 1239823 424253 67080 13653 632860 178549
BioRLHits    Misses BioD Hits    Misses DirE Hits    Misses
        0         0         0         0     26996     27954


Server Info:
Getattr Setattr Lookup Readlink Read Write Create Remove 90847 0 269426 0 8882 137000 16908 16947 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 3263 13427 0 0 0 197032 0 872760
    Mknod    Fsstat    Fsinfo  PathConf    Commit
        0     16594         0         0     28598
Server Ret-Failed
            65447
Server Faults
            0
Server Cache Stats:
   Inprog      Idem  Non-idem    Misses
       21     14256       920   1657428
Server Write Gathering:
 WriteOps  WriteRPC   Opsaved
   136997    137000         3


What make me worry is the hight value of the "Ret-Failed" field.
Is it normal?

I have no experience of NFS, is it normal that sometime ot stalls?
What else I could do to prevent this to happen?


Thanks.


--
Tony Lambiris [ [EMAIL PROTECTED] ]
"so if it is really hard for you then perhaps you are just
retarded and need treatment w/ electricity and if that does
not help then perhaps should not use computers..."

Reply via email to