[OpenAFS] Re: nightly failure since upgrading to 1.6.5

Andrew Deason adeason@sinenomine.net
Mon, 10 Feb 2014 14:27:14 -0600

On Mon, 10 Feb 2014 13:00:48 +0000
pg@afs.list.sabi.co.UK (Peter Grandi) wrote:

> That " _VLockFd: conflicting lock held" and "VAttachVolume:
> another program has vol NNNN locked" looks vaguely familiar, and
> in a case that I have seen it was because a DB server was
> offline, and 'vos' took a very very long time to switch to an
> online one. But this was with 1.4 and supposedly 1.6 should have
> a shorter timeout.

Just so there's no confusion, these situations don't have anything to do
with each other. The 'lock' in that message is referring to a very
low-level fcntl lock, and has to do with the storage of files on disk,
and the communication between the fileserver and volserver. Whereas the
'lock' I think you're thinking of is a VLDB entry lock (though honestly
that lock didn't have much relevance in that situation, either), which
involves different processes and is a much higher-level, more conceptual
'lock' in the AFS protocol.

Andrew Deason