[OpenAFS] Possible problem with openafs-client or modules 1.4.2

Derrick J Brashear shadow@dementia.org
Mon, 13 Nov 2006 14:07:23 -0500 (EST)

>> Except that code path can't cause a corrupted file. It may be related but
>> that error message (in the fileserver) is not a cause of that client
>> problem.
> In my tests the compilation sometimes abort, because of a timeout
> comunicating with the fileserver, usually happened during a vos
> backupsys of all volumes.

Can you get tcpdump from the client's point of view? Basically, at some 
point the client is marking the server down, I assume. The question is on 
the basis of what.

> Looking for errors in the fileserver I had seen "FindClient: stillborn
> client" in some of the cases.  Can it be possible when a client is
> hitting very hard a fileserver, with reads and writes, for this error
> to happen?

Yes. But, that's not necessarily related to the problem you're having.

> What I can do to pinpoint the cause of the problem?

As above.

> I can think this problem can hit my prodution clients and servers if I
> do an upgrade to 1.4.2, now they use 1.3.81, 1.4.0, 1.4.1.

There's no new code in 1.4.2 which would cause this. That server log 
message was also in 1.4.1, for instance.