Date: Mon, 17 Dec 2001 21:39:49 +0000 From: ian j hart <ianjhart@ntlworld.com> To: "Marius M. Rex" <marius@malkav.snowmoon.com> Cc: questions@freebsd.org Subject: Re: on/off NFS connection errors Message-ID: <3C1E6625.35C7D88@ntlworld.com> References: <20011217120545.D48149-100000@malkav.snowmoon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[cross post deleted] "Marius M. Rex" wrote: > > For a while I have been treating this as an annoyance, but I thought it > would be wise to investigate if something larger and more nefarious might > be being indicated by this. > > I have a mixed environment of mainly Linux boxen, with a dozen or so > FreeBSD machines (For when we need the kind of network resources that > raising the NMBCLUSTERS can offer.) Both types of systems serve mainly as > webservers, serving content that ultimately comes off of exported NFS > directories, from a Network Appliance (NetApp Release 5.3.4R3: Thu Jan 27 > 12:08:07 PST 2000) The Linux boxen don't complain at all, but the FreeBSD > boxen can get rather noisy about NFS connection errors. It happens > on and off like so: > > ><118>Dec 15 21:01:47 cc117 /kernel: nfs server netapp1:/vol/members: not > >responding > ><118>Dec 15 21:01:47 cc117 /kernel: nfs server netapp1:/vol/members: is > >alive again > ><6>nfs server netapp1:/vol/members: not responding > ><6>nfs server netapp1:/vol/members: is alive again > ><118>Dec 15 22:34:19 cc117 /kernel: nfs server netapp1:/vol/members: not > >responding > ><118>Dec 15 22:34:19 cc117 /kernel: nfs server netapp1:/vol/members: is > >alive again > ><6>nfs server netapp1:/vol/members: not responding > ><6>nfs server netapp1:/vol/members: is alive again > ><118>Dec 15 22:39:19 cc117 /kernel: nfs server netapp1:/vol/members: not > >responding > ><118>Dec 15 22:39:19 cc117 /kernel: nfs server netapp1:/vol/members: is > >alive again > ><6>nfs server netapp1:/vol/members: not responding > ><6>nfs server netapp1:/vol/members: is alive again > ><118>Dec 15 22:40:19 cc117 /kernel: nfs server netapp1:/vol/members: not > >responding > ><118>Dec 15 22:40:19 cc117 /kernel: nfs server netapp1:/vol/members: is > >alive again > > One moment we are connected, another we are down, and the we are back up > again. Some days I can get pages and pages of this, others very little. > Luckily the connection error is so short lived that Apache never hiccups. > > Has anyone else seen these kinds of persistent NFS errors is the 4.x > branch? (This didn't happen noticeably in 3.x, but I would still > maintain that the NFS code in 4.x is an improvement over 3.x.) Can anyone > suggest a sysctl/kernel variable I might tune to help remedy the problem? > If the root of the problem is more likely on the Netapp side, I have a support > contact and am not afraid to use it. Anyone have any advice or > suggestions to offer? > > This is the platform that I am working on: > FreeBSD cc117 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Aug 18 00:21:16 EDT > 2001 root@cc117:/usr/src/sys/compile/CCI_KERNEL i386 > > ------------------------------------------------------------------------- > Marius M. Rex > > Hardware: n. The parts of a computer that can be kicked. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Yes I've seen this (4.1 RELEASE/STABLE). Summer 2000 I used the install floppies to distribute Win95 "ghost" images to all our workstations, NFS mounting the source and untaring to the DOS partition. With 20 or so P200's these messages would be quite common. I put this down to the hubs being saturated. These were OfficeConnect 10BaseT. ie not cheap not cheerfull. The 8 port unit is particularly easy to "peg". This summer (4.3 STABLE) I saw very few occurances but half our network has been upgraded to 100BaseT switches. This is even though a third of the machines were also upgraded (700MHz). What's your network hardware? Try watching the idiot lights on the hubs. [please cc me, I only read stable] -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C1E6625.35C7D88>