Re: NFS timeouts (Solaris 9 and Solaris 10)

From: Sami Ketola (Sami.Ketola_at_iki.finland.invalid)
Date: 11/10/05 

Date: Thu, 10 Nov 2005 20:38:38 -0000

Carsten Benecke <Carsten.Benecke@rrz.uni-hamburg.de> wrote:
> Hmm,
>
> you are right, proto=tcp had been ignored, but -o proto=tcp,vers=3 does
> not make a difference. I still run into timeouts.
>
> On the other hand, -o proto=udp,vers3 now succeeds on both Sol 9 an Sol
> 10...
>
> So maybe tcp-transport is the default; but it should work with either
> tcp or udp, shouldn't it?

Yes. It's supposed to work with both tcp and udp. Without more data it's still
impossible to say if it's a problem with the server or the client.
please try snooping network traffic while doing ls to get more idea
where it goes wrong.

Sami 

-- 
  .signature: no such file or directory

Relevant Pages

  • NFS problem with recent 2.6 kernels (also serial console weirdness)
    ... 100000 2 tcp 111 portmapper ... 100000 2 udp 111 portmapper ... mounted filesystem with ordered data mode. ... Mounted root (ext3 filesystem) readonly. ...
    (Linux-Kernel)
  • Solaris 9 <---> linux (2.6.8) NFS file locking problem?
    ... to the same file placed on nfs filesystem. ... 100000 4 tcp 111 portmapper ... 100000 4 udp 111 portmapper ... 100021 1 udp 4045 nlockmgr ...
    (SunManagers)
  • Urgent help with Secure NFS.
    ... have that option - I'm just attempting to tunnel all NFS traffic to the ... 100000 4 tcp 111 rpcbind ... 100000 4 udp 111 rpcbind ... 100021 1 tcp 49153 nlockmgr ...
    (SSH)
  • Re: nfs error
    ... kernel: nfs: server ... So if your system uses ypbind be sure that is working properly before ... 100000 2 tcp 111 portmapper ... 100000 2 udp 111 portmapper ...
    (comp.sys.sun.admin)
  • Re: Incoherent E-mails
    ... The Novell crap was originally run on IPX ... The term in the early-mid nineties was "packet storm". ... The original advantage of UDP was ... > 60 bytes for TCP. ...
    (alt.computer.security)