[OpenAFS] Re: Locked Volume

[Andrew Deason]

On Mon, 20 Dec 2010 16:43:24 +0000
Angela Hilton <Angela.Hilton@manchester.ac.uk> wrote:

> I realise that I can issue  
> vos unlock -id volume.name
> BUT, I am unsure if there are any potential problems that this could
> cause.

A locked volume typically indicates a "vos" command is running, or a
command got interrupted.

If there is another "vos" command running (trying to release the volume,
or move the volume, etc), unlocking the volume and doing something else
with it can screw that up. If you know of a "vos" command that got
interrupted, typically it's fine to unlock it and continue what you want
to do, as vos can recover from interrupted operations.

If you're not sure if an operation is running, you could check the
process lists on various machines, if you know that there are a limited
number of machines that could be fiddling with that volume. Otherwise,
you can check "vos status" on all of the fileservers relevant for that
volume, to see if there are any transactions open for the RW volume's
volume ID, or the volume ID for the RO/BK/clone, etc.

If you see no open transactions for any of the volume ids related to
that volume, it is likely that there are no in-progress volume
operations, and unlocking it manually is probably okay.

-- 
Andrew Deason
adeason@sinenomine.net