SUMMARY: Problems with NFS between v5.0 and v5.1

From: Jan Brueninghaus (Jan_at_Brueninghaus-online.de)
Date: 05/19/04

  • Next message: Minkov, Ross: "replacing a failed lsm disk" 
    Date: Wed, 19 May 2004 18:05:02 +0200
To: tru64-unix-managers@ornl.gov

    Thanks all for helping!

    Problem:
    NFS-Client Tru64 v5.1 with NFS-Server Tru64 v5.0
    Accessing data larger than a few kB fails.

    errors in messages on the client:
    May 18 22:47:25 omega vmunix: NFS3 server delta not responding still trying
    May 18 22:47:37 omega vmunix: NFS3 server delta ok
    May 18 22:47:38 omega vmunix: NFS3 server delta not responding still trying

    errors in messages on the server:
    May 18 22:47:23 delta vmunix: svckudp_send: xdr_replymsg failed
    May 18 22:47:23 delta vmunix: rfs_dispatch: sendreply failed IP address:
    129.217.226.24

    All other network operations work fine, even a NFS-import from Tru64 v4.0E
    works without problems.

    Solution:
    John Lanier recommended to check if NFS is working over UDP or TCP, because
    there are patches for v5.0 for NFS over TCP.
    By checking out this with "mount -l -t nfs" i notices that wsize and rsize
    were different. The NFS-import from v4.0E had wsize=8192 and rsize=8192,
    but the NFS-import from v5.0 had wsize=32768 and rsize=32768. So I changed
    this to wsize=8192 and rsize=8192 and everything works fine.

    It seems that Tru64 v5.1 had used this options automatic, because I mounted
    without giving wsize and rsize. But adding this for the imports from v5.0
    solves the problem.

    Regards 

    --
Jan Brüninghaus
Universität Dortmund
Jan@Brueninghaus-online.de
  • Next message: Minkov, Ross: "replacing a failed lsm disk"