[OpenAFS] vos release

[Neulinger, Nathan]

FYI, there is a patch in the bug tracker that adds a significant amount
of additional progress reporting to vos release operations, to help
track down precisely where it is failing. (We see it occasionally on
servers that are otherwise happy.)

The patch has not yet been committed, not clear if it will be or not,
but if anyone wants it, it's attached to ticket #817. Output is only
added if running the release with -verbose.

-- Nathan

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


> -----Original Message-----
> From: Russ Allbery [mailto:rra@stanford.edu]=20
> Sent: Thursday, August 08, 2002 2:44 PM
> To: openafs-info@openafs.org
> Subject: Re: [OpenAFS] vos release
>=20
>=20
> Dan Pritts <danno@internet2.edu> writes:
>=20
> > I've used AFS with file servers in different sites,=20
> hundreds of miles
> > away.
>=20
> > Normally everything went just groovy, but occasionally when the WAN
> > links flaked (thanks NYNEX) we would see terrible=20
> performance problems
> > when doing a vos relase. =20
>=20
> > If you didn't know what was happening (say, because the vos release
> > was part of your useradd script, and it just seemingly hung there
> > forever), or just because you were impatient,  and you hit=20
> control-c,
> > the vos release process would die and the volume would be=20
> locked, and
> > the replica at the remote site would be hosed.
>=20
> Just as a data point, it's not clear to me that this always=20
> has something
> to do with network problems.  We've seen exactly the same=20
> behavior on the
> campus network with no noticable network difficulties between=20
> the servers.
> Every so often the volume release would just not work;=20
> usually it would
> involve "possible communication failure" errors and usually=20
> errors about
> being unable to start a transaction.  It seemed to be=20
> strongly correlated
> with some other volserver operation happening on that system=20
> 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).
>=20
> This has been getting slowly worse all summer, but we think=20
> it was due to
> having a mixed OpenAFS and Transarc AFS set of file servers. =20
> Or at least
> we hope.  As of this morning, everything is running OpenAFS 1.2.6, so
> we'll see if it gets any better....
>=20
> --=20
> Russ Allbery (rra@stanford.edu)            =20
> <http://www.eyrie.org/~eagle/>
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20