Arch Linux

RedShift

Member

From: Belgium

Registered: 2004-07-16

Posts: 230

Strange networking/NFS problem

Hello,

Occasionaly I'm having NFS slowdowns, then I see this information in dmesg on the client:

nfs: server galaxy2 not responding, still trying
nfs: server galaxy2 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server galaxy2 OK
nfs: server galaxy2 OK
nfs: server galaxy2 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server galaxy2 OK
nfs: server galaxy2 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server galaxy2 OK
nfs: server galaxy2 not responding, still trying
nfs: server galaxy2 not responding, still trying
nfs: server galaxy2 OK
nfs: server galaxy2 OK

But on the server, I see nothing in dmesg. But, I do see this:

eth0      Link encap:Ethernet  HWaddr 00:0E:0C:72:83:51
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:185954 errors:774 dropped:774 overruns:774 frame:0

(notice the high errors/dropped/overruns)

The LAN is a GigaBit lan, on the server:
00:09.0 Ethernet controller: Intel Corp.|82547EI Gigabit Ethernet Controller (e1000)
on the client:
00:0a.0 Bridge: nVidia Corp.|Ethernet controller (forcedeth)

The entry in rc.conf for the network looks like this:
client:
eth0="eth0 192.168.1.102 netmask 255.255.0.0 broadcast 192.168.1.255"
server:
eth0="eth0 192.168.1.1 netmask 255.255.0.0 broadcast 192.168.1.255"

Is this an NFS problem or a networking problem??

Thanks.

---

:?

mercy

Member

Registered: 2004-04-24

Posts: 62

Re: Strange networking/NFS problem

netmask should be 255.255.255.0 according to your broadcast

y should also have a look at network-components before your server also an easy one would be to change the cable

once our database was instable due to a cable-problem (was fine for 6 months before)