I thought I would mention that while this has gotten worse, I haven't done anything really to fix it aside from running "fs *" commands (haven't restarted my client for a while--my libafs (up to 1.3.82) use to not unload from the kernel nicely and caused too many reboots. I hate rebooting, especially when I'm in the middle of some computational work. Perhaps I will dare to restart this again.)
Spencer On Saturday 20 August 2005 07:26, Derrick J Brashear wrote: > On Fri, 19 Aug 2005, Lyle wrote: > > Yes, that is an old bug that used to only happen very rarely so it's > > interesting that it's happening more frequently now. The connection gets > > put in a permanent error state so that every packet that comes in > > generates an abort, and I think the CM should destroy the connection but > > doesn't. I'm just thinking that since it's multihomed, one of the other > > interfaces should be satisfying the request. > > Well, one case which has happened recently appears to be: > 1) fileserver sends rx data packet with call number 0 to client > 2) client marks rx protocol error and errors to server > 3) but keeps sending traffic, which gets an abort. > > but, I'm still waiting to get some raw tcpdump from someone to see what > actually happens. > _______________________________________________ > OpenAFS-devel mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-devel
pgpUFExaGMKKd.pgp
Description: PGP signature
