Thanks!!!

-----Original Message----- From: Kade, Mike [mailto:Mike.Kade@netapp.com] Sent: Wednesday, March 12, 2003 11:06 AM To: tom.felbinger@synopsys.com Subject: RE: Weired Linux error

Oops... Here it is.

http://www.fys.uio.no/~trondmy/src/

Mike

---------------------------------------------------------------------------- ------- Serving Data By Design - Network Appliance, Inc

Michael Kade Technology Evangelist (480) 510-8002 mkade@netapp.com

-----Original Message----- From: Tom Felbinger [mailto:tom.felbinger@synopsys.com] Sent: Wednesday, March 12, 2003 8:48 AM To: Kade, Mike Subject: RE: Weired Linux error

Mike,

Thanks, but I'm not finding the link you mentioned.

Just to be clear, all my nfs mounts are thru the automounter, both autofs and amd. autofs uses udp by default, but amd used tcp by default. I modified the /etc/amd.net file to use udp instead.

If memory serves me correctly, I did interactively mount the filer using tcp and still encountered the data corruption.

I've very interested in resolving this and look forward to the link.

Thanks to all for their input.

Tom

-----Original Message----- From: Kade, Mike [mailto:Mike.Kade@netapp.com] Sent: Tuesday, March 11, 2003 3:18 PM To: tom.felbinger@synopsys.com Subject: RE: Weired Linux error

Tom,

The following link is for the approved patches for NFS (this is the home website for the developer/maintainer of Linux NFS). A lot of these patches were actually done by NetApp. NetApp has spent quite a bit of time looking at Linux issues with NFS over the last year. A lot of this work shows up in these patches.

Regards,

Mike

---------------------------------------------------------------------------- ------- Serving Data By Design - Network Appliance, Inc

Michael Kade Technology Evangelist (480) 510-8002 mkade@netapp.com

-----Original Message----- From: Tom Felbinger [mailto:tom.felbinger@synopsys.com] Sent: Tuesday, March 11, 2003 7:04 AM To: toasters@mathworks.com Subject: RE: Weired Linux error

A couple folks mentioned running NFS over TCP for linux.

However, I've encountered data corruption (i.e. running a filer hosted binary will core dump) with RH 7.1 and 7.2 with NFS over TCP. Is there some patch/kernel rev/something I need to apply???

I stopped pursuing this because RedHat and NetApp said this was a known issue. Sounds like some people have it working though.

Tom

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Steve Losen Sent: Monday, March 10, 2003 6:04 PM To: toasters@mathworks.com Subject: Re: Weired Linux error

A few RedHat 7.2 nfs clients mounting a F840 volume via automount error

out with

the following. I have looked into everyting including NIS timeouts, filer sysstat, network performance and everything looks to be fine. Intrestingly

all

the other non linux Clients accessing the same auto-mount are working

perfectly.

Mar 9 06:35:12 linuxclient kernel: nfs: server filer OK Mar 9 06:35:13 linuxclient last message repeated 52 times Mar 9 06:35:31 linuxclient kernel: nfs: server filer not responding,

still

trying Mar 9 06:35:41 linuxclient kernel: nfs: server filer OK Mar 9 06:35:54 linuxclient kernel: nfs: server filer not responding,

still

trying Mar 9 06:36:34 linuxclient kernel: nfs: server filer OK Mar 9 06:36:46 linuxclient kernel: nfs: server filer not responding,

still

trying Mar 9 06:38:36 linuxclient kernel: nfs: task 41929 can't get a request

slot

Mar 9 06:38:41 linuxclient kernel: nfs: task 43328 can't get a request

slot

Be sure you are mounting with the "tcp" flag. We have found that a Linux NFS v3 client using udp has this problem, but it goes away if you use tcp. I think Linux defaults to udp.

You may need to enable tcp on the filer with

options nfs.tcp.enable on