System for file and record locking between nodes in a distributed data processing environment maintaining one copy of each file lock5202971Abstract A conventional single node operating system is provided with a distributed file management system (DFS) with a plurality of nodes and a plurality of files. The DFS uses the UNIX operating system tree structure employing inodes (data structure containing administrative information for each file) to manage the local files and surrogate inodes (s.sub.-- inode) to manage access to files existing on another node. In addition, the DFS uses a lock table to manage the lock status of files. The method which implements the DFS locking of records and files involves the following steps. If the file is a local file, then the UNIX operating system standard file locking is used. However, if a remote file is to be locked, the UNIX operating system LOCKF and FCNTL system calls are intercepted and an remote process call (RPC) DFS.sub.-- LOCK.sub.-- CONTROL is executed. The server node receives the remote process call and carries out the lock request. The request could entail locking a single record, a set of records or the whole file. The server then acknowledges receipt of the RPC by sending a signal while the client surrogate inode is waiting for a reply from the DFS.sub.-- LOCK.sub.-- CONTROL RPC. The client confirms the reception of the lock and sends an acknowledgement to the remote server. The server updates the lock table after receiving the acknowledgement from the client surrogate inode. If the server does not confirm the reception of DFS.sub.-- LOCK.sub.-- CONTROL's acknowledgement, then DFS.sub.-- LOCK.sub.-- CONTROL updates the lock table. Claims We claim: Description CROSS REFERENCE TO RELATED APPLICATIONS
______________________________________
function lookup
input: directory vnode pointer,
name to be looked up in directory
output: vnode pointer to named file/dir.
convert directory vnode pointer
to an inode pointer;
-- use private data pointer of vnode
lock directory's inode;
if( we don't have search permission in
directory )
unlock directory inode;
return error;
search directory for name;
if( found )
create file handle for name;
-- use inode found in directory entry;
get pointer to vnode for file handle;
unlock directory inode;
return pointer to vnode;
else -- not found
unlock directory inode;
return error;
VN.sub.-- OPEN
______________________________________
The function vn.sub.-- open creates a file access structure (or modifies an existing one) to record what open modes (READ/WRITE or READ.sub.-- ONLY) to open a file. The pseudo code for the vn.sub.-- open operation is listed below:
______________________________________
function vn.sub.-- open
inputs: vnode pointer for file to be opened
open flags (e.g., read-only,
read/write)
create mode -- file mode bits if
creating
output: return code indicating success or
failure
get pointer to file's inode from vnode;
lock inode;
if( not permitted access )
unlock inode;
return( error );
get the file access structure for this
client;
-- if there is no file access structure
allocate one
if( couldn't allocate file access
structure )
unlock inode;
return( error );
update file access structure read-only,
read/write, and text counts;
if( truncate mode is set )
truncate file:
unlock the inode;
LOOKUPPN
______________________________________
The lookuppn operation is the function which follows paths. Its input is a path (e.g., "/dir1/dir2/file"), and its return is a pointer to the vnode which represents the file. Lookuppn calls vn.sub.-- lookup to read one directory, then it checks to see if the vnode returned by vn.sub.-- lookup has been mounted over. If the vnode is not mounted over, then lookuppn calls vn.sub.-- lookup in the same file system. If the vnode has been mounted over, then lookuppn follows the pointer from the mounted over vnode (e.g. block 24 in FIG. 4) to the vfs of the mounted file system (e.g., block 25 in FIG. 4). From the vfs, it follows the pointer to the root vnode (e.g., block 26 in FIG. 4) and issues a new vn.sub.-- lookup giving as input the vfs's root vnode and the name which constitutes the next element in the path. The pseudo code for the lookuppn function is listed below:
______________________________________
function lookuppn
input: pathname
output: pointer to vnode for named file
if( first character of path is `/` )
current vnode for search is user's root
directory vnode;
else
current vnode for search is user's
current directory vnode;
repeat
if( next component of path is ".." )
while( current vnode is root of a
virtual file system )
current vnode becomes the vnode that
the virtual file system is mounted
over;
if( there is not mounted over vnode )
return( error ); -- ".." past root
of file system
use vn.sub.-- lookup to look up path component
in current vnode;
if( vn.sub.-- lookup found component );
current vnode becomes the vnode
returned by vn.sub.-- lookup;
while( current vnode is mounted over )
follow current vnode's pointer to vfs
structure that represents the
mounted virtual file system;
current vnode becomes root vnode of
the mounted vfs;
else -- vn.sub.-- lookup couldn't file component
return( error ); -- search failed
until( there are no additional path
components );
return( current vnode );
______________________________________
The operation will be illustrated by describing the scenarios of following a path to a file and mounting a directory. First, in following a path to a file, suppose an application process issues a system call (e.g., open) for file "/u/dept54/status". This request is accomplished by the operating system in the following manner with reference to FIG. 4 (operations which are basically unchanged from the UNIX operating system are not explained here in any detail). The following assumptions are made: First, the vfs represented by block 21 is the root virtual file system. Second, the file "/u" is represented by vnode block 24 and inode block 31. Third, a previous mount operation has mounted a device's file system onto the directory "/u". This mount created the vfs represented by block 25. Fourth, all of the directories and files involved are on the same device. Fifth, the following directory entries exist in the indicated directories:
______________________________________
DIRECTORY
INODE NUMBER NAME INODE NUMBER
______________________________________
2 "u" 15
45 "dept54" 71
71 "status" 12
______________________________________
The code which implements the system call calls lookuppn to follow the path. Lookuppn starts at the root vnode (block 23) of the root virtual file system (block 21) and calls vn.sub.-- lookup to look up the name "u" in the directory file represented by this vnode. Vn.sub.-- lookup finds in the directory that the name "u" is associated with inode 15 in block 31. Vn.sub.-- lookup must return a pointer to a vnode associated with inode 15. To do this it first brings inode 15 into the inode table. Then it checks to see if there is already a vnode in the parent vfs (the input vnode (block 23) has a pointer to the parent vfs) for this vnode. In this case there is. Vn.sub.-- lookup then finds the vnode (block 24) in the root vfs (block 21) and returns a pointer to the vnode. Lookuppn discovers that the returned vnode is mounted over in the parent vfs. It follows the "mounted over" pointer from the vnode (block 24) to the mounted vfs (block 25). Lookuppn follows the "root vnode" pointer to the root vnode (block 26) of the new vfs (block 25). Lookuppn now calls vn.sub.-- lookup again, this time inputting a pointer to the root vnode (block 26) and name "dept54". As before, vn.sub.-- lookup reads the directory, finds the inode associated with the name, finds or creates a vnode for this inode in the parent vfs (block 25) and returns a pointer to this vnode. Lookuppn calls vn.sub.-- lookup once more inputting the vnode for the just found directory and the name "status". Vn.sub.-- lookup reads the directory, finds the inode associated with the name (block 34), finds or creates a vnode (block 28) for this inode in the parent vfs (block 25) and returns a pointer to this vnode. The code which implements the system call now performs the requested operation on the file. Suppose now that an application process issues a "mount" system call to mount the directory "/u/gorp" over the directory "/u/foo". The following scenario explains how this request is accomplished by the operating system (again, operations which are basically unchanged from UNIX operating system are not explained in any detail). This scenario refers to FIG. 5, which represents initial conditions, and FIG. 6, which represents the final conditions, with the following assumptions: First, the vfs represented by block 41 is the root virtual file system. Second, all of the directories and files involved are on the same device. Third, the following directory entries exist in the indicated directories:
______________________________________
DIRECTORY
INODE NUMBER NAME INODE NUMBER
______________________________________
2 "u" 15
2 "etc" 83
15 "gorp" 92
83 "foo" 75
75 "file1" 89
______________________________________
The code which implements the mount system call performs the following operations. Lookuppn is called to follow the path to the directory which is to be mounted over--"/etc/foo". At the completion of this operation, the root vfs (block 41) contains a vnode for "/etc/foo" (block 44) which has a pointer to the root vfs (block 41) and pointer to an inode table entry (block 45) for inode 75. Lookuppn is called to follow a path to the directory which is to be mounted --"/etc/gorp". At the completion of this operation, the root vfs (block 41) contains a vnode for "/etc/gorp" (block 49) which has a pointer to the root vfs (block 41) and a pointer to an inode table entry (block 48) for inode 92. Now the mount logic creates the new virtual file system by first creating a new vfs (block 46) and then creating a root vnode for this vfs (block 47) with a pointer back to its parent vfs (block 46) and a pointer to the root inode (inode 92, block 48) of the vfs. A "mounted over" pointer is installed in the covered vnode (block 44) in the root vfs (block 41), and a pointer to the vnode upon which it is mounted (block 44) is installed in the new vfs. The foregoing illustrates the data structure for standalone operation. Reference is now made to FIG. 7 which shows a distributed system similar to that shown in FIG. 1 in which the operating system which supports the present invention has been implemented. In the following description, the term "server" is used to indicate the node where a file is permanently stored, and the term "client" is used to mean any other node having processes accessing the file. It is to be understood, however, that the term "server" does not mean a dedicated server as that term is used in some local area network systems. The distributed services system in which the invention is implemented is a truly distributed system supporting a wide variety of applications running at different nodes in the system which may access files located anywhere in the system. The data structure for the distributed system shown in FIG. 7 is illustrated in FIG. 8, and the component parts of that data structure are shown in FIGS. 9A to 9F. With reference to FIG. 8, a client node may have access to files which reside in a remote server node. Such a client gains access to a server's files by mounting one of the server's directories. In the client node, the data structures created by a remote mount operation compare to those created by mounting a local entity in the following ways: Just as in the local case, a remote mount creates a vfs in the client node (e.g., block 54). Just as in the local case, use of a file in a virtual file system which contains remote files creates a vnode structure in the client node (e.g., block 57). Just as in the local case, the vnode structure has a pointer to a inode table entry (e.g., block 63). The inode table entry, however, does not contain the inode information from the remote file. Instead, the inode table entry contains a surrogate inode. This surrogate inode stands for, or represents, the remote inode. In the server node, some data structures are constructed to allow the server to record state information about how remote nodes are using its files. More specifically, each server has a "dummy vfs" (e.g., block 71) to provide a vfs to hold files open by remote clients. A server has only one dummy vfs, and all files open by all remote clients reside in this vfs. The dummy vfs is not a part of the server's file tree. For each file which is open by a remote node, there is a vnode (e.g., block 74) in the server's dummy vfs. Each file which is open by a remote node has an inode table entry in the server's inode table (e.g., block 85). This inode table entry is the same as that which exists because a local process at the server has a file open. For example, block 84, which is in the table because of a remote open, has the same structure as block 88, which is in the table because of an operation at the server. When a client and server communicate about a server file, they need a way to identify the file. This is done with a file handle. When a client request causes the server to reply with a designation of a particular file (e.g., a remote lookup request), the file is identified by a file handle. When a client request carries a designation of a particular file (e.g., a remote open request), the file is identified by a file handle. The file handle contains the following fields: device number, inode number, and inode generation number. The need for a file handle is illustrated by the following scenario. Suppose a client makes a request of a server and gets a file handle in reply. The client stores and remembers the file handle. Some activity at the server causes the file to be deleted and the inode slot reused for another file. The client makes a request of the server using the stored file handle. The server receives the file handle and performs the operation on the new file. This would be an unacceptable operation. This flaw is prevented by use of the inode generation number. The inode generation number is stored on disk as a field in the inode. When the server deletes a file, it increments the inode generation number. If a request arrives at a server, the file handle is broken apart, the device number and inode number are used to locate the inode, and then the file handle inode generation number is compared to the inode's inode generation number. If they are different, then the request is rejected. When a client wants to open a file which resides on a remote server, it uses a network transport mechanism to establish a connection with the server. Subsequent transactions regarding this file (e.g., read, write, etc.) flow on this connection. Each node contains a node table. A node uses entries in its node table (e.g., block 70) to record information about existing connections to remote nodes. There are a limited number of operations that one node in the network can request another node to perform on its behalf. These operations are called dfs.sub.-- ops. When a node makes a request of another node, the following operations occur: First, the requesting node sends a message which specifies which dfs.sub.-- operation is being requested and carries the parameters appropriate to that request. Next, the receiving node receives the request and performs the specified operation. Finally, the receiving node sends a message which carries the reply parameters appropriate for the dfs.sub.-- operation. There is a close correlation between the vn.sub.-- ops that are issued within a local node to a file system and the dfs.sub.-- ops that are issued over the network. A typical operation on a remote file is as follows: First, a local kernel issues a vn.sub.-- op, not knowing whether the file being operated on is remote or local. Second, since the file resides in a remote node, the file system implementation code sends the corresponding dfs.sub.-- op to the node which holds the file. Note that if the file had been a local file, the operation would have been performed, the return parameters would have been returned, and the task would have been complete. Third, the node which holds the file receives the dfs.sub.-- operation request and requests its local file system to perform the corresponding vn.sub.-- operation. The return parameters from this vn.sub.-- op are used to construct the return parameters for the dfs.sub.-- op. Fourth, the requesting node receives the dfs.sub.-- op reply from the server node and uses the dfs.sub.-- op return parameters to construct the return parameters to the original vn.sub.-- operation request. The operation will be illustrated by describing the scenarios of mounting a remote directory over a local directory and following a path to a file. In the first scenario, suppose that an application process in a client node issues a "mount" system call to mount a server node's directory "/u/gorp" over the local client directory "/etc/foo". The following scenario explains how this request is accomplished. This scenario refers to FIG. 10, which represents the initial conditions, and to FIG. 11, which represents the final condition, with the following assumptions: The vfs represented by block 51 is the root virtual file system of the server's file tree, and all the server directories and files involved are on the same device. The following entries exist in the indicated directories:
______________________________________
Server Node
DIRECTORY
INODE NUMBER NAME INODE NUMBER
______________________________________
2 "u" 15
15 "gorp" 92
92 "file2" 67
______________________________________
Client Node
DIRECTORY
INODE NUMBER NAME INODE NUMBER
______________________________________
2 "etc" 83
83 "foo" 75
______________________________________
The code which implements the mount system calls lookuppn to follow the path to the directory which is to be mounted over--"/etc/foo". At the completion of this operation, the root vfs (block 51) contains a vnode for "/etc/foo" (block 53) which has a pointer to the root vfs (block 51) and a pointer to an inode table entry (block 61) for inode 75. Since the directory being mounted resides in a remote node, a dfs.sub.-- mount request is issued to the server node, passing the path "/u/gorp" as the path to the object to be mounted. Upon receiving the dfs.sub.-- mount request, the server node calls lookuppn to follow the path to the directory which is to be mounted--"/u/gorp". At the completion of this lookup operation, the server's root vfs (block 71) contains a vnode for "/u/gorp" which has a pointer to the root vfs and pointer to an inode table entry for inode 92. The server uses the information in the inode (device 0, inode 92) to construct a file handle for the file "/u/gorp". The server returns this file handle in the reply to the dfs.sub.-- mount request and then releases the vnode and inode. Finally, the client receives the file handle in the reply to the dfs.sub.-- mount request and performs the operations necessary to create the new virtual file system as follows: a) Create a new vfs (block 54). b) Create a root vnode for this vfs (block 55) with a pointer back to its parent vfs (block 54) and a pointer to the root inode of the vfs (block 62). Since the root inode of this vfs is a remote directory, the inode pointed to from the root vnode is a surrogate inode. This surrogate inode contains the file handle returned by the server in response to the client's dfs.sub.-- mount request. c) Install a "mounted over" pointer in the covered vnode (block 53) in the root vfs (block 51). d) Install in the new vfs (block 54) a pointer to the vnode upon which it is mounted (block 53). Suppose now that after executing the remote mount described above (mount server /u/gorp over client /etc/foo) a client process issues a system call to operate on the file "/etc/foo/file2". The block numbers in the following scenario refer to FIG. 11, which represents initial conditions, and FIG. 12, which represents the system state after the open operation. First, the code which implements the system call calls lookuppn to follow the path. Lookuppn starts at the root vnode (block 52) of the root virtual file system (block 51) and calls vn.sub.-- lookup to look up the name "u" in the directory file represented by this vnode. Vn.sub.-- lookup finds in the directory that the name "u" is associated with inode 15. Vn.sub.-- lookup constructs a vnode and inode in the root virtual file system for inode 15 and returns to lookuppn a pointer to this vnode. Lookuppn calls vn.sub.-- lookup again, this time to look up the name "foo" in the directory identified by inode 15. Vn.sub.-- lookup reads the indicated directory and discovers that the name "foo" is associated with inode 75 in block 61. There already exists in the root vfs (block 51) a vnode (block 53) for this inode (block 61), so vn.sub.-- lookup returns a pointer to this vnode. Lookuppn discovers that the vnode is mounted over (the "mounted over" pointer in block 53 points to block 54). Lookuppn thus follows the "mounted over" pointer to the next vfs (block 54) and follows its root vnode pointer to the root vnode (block 55) of the virtual file system. Lookuppn now calls vn.sub.-- lookup for the next element ("file2") of the path giving vn.sub.-- lookup a pointer to block 55 and the name "file2". The directory to be searched resides in a remote node and is identified by the file handle stored in the client surrogate inode (block 62). Vn.sub.-- lookup issues a dfs.sub.-- lookup to the server which holds the file, sending the file handle which identifies the directory and the name ("file2") which is to be looked up. When the server receives the dfs.sub.-- lookup, it uses the file handle to identify the directory to be read and issues a vn.sub.-- lookup to search for the name "file2" in this directory. Vn.sub.-- lookup reads the directory and discovers that the inode number associated with the name "file2" is 67. Vn.sub.-- lookup constructs a vnode and inode in the dummy virtual file system for inode 67 and returns to lookuppn a pointer to this vnode. Dfs.sub.-- lookup uses the information in data structures returned by vn.sub.-- lookup to construct a file handle for the file identified by inode 67. It returns this file handle to the client, as the reply to the dfs.sub.-- lookup request, and releases the vnode and inode. In the client, a vnode (block 58) and surrogate inode (block 63) are created for the found file. Since "file2" is the last piece of the path, lookuppn returns to its caller a pointer to the found vnode (block 58). The code which implements the system call now performs the requested operation on the file. In the distributed services system in which the invention is implemented as shown in FIG. 7, a local cache 12A, 12B and 12C exists at every node A, B and C. If file 5 permanently resides at node A on disk 2A, use of the cache 12A by local processes 13A executing at the server node A is the same as that in a stand alone system as discussed above. However, remote processes 13B and 13C executing at nodes B and C, respectively, access file 5 through a two step caching scheme using a server cache and a client cache as shown in FIG. 3. The server node gets blocks of file 5 from disk 2A and stores it in the server cache 12A. Client node B goes out over the network 3 and gets blocks of file 5 from the server cache 12A. Client node B stores the blocks of file 5 as it existed in the server cache 12A into the client cache 12B. When the user address space 14B of client node B seeks data from any block of file 5, the client cache 12B is accessed instead of going across the network 3 for each access. Using the client cache 12B to access a remote file 5 can significantly improve the performance since it can save network traffic and overhead. The system and method of this invention manages the use of the client cache 12B and server cache 12A in a distributed environment to achieve high performance while preserving the file access semantics at the application program level. This allows existing programs which run on a standalone system to run on a distributed system without any modification. The file access semantics preserves a file's integrity as it is being opened by different processes that issue read and write system calls to access and modify the file. The file access semantics require that only one I/O operation is allowed on any byte range at a time, and once an I/O operation starts, it cannot be pre-empted by any other I/O operation to the same byte range of the file. An example of this is given by referring to FIG. 13. If process 131 issues a write system call to a byte range N1-N2 in file 5, the write system call can only be executed when the entire byte range N1-N2 is available for access by process 131, and no read operation involving the byte range N1-N2 is being executed. During the execution of the write system call, all other operations involving the byte range N1-N2 in file 5 are suspended until the write is completed. The write is not completed until the bytes are written to the local cache 12A. When a write request is complete, the written data in the cache 12A is visible to any subsequent read operation by any of the other processes 131 to 13N. Another requirement of file access semantics is that when a file byte range such as N1-N2, which can be a record or a set of related records accessed by the same I/O operation, is visible to a read process, the file byte range N1-N2 must always have a consistent set of data reflecting the last update to this range. This range is never available for access while a write operation is being executed. In this way, the next read issued by a process will read the data just written and not the old outdated data. In a distributed networking environment of this invention as shown in FIG. 7, the execution of read and write system calls from different application programs 4A and 4B and processes 131 to 13N and 231 to 23N are synchronized such that the file access semantics as previously discussed are preserved. The system and method of this invention guarantees synchronization by utilizing various cache synchronization (sync) modes. For a specific file 5, the I/O calls are synchronized by either the client B or the server A depending on the location of the processes 131 to 13N or 231 to 23N which have the file 5 open for access, and the sync mode. The three synchronization modes are shown in FIG. 14 and are described with reference to FIG. 7. The first mode 104 is referred to as ASYNC's.sub.-- mode, or asynchronous mode. The file 5 operates in this mode 104 if file 5 is open for read/write access by processes 13C executing at only one client remote node C, as shown in block 107 of FIG. 14. In this mode 104, all of the control is in the client node C. Both the server cache 12A and client cache 12C are used for these read/write operations. A read or write operation requires access to the server cache 12A only if it cannot be satisfied from the client cache 12C. Modified blocks at the client 12C are written to the server 12A by the periodic sync operation, when the file 5 is closed by all processes 13C in the client node C, or when more room is needed in the client cache for other data. Additionally, modified blocks are written to the server when the file changes from ASYNC s.sub.-- mode to FULLSYNC s.sub.-- ode. A second mode 105 is READONLY s.sub.-- mode. The READONLY s.sub.-- mode 105 is used for files 5 that are open for read only access from processes 13C in only one node C, or from processes 13B and 13C in more than one node B and C as shown in block 108 in FIG. 14. In this mode 105, the server cache 12A and the client caches 12B and/or 12C are used. The read request is issued for a block or more at a time. Every other read request from the same client, either B or C, to the specific block does not go to the server 12. Instead, it is read from the respective client cache, either B or C. In other words, a read operation does not require access to the server 12A if it can be satisfied from the client cache 12C or 12B. In summary, the file 5 operates in mode 105 if the file 5 is open for read only access by any of the processes 13A, 13B or 13C in any of the nodes A, B or C. A third mode 106 is FULLSYNC s.sub.-- mode. The FULLSYNC s.sub.-- mode 106 is used for files 5 open in more than one node A, B and at least one node has the file 5 open for write access. In the FULLSYNC s.sub.-- mode 106, the client cache 12C or 12B is bypassed, and only the server cache 12A is used. All read and write operations are executed at the server 12A. In a distributed environment 1 as shown in FIG. 7, most files 5 will more frequently be open for read only by processes 13A, 13B and 13C at several nodes A, B and C in the READONLY s.sub.-- mode 105 shown in FIG. 14 or open for update at only one node in the ASYNC s.sub.-- mode 104. It will be less frequent that there will be an open for read and write access by processes executing at more than one node in the FULLSYNC s.sub.-- mode 106. In both the READONLY s.sub.-- mode 42 and the ASYNC s.sub.-- mode 104, the use of a client cache 12B, shown in FIG. 13, significantly reduces the remote read/write response time of accessing file 5 and improves overall system performance. As shown in FIG. 15, in the FULLSYNC s.sub.-- mode, the client cache is not used. The client node B accesses the file 5 from the server A over the network 3 for each read and write operation. Although the read/write response time increases in this mode, the file access semantics are preserved since a client does not retain a file 5 in local cache that has not been updated along with the corresponding file residing at the server. Utilizing the three modes to manage the use of the client cache optimizes overall system performance by combining both an overall average increase in read/write response speed with file integrity. Using a client cache in some situations decreases the read/write response time; while not using a client cache in other situations preserves the file system semantics. A file's sync mode is not only dependent on which nodes have the file open and whether the file is open for read or write, but also on whether the device where the file resides is open in raw access mode. Raw access for a device means that a block of data LBN1 shown in FIG. 8 within a device 2A is accessed. In this way, the reads and writes of the device 2A read and write to a block LBN1 of device 2A. It is not relevant to which file the block belongs. The device 2A can be opened for raw access from a process 131 to 13N at the server node A. It can not be opened for raw access from a remote node B or C. In FIG. 13, the cache 12A is managed as blocks LBN1 of device 2A, similar to a standalone system as described above with reference to FIG. 2. The server A looks at the server cache 12A as a logical block LBN1 within a device 2A. The client B has no knowledge of where the file 5 resides on the device 2A. All the client B knows is that it accesses a file 5 on block number N1 on device 2A. The client cache 12B handles the data as logical blocks N1 of file 5. In the server cache 12A, the data is handled as logical blocks LBN1 of devices 2A. In handling the data this way, the server can guarantee that if data is written to the device as a raw device, and if there is another read of a block of the file that happens to be the same block that was written to the device, then the read would see the newly written data. This preserves the file system semantics. If the file is being accessed in a client node B, and the file is in ASYNC or READONLY mode, as shown in FIG. 13, the client operating system 11B does not convert the file descriptor and byte range within the file in the system call READ (file descriptor, N1) 16 to the device number and the logical block number in the device. The client does convert the file descriptor and byte range to a file handle, node identifier, and logical block number within the file. In the client cache 12B, there are blocks 17 that are designated by file handle, node identifier, and logical block number within the file. When a read 16 is issued from a client application 4B, the request for the read goes to the operating system 11B with the file descriptor and the byte range within the file. The operating system then looks in the client cache 12B. If the file handle, node identifier, and logical block number within the file is there, the cache 12B is read; on the other hand, if it is not there, the read is sent to the server. The server then takes the file handle and the logical block number within the file and converts it to a device number and logical block in the device. This conversion is necessary since the server cache 12A is managed by device number and block number within the device as it is in a standalone system. After the read is sent to the server, it is handled the same as if the read was coming from its own application in a standalone system as described with reference to FIG. 2. A closed file does not have a synchronization mode. However, once a file is first opened by a process, the file's sync mode is initialized according to the following as illustrated in FIG. 16. The sync mode for a file is initialized to ASYNC 104 if the device there the file resides is closed 112; i.e., it is not open as a special device and the file is open for write access at one remote node 113. The sync mode for a file is READONLY 105 if the device where the file resides is closed, and the file is open for read only access in one or more nodes 114, or both the device and the file are open for read only access 115. The sync mode for a file is initialized to FULLSYNC 106 if the device where the file resides is open as a block special device for read/write access 116, or the file is open in more than one node and at least one of the opens is for writing. A block special device means that there is a raw access to the device. Once a file is initialized to a mode, if the conditions change, the file mode may change. Transitions from one mode to another, as shown by lines 118 to 123 in FIG. 16, may occur under the following conditions. If a file is presently in ASYNC mode 104, and the number of nodes where the file is open becomes two or more, 124, then the sync mode changes to FULLSYNC 106 as shown via line 119. Also, if there is an open of the block special device D where the file resides, 125, the sync mode will change from ASYNC 104 to FULLSYNC 106. In a close operation for the file, if the close operation is not the last close of the file, and the file is still open for write, there is no mode change. However, if the close operation is the last close of the file for write access such that all the remaining opens are for read access, 83, then the new mode becomes READONLY 105 as shown via line 121. If the close operation is the last close of the file, then there is no sync mode. If a file is presently in READONLY s.sub.-- mode 105 and there is a file open operation, there will not be a mode change if the open is for read. However, if the open is for write, then the new sync mode is ASYNC 104 if all the opens are in one client node, 127, as shown via line 120. Otherwise, the sync mode is FULLSYNC. Furthermore, if the device where the file resides is open for read/write access, 130, the new sync mode for the file is FULLSYNC mode 106. For a close operation, if the close is the last close of the file, there is no sync mode for the file. If the file is still open at one or more nodes after a close operation, there is no change to the sync mode. If a file is presently in FULLSYNC mode 106 and there is another open for the file, or the device where the file resides is opened, there is no sync mode change. If after a close operation of the file, there remains an open for read/write access at the remote node, and the block special device where the file resides is not open, the sync mode is changed to ASYNC s.sub.-- mode 104, as shown by block 141 via line 118. The sync mode is changed from FULLSYNC 106 to READONLY 105 if the block special device where the file resides is not open, and the file is open for read only access at one or more nodes as shown by block 142 on line 122, or if the block special device where the file resides is open for read only access and the file is open for read only access as shown in block 143 on line 122. All open and close operations for files and devices are resolved at the server node. The server determines the sync mode of an open file when executing any operation that may change the mode. The server also performs the change of the synchronization modes. As the server gets new opens or closes for the file, a change in synchronization modes for the file may be triggered. If the required sync mode is not the current one, the server sends a "change sync mode" remote procedure call to all the clients with the file open. After a file is opened for the first time, the client that opened the file is informed of the mode of the file. If the mode is either ASYNC or READONLY, the client can start using the client cache for reads, and also for writes if the mode is ASYNC, as shown in FIG. 13. The client does not have to read or write over the communications link to the server. If the mode is FULLSYNC as shown in FIG. 15, the client cache is not used, and the client must send the read or write over the communications link 3 to the server. The server A, in FIG. 15, always sets the mode 151 of the file 5. The mode of the file is the same at every node that has the file open. The server A also knows which nodes have the file open, and whether the opens are for reads or writes. The server A does not have to know which processes 131 to 13N, 231 to 23N within a node have a file open. The server keeps all the above information in a file access structure list 150, as shown in FIG. 15. Each element of the file access structure list 150 contains a node which has the file open 152, the number of opens for read 153 in the node, and the number of opens for write 154 in the node. In the UNIX operating system, processes can lock byte ranges within files so that other processes do not have access to these ranges. Support for such locking has varied from one version of the UNIX operating system to another; however, in most implementations, locks apply to a byte range of a file. A lock over the entire extent of a file locks the file and is sometimes called a file lock. By convention, a request to lock a range of zero bytes in length indicates that all bytes from the beginning of the range to the end of the file are to be locked. This allows a process to lock a file before appending additional bytes to the file while maintaining control over all of the new bytes. A lock over an arbitrary byte range is sometimes called a record lock, but within this document all locks on files and records (byte ranges) will be simply referred to as locks. In the AIX operating system, lockf(2) and fcntl(2) provide support for both read and write locks. Write locks are exclusive locks: if a range of a file is write locked, no other lock of either kind can exist on that range. Read locks are shared locks: any number of overlapping read locks can apply to a segment of a file. Notice that an existing read lock does not block other read locks, but it does block other write locks; and an existing write lock blocks all other locks on an overlapping range. Files, in the AIX operating system, are either in enforced locking mode or advisory locking mode. The locking mode of a file is controlled by changing the file's permission codes with the chmod system call. Locks on a file in enforced locking mode are called enforced locks; locks on a file in advisory mode are called advisory locks. An advisory lock does not provide absolute protection for a file or record because it does not prevent a process from reading or writing the locked file or record. Advisory locks only affect the results of calls to lockf(2) or fcntl(2), and so, must be used by processes that are cooperating, by using lockf(2) or fcntl(2) to query the status of locks on the shared files that they are accessing. The advantage of advisory locks is that they do not have to be interrogated by the kernel during ordinary reading or writing operations. Enforced locks will probably be used less often. An enforced lock, like an advisory lock, affects subsequent calls to lockf(2) and fcntl(2); but in addition, each read(2), write(2), open(2), creat(2), fclear(2), ftruncate(2), and shmat(2) insures that no read or write locked portion of the file is being changed and that no write locked portion of the file is being accessed. Three different commands of the fcntl(2) system call are related to locking: F.sub.-- GETLK Find the first existing lock that would prevent the lock described by fcntl(2)'s argument from being granted to the caller. F.sub.-- SETLK Grant the lock described by fcntl(2)'s argument to the caller. If the lock cannot be granted because an existing lock interferes with the request, return the description of this existing lock. F.sub.-- SETLKW Grant the lock described by fcntl(2)'s argument to the caller. If the lock cannot be granted because an existing lock interferes with the request, check for deadlock and if no deadlock will be caused, cause the caller to wait. Each time an interfering lock is cleared, the kernel again attempts to establish the requested lock by searching for any interfering locks. A process could wait forever. Although deadlocks that involve only file locks on a single node are detected, deadlocks due to file locks on multiple nodes can occur. Also, a process might never deadlock, but it could fail to obtain the lock for an indefinite period because each time an interfering lock was cleared, another interfering lock could already be set. For each of these commands, a pointer to a structure, the flock structure describing a lock, is provided as an argument in the fcntl(2) call. The flock structure has the following form:
______________________________________
struct flock {
short l.sub.-- type;
short l.sub.-- whence;
long l.sub.-- start;
long l.sub.-- len;
unsigned long
l.sub.-- sysid;
short l.sub.-- pid;
}
______________________________________
The fields of the flock structure as shown in FIG. 18 have the following meanings: 1.sub.-- type 200 is used to indicate whether the lock is a read or a write lock, 1.sub.-- whence 205 is 0 if the byte range for this lock starts at a position relative to the beginning of the file, 1 if the range starts at a position relative to the current position, and 2 if the range starts at a position relative to the end of the file, 1.sub.-- start 201 is the offset, relative to the location specified by 1.sub.-- whence, of the beginning of the range to be locked, 1.sub.-- len 202 is the size of the range to be locked, 1.sub.-- pid 204 is the process id of the lock's owner, returned by fcntl in response to the F.sub.-- GETLK command, 1.sub.-- sysid 203 is the node id of the node where the lock's owner resides. Locks are associated with open files, and it is natural to place lock information with the other information about an open file, in the file's inode structure. In the AIX operating system this is impractical, the inode structure has a fixed size and cannot contain the variable amount of data that could be associated with the locks on a file. Instead, the lock information is stored so that it is reached from the inode structure 210, FIG. 19, and not contained within it. The data associated with file locks is kept in a linked list pointed to by a field 220 of the inode structure 210. This linked list 221, 222, 223 is a list of entries in a table called the lock table 215. Each entry of the lock table has the following form:
______________________________________
struct filock {
struct flock set;
union {
int wakeflg;
struct {
unsigned long sysid;
short pid;
} blk;
} stat;
struct filock *prev;
struct filock *next;
}
______________________________________
The filock structures 221, 222, 223 are chained together into separate lists, one for each file currently having any locks set. The head of the list is pointed to by a member of the file's inode structure 220. One additional list of filock structures is maintained by the AIX operating system. This list is the sleep list 230, 231, 232, FIG. 20, and is pointed to by the sleeplcks 229. The sleep list has one entry for each process currently trying to establish a lock but prevented from doing so (and hence asleep) because of a preexisting, interfering lock. When used as elements of a linked list 221, 222, 223 of locks on a file, members of the filock structure have the following meanings:
______________________________________
set 300 is a flock structure, as shown in FIG. 18,
containing a description of the locked region
and the process id and node id of the process
owning the lock,
stat.wakeflg 304 is set when some process is asleep,
waiting for the lock corresponding to this
entry to be released,
stat.blk.sysid and stat.blk.pid are not used,
prev 302 and next 303 are pointers to the previous and
next elements in the (doubly linked) list.
______________________________________
When used as elements of the sleep list 230, 231, 232, the members of the filock structure FIG. 21 have the following meanings:
______________________________________
set 300 is a flock structure, as shown in FIG. 18,
containing a description of the region that the
sleeping process wants to lock along with the
sleeping process's process id and node id,
stat.wakeflg 304 is not used,
stat.blk.sysid 304 is the node id of the process
owning the lock that blocked the request
described by the set member,
stat.blk.pid 301 is the process id of the process
owning the lock that blocked the request
described by the set member,
prev 302 and next 303 are pointers to the
previous and next elements in the (doubly
linked) list.
______________________________________
Although there are two different system calls that can be used to perform locking in the AIX operating system, both are implemented by calling a routine named reclock. This routine operates as follows:
______________________________________
[reclock]
INPUTS:
inode pointer, pointer to inode for file to
be locked,
file pointer, pointer to file structure for
file to be locked the file
structure contains the current
offset and open mode of the file,
request, a pointer to an flock structure
containing a description of region
to be locked or unlocked,
OUTPUT:
returns 0 if lock request is granted,
otherwise returns error indication.
PROCEDURE:
/* put request into a standard form */
convert range (l.sub.-- whence, l.sub.-- start, and l.sub.-- len)
in request to form where l.sub.-- start is relative
to beginning of file;
/* get lock list */
lock list is pointed to by member of inode
structure;
/* attempt request */
if request is to unlock
scan lock list for locks owned by process
that called reclock;
unlock the portions of any such locks that
intersect the request's range;
wakeup any processes that were sleeping on
a locked range that has had portions
unlocked;
return 0 /* success */
/* otherwise, request is to set a lock */
/* test for interfering locks on the file */
while there is an interfering lock
/* check for deadlock */
if request causes a deadlock
return error;
if there is no room in lock table
/* i.e. can't put caller to sleep
*/
return error;
/* now put caller to sleep;
*/
/* an entry of the lock table is
*/
/* chained onto the sleep list;
*/
/* the sleep list has one entry for
*/
/* each process that is asleep and
*/
/* waiting for a lock range to be
*/
/* unlocked; the lock table entry on
*/
/* the sleep list identifies both
*/
/* the sleeping process and the
*/
/* process that owns the lock that
*/
/* the sleeper is waiting for.
*/
add entry to sleep list;
/* now we are almost ready to put
*/
/* the running process to sleep;
*/
/* first however, release inode if
*/
/* it is locked; this could happen
*/
/* if this code is being executed
*/
/* during a read or write of a file
*/
/* in enforced-locking mode
*/
if inode is locked
release inode;
/* finally ready so */
sleep, catch interrupts;
if interrupted from sleep
return error;
else /* normal awakening;
*/
/* interfering lock is gone;
*/
/* no longer sleeping so
*/
remove entry from sleep list;
if inode was previously locked
relock inode;
/* now loop back and scan the entire
*/
/* list again, locks could have
*/
/* changed while we were sleeping
*/
}
/* now, no interfering locks are present
*/
add the new lock to the file's lock list;
/* note that some entries may be merged
*/
if request could be added to lock list
return 0; /* success
*/
else
/* an error, perhaps there is no more
*/
/* room in the lock table
*/
return error;
______________________________________
In a distributed environment, processes at more than one node can have a single file open at the same time. Each time a lock is added or removed, a file's entire lock list may have to be scanned and updated. A straightforward design of such a system would keep the lock list and sleep list at the file's server: each time a lock is applied, requests are sent to the server (unless a process local to the server is applying the lock) to perform the necessary actions on the lock list and possibly sleeping process list. A system based on this straightforward design has the disadvantage of unnecessary network traffic and delays when the only process having a file open are all running at a single non-server node. Most often, files in an AIX operating system are opened by a single process; if the process is running at a client (non-server) node, the straightforward design described above would introduce the undesirable costs of communicating with a remote server in this common situation each time a lock was changed or tested. Sometimes, a file in an AIX operating system is open by many different processes at the same time, all of which could be located at different nodes in a distributed environment. Any design for file and record locking in an AIX operating system should avoid the costs of the straightforward design in the simple more common cases and work properly, even if not as efficiently, in the less common more complex cases. The invention described in this application accomplishes these conflicting goals. One solution to the problem might be to keep copies of the lock list and sleep list at all nodes where it could be useful. The problem with this approach is that the lists don't stay consistent with each other as changes are being made unless one list is denoted the master, in which case all changes must be communicated with the master anyway and no advantage over the straightforward design are realized, or changes to each list are carefully negotiated with other nodes having copies of the lists, producing additional undesirable overhead in network traffic and delays each time a lock is modified. The invention described in this application keeps only one copy of the lock list for each file. The lock list information is kept at the server, step 404 of FIG. 22A, when there are several processes located at different nodes having the file open, steps 406, 402, 403, 404, and 405 of FIG. 22A, and the information is kept at the non-server node, step 413 of FIG. 22A, in the frequent case of all processes with the file open running at a single node steps 406, 411, 412, 413, and 414 of FIG. 22A. The problems of multiple copy consistency are avoided, and the inefficiencies of requiring network messages for each lock operation in the common case where all opens are at one node are also avoided. There are two important implications of this architecture. First, processes may have to use remote procedure calls (RPC)s to set or test locks. These RPCs will run on the file's server. Second, when the synch mode of a file changes, the file's lock list may have to be moved from the client to the server, steps 502, 504, 505, and 506 of FIG. 22B, or vice-versa, steps 502, 504, 507, and 508 of FIG. 22B. The entries of an inode's lock table correspond to locks over segments of the inode's file. To represent a lock, a lock list entry must contain information identifying the range of bytes locked, the type of lock (read or write), the owner of the lock. In standalone UNIX operating system a process that tries to establish a lock may have to wait for an existing lock to clear first. Before waiting (going to sleep) the process must check the sleep list to insure that no deadlock will occur if it does wait. A waiting process has its proc table use the W.sub.-- CHAN field of the proc table to point to the lock table entry that it is waiting on. In a distributed system, waiting is not as easy. There are two ways to wait on a blocking lock: 1) directly on a local lock list entry and 2) indirectly on a server lock list entry. Direct waiting is identical to the standalone waiting described above. It is used anytime that a process must wait for a lock that occurs locally in a lock table. It is important to remember that a lock list for a file resides in only one node. If the calling process is not in the same node then the lock list is in the server. A process that attempts to lock a region of a file that has its lock list located in a remote node (server) waits on the lock indirectly. This indirect waiting is done by an RPC that invokes a transaction program in the server and waits on the lock. In a standalone UNIX operating system, a process never enters the SLEEP state if a lock can be granted or if waiting could create a deadlock. In a distributed system, a process performing a lock request that does not reside in the same node as the lock table always enters the SLEEP state, at least briefly. It must do so while it is waiting for the RPC to return. In order to avoid unnecessary network communication, a process that is waiting for the reply from a dfs.sub.-- flock RPC will not know if it is waiting because the RPC transaction program is in turn waiting for a blocking lock or if it is waiting because the transaction program has not finished running in the server where no blocking lock was found. When a lock is first applied to a file that has no other locks, an entry is made in the server lock table if the file is open in FULLSYNCH mode or READONLY mode, step 403 of FIG. 22A; an entry is made in the client lock table if the file is open in ASYNCH mode, step 412 of FIG. 22A. Additional entries are made in the same table and chained together to form a file lock list, as long as no open, close, or chmod system calls change the file synchronization mode. (Note that chmod can change the file sync mode by placing a file in enforced-locking mode, steps 500 and 501 of FIG. 22B. A file in enforced-locking mode is always treated as if it is in FULLSYNCH mode, regardless of the number of processes having the file open.) When a file's synch mode changes tested in steps 502 and 504 of FIG. 22B, due to an open for example, steps 500 and 501 of FIG. 22B, the lock list and sleeping processes are moved from one node to another, steps 505, 506, 507, and 508 of FIG. 22B. Files in enforced-locking mode have FULLSYNCH synchronization mode, and like other FULLSYNCH files, the lock lists for enforced-locking mode files are kept at the server, step 404 of FIG. 22B. Complications that must be addressed by the invention include the problems of when is the lock list information moved between nodes, how is the lock list information moved between nodes, and how are the processes sleeping while waiting for locks managed. Although the data structures used in AIX(TM) to support the file and record locking in a distributed environment are the same as those described above for standalone operation, the procedures used to add and remove locks are different in a distributed system. The system calls lockf and fcntl on a client node, (the test at step 401 of FIG. 22A is used to determine this), that is a node in a distributed environment that does not contain the file to be locked, are implemented with calls to the raix.sub.-- flock. The routine raix.sub.-- flock works as follows:
______________________________________
[raix.sub.-- flock]
INPUTS:
vnode pointer, pointer to vnode for file to
be locked,
file pointer, pointer to file structure for
file to be locked, the file
structure contains the current
offset and open mode of the file,
request, a pointer to an flock structure
containing a description of region
to be locked or unlocked,
OUTPUT:
returns 0 if lock request is granted,
otherwise returns error indication.
PROCEDURE:
/* put request into standard form */
convert range (l.sub.-- whence, l.sub.-- start, and
l.sub.-- len) in request to form where
l.sub.-- start is relative to beginning of
file;
/* keep trying until error or done */
while( TRUE )
if file is in ASYNCH mode (step 406 of FIG. 22A)
{
/* do local processing */
/* lock the file's surrogate inode,
*/
/* waiting until we can. File's
*/
/* surrogate inode is pointed to by a
*/
/* member of a file's vnode structure
*/
wait until surrogate inode is unlocked,
then lock it;
/* could have slept in the previous
*/
/* step, so test synch mode again
*/
if file is not in ASYNCH mode
/* mode has changed so try again
*/
goto retry;
/* Ok, still in ASYNCH mode */
/* step 411 of FIG. 22A */
if request is to unlock a region
scan lock list for locks owned by
calling process;
unlock the portions of any locks
that intersect the unlock
request's range;
wakeup any processes that were
sleeping on a locked range
that has had portions;
goto success;
/* else, request is to set a lock */
/* test for any interfering locks */
while there is an interfering lock
{
/* check for deadlock */
if request causes deadlock
/* can't grant it */
goto errorexit;
if there is no room in lock table
/* can't put caller to sleep */
goto errorexit;
/*now put caller to sleep;
*/
/*an entry of the lock table is
*/
/*chained onto the sleep list;
*/
/*the sleep list has one entry for
*/
/*each process that is asleep and
*/
/*waiting for a lock range to be
*/
/*unlocked;the lock table entry on
*/
/*the sleep list identifies both
*/
/*the sleeping process and the
*/
/*process that owns the lock that
*/
/*the sleeper is waiting for.
*/
add entry to sleep list;
/*now we are almost ready to put
*/
/*the running process to sleep;
*/
/*first however, release inode if
*/
/*it is locked; this could happen
*/
/*if this code is being executed
*/
/*during a read or write of a file
*/
/*in enforced-locking mode
*/
if inode is locked
release inode;
/* finally ready so */
sleep, catch interrupts;
if interrupted from sleep
goto errorexit;
/* normal awakening */
/* interfering lock is gone
*/
/* no longer sleeping so
*/
remove entry from sleep list;
/* has synch mode changed?
*/
if file sync mode is not ASYNCH
goto retry;
if surrogate inode was previously
locked
relock surrogate inode;
/* now loop back and try again */
}
/* now, no interfering locks exist */
/* step 412 of FIG. 22A */
add new lock to the file's lock list;
/* step 413 of FIG. 22A */
if request could be added to list
goto success;
/* success */
else
goto errorexit;
}
else /* file is not in ASYNCH mode */
{
request lock at server,
use dfs.sub.-- flock rpc;
/* dfs.sub.-- flock rpc will invoke
*/
/* aix.sub.-- flock at the server to
*/
/* perform the remote locking
*/
if error
goto errorexit;
else if no errors
goto success
/* neither error nor success,
*/
/* lock request happened during
*/
/* a synch mode change so just
*/
/* retry it */
}
retry:
if surrogate was unlocked
unlock surrogate;
/* now loop back and try again */
}
errorexit:
if surrogate was unlocked
unlock surrogate;
return error;
success:
if surrogate was unlocked
unlock surrogate;
return 0;
______________________________________
This function, raix.sub.-- flock, is invoked by calls to lockf or fcntl for remote files. That is, when a process at a client node uses lockf or fcntl on a file at a server node, raix.sub.-- flock will be executed on the client (NO branch of test at step 401 of FIG. 22A). If the file is open at the client in ASYNCH file synchronization mode, raix flock will perform only local operations (YES branch of test at 406 of FIG. 22A); if the file is open at the client in a mode other than ASYNCH (NO branch of test at 406 of FIG. 22A), raix.sub.-- flock will use the dfs.sub.-- flock rpc, causing a kernel process to run in the server, steps 402, 403, 404, and 405 of FIG. 22A. This kernel process will lock or unlock the specified range at the server, where, in this case, the file's lock list resides. The dfs.sub.-- flock rpc sent by the client causes the dfs.sub.-- flock function to be run, by a kernel process, at the server. The dfs.sub.-- flock function's operation can be described as follows:
______________________________________
[dfs.sub.-- flock]
INPUTS:
(received as a part of dfs.sub.-- flock rpc)
file handle, handle for file to be locked,
file structure, file structure for the file to be
locked containing the current offset and open
mode of the file,
request, a structure containing a description of
the the region to be locked or unlocked,
OUTPUT:
(returned as a part of reply to dfs.sub.-- flock rpc)
returns 0 if lock request is granted,
returns error number if error,
returns EBUSY if operation failed and should be
retried because of synch mode changes
PROCEDURE:
if there is no vnode corresponding to the file
handle
/* file is no longer open */
send error back in reply;
/* requestor cannot still be awaiting
*/
/* reply, since that would imply that
*/
/* the file was still open
*/
}
perform lock operation using aix.sub.-- flock;
/* aix.sub.-- flock is called indirectly though
*/
/* vn.sub. -- lockf */
if error
send back error in reply;
else EBUSY
send back EBUSY in reply;
else
send back reply with indication of success
with return confirmation requested;
if return confirmation indicates
that no process received reply
{
/* original requesting process is
*/
/* gone, so */
unlock original requested lock;
}
______________________________________
The dfs.sub.-- flock function invokes the vn.sub.-- lockf vnode operation to perform locking at the server in response to the dfs.sub.-- flock RPC request. The vn.sub.-- lockf vnode operation at the server will map into a call of the aix.sub.-- flocl function (the YES branch of test at 401 of FIG. 22A). This function is similar to the raix.sub.-- flock routine, but has to be concerned with the manipulation of the file access structure lock. Notice that after attempts to acquire this lock and the lock on the inode, aix.sub.-- flock has to allow for the possibility of changes in the file's synchronization mode. Sleeping could have occurred while waiting for these locks. During the sleep periods, additional opens or closes could have been performed on the file. A description of the detailed operation of aix.sub.-- flock follows:
______________________________________
[aix.sub.-- flock]
INPUTS:
vnode pointer, pointer to vnode for file to
be locked,
file pointer, pointer to file structure for
file to be locked, the file
structure contains the current
offset and open mode of the file,
request, a pointer to an flock structure
containing a description of region
to be locked or unlocked,
OUTPUT:
returns 0 if lock request is granted,
otherwise returns error indication.
PROCEDURE:
/* put request into a standard form */
convert range (l.sub.-- whence, l.sub.-- start, and l.sub.-- len)
in request to form where l.sub.-- start is relative
to beginning of file;
/* get lock list, step 402 of FIG. 22A */
lock list is pointed to by member of inode
structure, inode structure is pointed to
by member of the vnode structure;
/* get file access lock */
wait for file access lock and lock it;
/* could have slept, check mode */
if file synchronization mode is ASYNCH
goto ebusy;
/* notice that this cannot happen when
*/
/* there is a file open at the server
*/
/* attempt request */
if request is to unlock
scan lock list for locks owned by process
that called reclock;
unlock the portions of any such locks that
intersect the request's range;
wakeup any processes that were sleeping on
a locked range that has had portions
unlocked;
goto success;
/* otherwise, request is to set a lock */
/* test for interfering locks on the file */
while there is an interfering lock
/* check for deadlock */
if request causes a deadlock
goto errorexit;
if there is no room in lock table
/* i.e. can't put caller to sleep
*/
goto errorexit;
/* now put caller to sleep;
*/
/* an entry of the lock table is
*/
/* chained onto the sleep list;
*/
/* the sleep list has one entry for
*/
/* each process that is asleep and
*/
/* waiting for a lock range to be
*/
/* unlocked; the lock table entry on
*/
/* the sleep list identifies both
*/
/* the sleeping process and the
*/
/* process that owns the lock that
*/
/* the sleeper is waiting for.
*/
add entry to sleep list;
/* now we are almost ready to put
*/
/* the running process to sleep;
*/
/* first however, release inode if
*/
/* it is locked; this could happen
*/
/* if this code is being executed
*/
/* during a read or write of a file
*/
/* in enforced-locking mode
*/
if inode is locked
release inode;
release file access structure lock;
/* finally ready so */
sleep, catch interrupts;
if interrupted from sleep
goto errorexit;
if synchronization mode is ASYNCH
/* it changed during sleep */
goto ebusy; /* need to retry */
remove entry from sleep list;
lock file access structure lock;
if inode was previously locked
relock inode;
/* now loop back and scan the entire
*/
/* list again, locks could have
*/
/* changed while we were sleeping
*/
}
/* now, no interfering locks are present
*/
add the new lock to the file's lock list,
step 403 of FIG. 22A;
/* note that some entries may be merged,
step 404 of FIG. 22A */
if request could be added to lock list
goto success; /* success
*/
else
/* an error, perhaps there is no more
*/
/* room in the lock table
*/
goto errorexit;
errorexit:
release file access structure lock;
return error;
ebusy:
release file access structure lock;
return EBUSY;
success:
return 0;
______________________________________
During the period of time that a file synchronization mode change is happening, the structures describing the file are being updated at both the server and some non-server nodes. Because the updates involve communication with a remote node, the processor can be preempted after the updates have started and before they are finished. To prevent processes from finding partially updated and hence inconsistent information about a file during the time that the synchronization mode is changing, the AIX operating system uses file access structure locks. Each opened file has a file access structure lock that can be set to indicate to other processes that the operating system information about the file is possibly inconsistent. The procedure aix.sub.-- flock, shown above, goes to sleep waiting on an interfering lock under some conditions. Before doing so it is important that the file access structure lock be released. If aix.sub.-- flock did not release the file access structure lock before waiting for some locks, a deadlock could occur. The source code for the file access structure is provided below with some descriptive information to show the detailed logic:
______________________________________
STRUCT FILE.sub.-- ACCESS
{ /*
File Access Structure Pointer
*/
STRUCT FILE.sub.-- ACCESS *FA.sub.-- NEXT; ;
/*
File Access Structure Flag
*/
SHORT FA.sub.-- FLAG; /*
File Access Structure Total Users
*/
SHORT FA.sub.-- COUNT; /*
File Access Structure Read/Only Count
*/
SHORT FA.sub.-- OROCNT; /*
File Access Structure Read/Write Count
*/
SHORT FA.sub.-- ORWCNT; /*
File Access Structure Executing Processes
*/
SHORT FA.sub.-- TXTCNT; /*
File Access Structure Node Structure Ptr.
*/
STRUCT NODE *FA.sub.-- NID; /*
File Access Structure Node ID
*/
INT FA.sub.-- NID; /*
File Access Structure S.sub.-- INODE Pointer
*/
STRUCT INODE *FA.sub.-- SIP; };
______________________________________
File Access Structure Lock The file access structure lock fas.sub.-- lock is used to synchronize the use of the inodes and surrogate inodes (s.sub.-- inode) for open files in a distributed file system (DFS). The synchronization is performed to avoid a deadlock situation which can occur if an inode and the s.sub.-- inodes are locked. In a standalone AIX operating system, execution of system calls that require access to a file F are serialized by locking the inode for F during the entire execution time of any system call for that file. In DFS, if file F is open at a remote node C, a s.sub.-- inode is created at node C to represent file F. Thus, two resources are involved: the inode for the specific file at the server node where the file resides, and the s.sub.-- inode at the client node where the file is open. To serialize system calls executing at client C, the s.sub.-- inode for file F is locked during the execution time for each call. If an access to the server is required to read a block of data not available in the client cache, the inode for file F is also locked. Locking the inode for file F in the server and the s.sub.-- inode for file F in the client for the entire execution time of each system call can lead to a deadlock situation if the order in which the two resources are acquired is not always carried out in the same order. Typically, the s.sub.-- inode is locked first and then the server is accessed via a remote procedure call (RPC) and the inode is locked. However, there are some exceptions to the above order. Under certain conditions, the server may lock the inode and then send a RPC to the client which requires the locking of the s.sub.-- inode. A deadlock can occur in any one of the following situations in which two operations are currently executing O1 and O2: a) O1 is executing at a client node. O1 locks the s.sub.-- inode and tries to lock the inode in the server for a read operation. b) O2 is executing in the server. O2 locks the inode and initiates a RPC to the client node to open a file. The execution of the RPC request in the client node waits on the s.sub.-- inode to lock it. Because both operations are executing and require the same two resources and each have acquired one and are waiting on the other locked resource, a deadlock situation is present. In examining the cause, note that the deadlock occurs during the execution of the RPC from the server to the client. The inode on the server is locked first and an attempt is made to lock the s.sub.-- inode. This is the reverse of most cases where the s.sub.-- inode is locked first and then sends a RPC to lock the inode. To prevent the above problem from occurring, the server could unlock the inode before originating a RPC to lock the s.sub.-- inode to the client. Unlocking the inode during the execution of the open operation will solve the above problem; however, it complicates the sync mode change management for open files since more than one open and/or close operation can occur at the server in parallel. It may also introduce another problem as shown in FIG. 17. In FIG. 17 file F at 10 is open in ASYNC mode by only one process in client node C-1 at 20. Two operations are in progress: a close operation from C-1 at 20 and an open operation at 60 for the same file F at label 10 from another client C-2 at label 40. The close operation from C-1 at label 20 will lock the s.sub.-- inode (which has a use count of 1) and sends a "dfs.sub.-- close" RPC at label 50 to the server at label 30. The open operation from C-2 at label 40 sends a "dfs.sub.-- open" RPC at label 70 to the server at label 30. This RPC arrives at the server and executes before the "dfs.sub.-- close" RPC at label 50 from C-1 at label 20. The s.sub.-- mode for file F is ASYNC, so the server unlocks the inode and sends a "dfs.sub.-- chng.sub.-- sync mode" RPC at label 80 to C-1 at label 20 requesting that file F at label 10 be changed to FULLSYNC s.sub.-- mode. This RPC will arrive at C-1 at label 20 and wait for the s.sub.-- inode to be unlocked. Next, the "dfs.sub.-- close" RPC at label 50 arrives at the server. Since the inode for file F at label 10 is not locked at the server, the close operation executes at the server and a "dfs.sub.-- close.sub.-- ack" RPC at label 90 is sent to C-1 at label 20. When the "dfs.sub.-- close.sub.-- ack" RPC at label 90 arrives at C-1 at label 20, the use count on the s.sub.-- inode is decremented and since the use count's value is zero, the s.sub.-- inode is released at label 100. This leaves no s.sub.-- inode for the sync mode change to be applied to in C-1 in label 20. A solution to this problem is to have the sync mode change procedure increment the use count of the s.sub.-- inode before waiting on it. However, this approach raises more management headaches for the file management system. A better approach is to introduce a new lock, the file access structure lock (fas.sub.-- lock). Use of the fas.sub.-- lock will eliminate the inode from being a critical resource. The two critical resources will be the s.sub.-- inode in the client node and the fas.sub.-- lock at the server. To prevent a deadlock, any operation executing at a client node which requires holding the fas.sub.-- lock should unlock the s.sub.-- inode before a RPC is sent to the server. Operations that generate a RPC from the server to clients must acquire the fas.sub.-- lock before sending a RPC. Examples of situations in a UNIX operating system and/or an AIX operating system environment are:
______________________________________
Remote Procedure Calls (RPC):
* DFS.sub.-- OPEN * DFS.sub.-- CREATE
* DFS.sub.-- CLOSE * DFS.sub.-- GET.sub.-- ATTR
* DFS.sub.-- SET.sub.-- ATTR
* DFS.sub.-- LOOKUP
* DFS.sub.-- CHNG.sub.-- SYNC.sub.-- MODE UNIX System Calls From
Server Processes:
* OPEN * CLOSE
* CREAT * STAT
* FULLSTAT * CHMOD
* EXIT
______________________________________
The above UNIX operating system and AIX operating system operations correspond to the following vn.sub.-- ops:
______________________________________
| ||||||