Date: Thu, 20 Dec 2001 16:24:15 -0600 From: Eric Anderson <anderson@centtech.com> To: freebsd-questions@freebsd.org Subject: amd / multi-homed nfs servers - not responding? Message-ID: <3C22650F.95482042@centtech.com>
next in thread | raw e-mail | index | archive | help
Ok, this is a weird issue I'm having with FreeBSD clients (4.2, 4.3). 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 It only seems to happen with NFS servers that have a NIC on the same net as the FreeBSD client AND a NIC on a different net. 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. Anyone have any ideas? Anybody seen this? Eric -- ------------------------------------------------------------------ Eric Anderson anderson@centtech.com Centaur Technology If at first you don't succeed, sky diving is probobly not for you. ------------------------------------------------------------------ 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?3C22650F.95482042>