Re: Still getting NFS client locking up
From: Matt Smith (matt_at_xtaz.co.uk)
Date: 11/10/03
- Previous message: Lukas Ertl: "named pipes memory leak?"
- Next in thread: Soren Schmidt: "Re: Still getting NFS client locking up"
- Reply: Soren Schmidt: "Re: Still getting NFS client locking up"
- Reply: Robert Watson: "Re: Still getting NFS client locking up"
- Maybe reply: Don Lewis: "Re: Still getting NFS client locking up"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 10 Nov 2003 14:50:11 +0000 To: Robert Watson <rwatson@FreeBSD.ORG>, Soren Schmidt <sos@spider.deepcore.dk>
With a current build from november the 9th I am still getting exactly
the same NFS lockups. I assume soren is as well. NFS has basically been
pretty unusable now for over a month.
As only a couple of people have complained about this from what I can
see I assume it is something related to something specific such as a
network card?
From my testing I only get this lockup when writing to the server.
Reading from the server works perfectly all the time. So luckily I can
still manage an NFS mounted installworld/kernel.
I just got the lockup again now whilst it downloaded p5-Net-DNS to
portupgrade into /usr/ports/distfiles. This is a very small file but it
was enough to trigger it off. So it doesn't look like a size related
issue either as I can download around 4% of mysql before it locks up.
Obviously we should really try and find the cause of this before 5.2. I
am willing to try any patches/debug on my systems. But I just have zero
clue about what to look for myself.
As a start here is the relevent parts of my dmesg to show the NIC's I'm
using. I wonder if this corresponds to sorens?
NFS CLIENT (xl1 would be the card it's using to talk to the server):
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xe400-0xe47f mem
0xea000000-0xea00007f irq 12 at device 15.0 on pci0
xl0: Ethernet address: 00:a0:24:ac:e1:b4
miibus0: <MII bus> on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl1: <3Com 3c905-TX Fast Etherlink XL> port 0xe800-0xe83f irq 11 at
device 17.0 on pci0
xl1: Ethernet address: 00:60:08:6d:1e:3b
miibus1: <MII bus> on xl1
nsphy0: <DP83840 10/100 media interface> on miibus1
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
NFS SERVER:
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x1000-0x107f mem
0xfc304800-0xfc30487f irq 10 at device 7.0 on pci5
xl0: Ethernet address: 00:04:76:8d:c5:fd
miibus0: <MII bus> on xl0
xlphy0: <3c905C 10/100 internal PHY> on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Both connected to a 100meg full duplex switch.
Any ideas? As I have said I'm happy to enable some major debugging etc.
But I just need somebody to give me a step by step guide for what to do
and look for.
In case this thread is too old now and nobody remembers anything about
it the previous email regarding it is at
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1183410+0+archive/2003/freebsd-current/20031102.freebsd-current
Regards, Matt.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Lukas Ertl: "named pipes memory leak?"
- Next in thread: Soren Schmidt: "Re: Still getting NFS client locking up"
- Reply: Soren Schmidt: "Re: Still getting NFS client locking up"
- Reply: Robert Watson: "Re: Still getting NFS client locking up"
- Maybe reply: Don Lewis: "Re: Still getting NFS client locking up"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
