[OpenAFS] vos release

Derrick J Brashear shadow@dementia.org
Thu, 8 Aug 2002 17:02:09 -0400 (EDT)


On Thu, 8 Aug 2002, Russ Allbery wrote:

> Just as a data point, it's not clear to me that this always has something
> to do with network problems.  We've seen exactly the same behavior on the
> campus network with no noticable network difficulties between the servers.
> Every so often the volume release would just not work; usually it would
> involve "possible communication failure" errors and usually errors about
> being unable to start a transaction.  It seemed to be strongly correlated

I think a fix in OpenAFS 1.2.6 will help this. Particularly, Brent Johnson
mentioned something to me at Usenix and based on that we made a change in
the fssync interface. I'm told IBM made an analogous change sometime
recently also.

> with some other volserver operation happening on that system at the same
> time (in other words, I could make it happen about 70% of the time by
> releasing two volumes located on the same servers at the same time).
> 
> This has been getting slowly worse all summer, but we think it was due to
> having a mixed OpenAFS and Transarc AFS set of file servers.  Or at least

I don't think it was the problem. 

> we hope.  As of this morning, everything is running OpenAFS 1.2.6, so
> we'll see if it gets any better....

Hopefully.