Messages in this thread | | | Date | Mon, 02 Aug 1999 20:42:26 -0400 | From | bmccann@indusriv ... | Subject | NFS client may be broken in 2.2.11pre4 |
| |
I have three PC's running 2.2.11pre2, 2.2.11pre2, and 2.2.10, respectively. One (canopus) is an NFS server running 2.2.11pre2 and the other two, (antares and deneb) are NFS clients (mounting canopus) that run 2.2.11pre2 and 2.2.10, respectively.
I tried upgrading 'deneb' from 2.2.10 to 2.2.11pre4. I applied all three of Alan's patches, rebuilt, rebooted, you know the drill....
When it came back up, 'deneb' mounted 'canopus' NFS file system's but it could not access any files. /var/log/messages contains the following messages:
Aug 2 20:22:36 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41774 F=0x20B9 T=64 (#0) Aug 2 20:22:36 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41775 F=0x20B9 T=64 (#0) Aug 2 20:22:38 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41776 F=0x20B9 T=64 (#0) Aug 2 20:22:41 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41777 F=0x20B9 T=64 (#0) Aug 2 20:22:46 deneb kernel: nfs: server canopus not responding, timed out Aug 2 20:23:13 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41790 F=0x20B9 T=64 (#0) Aug 2 20:23:14 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41791 F=0x20B9 T=64 (#0) Aug 2 20:23:15 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41792 F=0x20B9 T=64 (#0) Aug 2 20:23:18 deneb kernel: eth0 PROTO=17 192.168.0.1:0 192.168.0.4:0 L=1500 S=0x00 I=41794 F=0x20B9 T=64 (#0) Aug 2 20:23:24 deneb kernel: nfs: server canopus not responding, timed out
I don't recognize this error but it only occurs with NFS. I was still able to ping and telnet from 'deneb' to 'canopus'. Also note NFS doesn't appear totally dead. My 'home' directory is NFS mounted and I was able to log in and run my .tcshrc, .login, etc... I didn't get into this state until I tried to start X. (Of course, everything works fine with 2.2.10 so I don't believe it is a configuration problem).
For tonight, I'm backing off to 2.2.10 on 'deneb'. Tommorrow I'll see if the same problem occurs with my other NFS client (running 2.2.11pre2) when I upgrade it to 2.2.11pre4.
Please send mail directly if there is something else I should try.
-Ben McCann -- --- Ben McCann Indus River Networks 31 Nagog Park Acton, MA, 01720 email: bmccann@indusriver.com web: www.indusriver.com phone: (978) 266-8140 fax: (978) 266-8111
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |