Hmm... I must not be decoding the abort type packet completely. If the error code is the 4-byte integer after the Service ID, then it is 0x0000006E, or 110. I didn't see any mention of that in the rx_packet structure though.
The trace is tiny if you want it. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Ken Hornstein [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 01, 2002 10:08 AM > To: Neulinger, Nathan > Cc: [EMAIL PROTECTED] > Subject: Re: [OpenAFS-devel] RX abort packets, and client > sitting in "waiting for busy volume" state > > > >(I've been doing alot of diagnosis attempting to improve our > AFS cell, that's > >why the stream of lots of these notes.) > > > >We just had a client start to experience continual 'waiting > for busy volume' > >messages against two volumes on a server that is not very > loaded. I've got > >a network trace of communications w/ that client+server, and > what's going on > >is the client is sending two FetchStatus requests (one > against each volume), > >and the server is sending back a RX abort packet. Nothing > but that over > >and over again. > > What's the error code from the abort packet? That should > tell you _something_. > > --Ken > _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
