[1660] in NetBSD-Development
Re: Problems galore
daemon@ATHENA.MIT.EDU (Nathan J. Williams)
Wed Apr 22 08:10:50 1998
To: Yoav Yerushalmi <yoav@MIT.EDU>
Cc: netbsd-dev@MIT.EDU
From: "Nathan J. Williams" <nathanw@MIT.EDU>
In-Reply-To: Your message of "Wed, 22 Apr 1998 02:47:13 EDT."
<199804220647.CAA01085@emu.LCS.MIT.EDU>
Date: Wed, 22 Apr 1998 08:10:09 EDT
> However, now AFS is acting strange. I can't get it to run
> it tries to allocate 256 dcache entries, but then just hangs there.
> If I ctrl-c, afsd will not reload, and /afs/ is a device not ready device.
I've seen this before. My observations are that this only
happens after an earlier aborted use of AFS from the same IP
address. The server continues to talk to the client, and when the
network interface comes up the client at first sends back a lot of
ICMP port unreachable packets. I'm guessing that AFS server(s) in
question are caching the failure and not sending more data, but it's a
guess.
The workarounds I know are to wait or to use a different IP
address. I've had one report that the latter didn't help, which we
couldn't figure out.
- Nathan