[OpenAFS] Opening files read-only when another process has a
Fri, 18 Mar 2011 10:53:34 -0400
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=UTF-8
On 3/18/2011 9:29 AM, Thomas Smith wrote:
> Is it possible to open files read-only when another process has a
> write-lock? I found the following information regarding 1.5.20.
The release notes for the version of the OpenAFS client that is
installed on the machine in question is available locally
> Many applications on Windows (e.g. Microsoft Office) require
> the use of byte range locks
> applied to a file either to protect against simultaneous file
> access or as a signaling mechanism.
> OpenAFS for Windows release 1.5 (or greater) implements byte
> range locking within the
> CIFS-AFS gateway server. This support for byte range locking
> obtains AFS=E2=80=99 advisory file
> server locks to simulate Microsoft Windows mandatory locks.
> When an application opens
> a file, a lock will be obtained from AFS indicating that the
> file is in use. If the lock is a write
> lock, access to the file will be restricted to other
> applications running on the same machine
> as the first application to request the lock. Applications
> running on other machines will see
> the AFS full file lock and will be unable to access the file.
> Just wasn't sure if this is the current state things.
> I'm on 1.4.12 on the server and 1.5.78 on the client.
> This issue arose when one of my users was editing a spreadsheet and
> another user attempted to open the same spreadsheet for viewing--the
> attempted viewer received an error indicating that the file was
As described above, Microsoft Office applications use byte range locks
as a form of signaling. When an Office application requests a file be
opened in read-only mode it obtains a shared byte-range lock on a
particular section of the file. That permits other instances of Office
on the network to know that the file is open for read-only use and it
should not be changed.
This model works just fine on AFS if both instances are sitting behind
the same AFS cache manager since the cache manager can manage the byte
range lock allocations. However, it fails if the instances are on
different machines because the AFS file servers do not support
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
-----END PGP SIGNATURE-----