[OpenAFS-devel] Re: Breaking callbacks on unlink

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig60F07B94CA9B01B39DCAB50E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 2/28/2012 12:22 PM, Andrew Deason wrote:
> And how does this make the callback break a waste? If the contents are
> gone, forgoing a callback break can (and does, as we've seen) result in=

> inconsistent state between clients.

Inconsistent state between clients was not the issue that was raised
here.  The issue was unpredictability of continued file access.  The
designers made a compromise decision.  Do not break the callback on the
last unlink because it will expire on its own and by doing so permit
other clients that are using the file a bit more time to continue using
what is in the cache.  That is all.

>> Go back and re-read this thread.  Polling was brought up in discussion=

>> yesterday in the exchanges between Troy and Simon.
>=20
> The last post I see from Simon is from Saturday. Post a link or a
> message-id or something?

Simon's message from Saturday describes polling but does not use the word=
=2E




--------------enig60F07B94CA9B01B39DCAB50E
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)

iQEcBAEBAgAGBQJPTRL7AAoJENxm1CNJffh4H4QH/1D//yI3z6c3pDzmJTO+LkN3
VtsJurUkt/ftl6tR7GIys0GYLqxpsxQ7lFlNkIctSfg7w9ZI4IyxA+Za7v0kLi5d
LdM7sW647ZBEBO8Fl+grTv0kxzQo6bJWPBRUz2wVmF48z3hEHU8xrJ+0dyhfvbxb
2Jk+zWxda8qlj5spzpH20yICg4h/GKUxVL7b3FnegToHNyPVMxVueQCFl6tx6yx/
lsCIh7YY7VsZ1Fn3kYCf0E5E0iEka/KQsSEXWs/bnsdtZBOOuMkIWKe7pOBVPORF
yxoXk0w9xhgd6uTfITTBp0MxoylZeil4Gqgx4lh51tVfIrDzXLzXJBaTt3I9f8c=
=iGfq
-----END PGP SIGNATURE-----

--------------enig60F07B94CA9B01B39DCAB50E--