Data and tokens must be acquired

The third, and most complex path through write occurs when neither the buffer nor the token exists at the local node.

Prior to the allocation of a buffer, a token is acquired for the area of the file that is needed. As was true for read, if sequential operations are occurring, a token covering a larger range than is needed is obtained if no conflicts exist. If necessary, the token management function revokes the needed token from another node holding the token. Having acquired and locked the necessary token, the write continues as in Token available locally but data must be read.