[OpenAFS] Replicated volume refuses to be salvaged

[Derrick J Brashear]

On 25 Feb 2003, Norman P. B. Joseph wrote:

> Not that I doubt your diagnosis, Harmut, (and thanks for the response),
> but "c2t0d2s6" is a long name?  And anyways, it seems long past the time
> that we should be expecting dynamically generated pathnames fit into
> fixed-length buffers.  Regardless, all the file servers here are running
> Transarc AFS under Solaris 7, and I don't recall running into this
> problem before, having done many salvages.  What might have tickled this
> particular bug?



> The real reason for my post is this:  In practical terms, I have a clone
> volume that I can't seem to salvage, but neither can I delete it or
> "zap" it, or re-release the volume as long as this bad clone exists. 
> Does anyone have any advice for recovering from this position?  I can
> only imagine doing something like "vos remsite" for that volume and then
> pretending it doesn't exist anymore, but that leaves a bad taste in my
> mouth for obvious reasons.

If you roll over the pid space so you're using <= 4 digit pids, what
changes?

I'm not kidding.