[OpenAFS-devel] RX abort packets, and client sitting in "waiting for busy volume" state

[Neulinger, Nathan]

Primarily cause I can't easily add the instrumentation afterwards =
without
a major hassle. Right now, it's convenient for me to take the server =
down,=20
later it won't be.

They should all be running relatively current code (within 3-5 months of =
today)
for the clients, but June'ish for the servers.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Derrick J Brashear [mailto:shadow@dementia.org]=20
> Sent: Friday, February 01, 2002 3:59 PM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] RX abort packets, and client=20
> sitting in "waiting for busy volume" state
>=20
>=20
> On Fri, 1 Feb 2002, Neulinger, Nathan wrote:
>=20
> > We just had a client start to experience continual 'waiting=20
> for busy volume' messages against two volumes on a server=20
> that is not very loaded. I've got a network trace of=20
> communications w/ that client+server, and what's going on is=20
> the client is sending two FetchStatus requests (one against=20
> each volume), and the server is sending back a RX abort=20
> packet. Nothing but that over and over again.
> >=20
> > Any idea what could be causing this?
>=20
> Depends; What version are you running on them? A bug which could cause
> that was fixed in (I think) 1.2.2 after Jimmy Engelbrecht=20
> complained about
> his Arla clients suffering from it; Clients were not being=20
> properly reaped
> by the fileserver.
>=20
> > We're going to be upgrading file servers to more recent code very
> > shortly, if there is any instrumentation y'all think it=20
> would be worth
> > adding before I do that, please speak up, cause now is the=20
> time I can
> > add it reasonably. (We're clearing servers then upgrading os and afs
> > install.)
>=20
> Why not try the upgrade first, then worry about instrumentation if you
> still have a problem?
>=20
> -D
>=20
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20