Date: Thu, 3 Jan 2002 12:12:38 -0800 (PST) From: Eric Anderson <anderson@centtech.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/33515: amd incorrectly handles multi-homed nfs servers - causing failures Message-ID: <200201032012.g03KCcX53390@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 33515
>Category: bin
>Synopsis: amd incorrectly handles multi-homed nfs servers - causing failures
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jan 03 12:20:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Eric Anderson
>Release: FreeBSD RELEASE 4.x
>Organization:
Centaur Technology
>Environment:
FreeBSD proton.centtech.com 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Fri Sep 7 09:42:10 CDT 2001 root@proton.centtech.com:/usr/src/sys/compile/PROTON i386
>Description:
I have a FreeBSD client on net A, and a multi-homed NFS server (running Linux, or
Solaris, take your pick) on nets A and B. If I attempt to access the server
with automounter (amd) via the interface that is NOT on my net (A), it times
out, responding with:
nfs server pid226@clienthostname:/net: not responding
nfs server pid226@clienthostname:/net: is alive again
ls: /net/inside/usr2: No such file or directory
Also, this may be unrelated, but it's still odd (and probably somehow
exploitable). Hard to explain, but I'll do my best.
If, on a client, I try to do a 'cd /net/server1/' to a NIC (on the server) that
will timeout (as mentioned above), and as soon as it starts timing out, I do
ctrl-C to break from it, and open another window and do a 'cd
/net/server2/share/', when the first 'cd' command finally breaks, it will drop
to a /net/server2/share/ directory, instead of the original working directory..
So it sounds kind of like the NFS handles are being reused too quickly or
something like that.
>How-To-Repeat:
On a FreeBSD 4.x client (with NFS client and amd enabled), access an automount on a server that is on two networks. You must access the nic that is NOT on the same network as the client.
This has been mentioned before, but has not been corrected. See PR # 4705.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201032012.g03KCcX53390>