Bug 4467
Summary: | NFS and Network Appliance (NetApp) lose contact | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | sandman |
Component: | nfs-server | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | luke, vancleef, vijay |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-15 04:24:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sandman
1999-08-10 23:53:19 UTC
What kernel and what knfsd are you running? You migh try the latest kernel and knfsd from Raw Hide -- NFS has changed some from virgin Red Hat 6.0 binaries ... Hi, We downgraded to RH 5.2. However, to use 1G memory we need to upgrade the kernel back to 2.2.5. The nfs-server version is 2.2beta37-1 We still experienced the same nfs errors. So looks like there is some problem with the new 2.2.5 kernel. Any ideas? New results: We nfs mounted a 5.2 linux (2.2.5) machine partition (/data1) to the 5.2 linux (2.0.6) machine as /data. We loaded the cpu by doing a recursive copy of /usr to a /data/xyz. We still get the errors: Aug 17 05:45:14 hotweb006 kernel: NFS server hotweb001 not responding, still try ing. Aug 17 05:45:14 hotweb006 kernel: NFS server hotweb001 OK. Aug 17 05:48:18 hotweb006 kernel: NFS server hotweb001 not responding, still try ing. Aug 17 05:48:18 hotweb006 kernel: NFS server hotweb001 OK. You can easily reproduce this. I have not tried a 5.2(2.0.6) to 5.2(2.0.6) mount yet. Just tested 5.2 (2.0.6) with 5.2 (2.0.6) nfs mounts and the same error occurs. However, in this case the erorr is for a split second only. This problem has impacted our systems also. When it strikes, all processes using NFS files systems are effectively hung until whatever is happening runs its course. Feb 9 11:55:01 arwin kernel: NFS: server iris, readdir reply truncated Feb 9 11:55:01 arwin kernel: NFS: nr=38, slots=3, len=7 I would like to see the priority on this bumped up a notch or two. |