초록 ▼

A read-write access to a file in a file server includes an initial metadata access step, an asynchronous read or write of file data, and a metadata commit step. In order to parallelize access to a range locking database, an inode and indirect file block mapping database, and a pre-allocation data ba

A read-write access to a file in a file server includes an initial metadata access step, an asynchronous read or write of file data, and a metadata commit step. In order to parallelize access to a range locking database, an inode and indirect file block mapping database, and a pre-allocation data base, operations are pipelined within the metadata access step and also within the metadata commit step. The pipelined operations within the metadata access step include a first stage of range locking, a second stage of reading block mapping metadata, and a third stage of reading and updating a pre-allocation map for write access. The pipelined operations within the metadata commit step include a first stage of releasing range locks, a second stage of accessing old block metadata for write access, and a third stage of updating metadata and flushing the pre-allocation map for write access.

대표청구항 ▼

What is claimed is: 1. A method of operating a file server computer for providing clients with concurrent write access to respective byte ranges of a file in storage of the file server computer, the method comprising: the file server computer responding to a concurrent write request from a client b

What is claimed is: 1. A method of operating a file server computer for providing clients with concurrent write access to respective byte ranges of a file in storage of the file server computer, the method comprising: the file server computer responding to a concurrent write request from a client by accessing metadata of the file to obtain a block mapping for the concurrent write request, and then writing data from the client to the file using the block mapping for the concurrent write request, and then committing metadata changes to the file, the metadata changes including change in an allocation of file blocks to the file; wherein the file server computer accesses the metadata of the file to obtain the block mapping for the concurrent write request by accessing a range locking database in the file server computer to set a respective exclusive byte range lock upon one of the respective byte ranges of the file, accessing a file block mapping database in the file server computer, and accessing a pre-allocation database in the file server computer to pre-allocate a new file block to which the data from the client is written, and wherein the file server computer commits the metadata changes to the file by accessing the range locking database to release the respective exclusive byte range lock, accessing the file block mapping database, accessing the pre-allocation database, and writing the metadata changes to the storage of the file server computer to commit the new file block to the file in the storage the file server computer. 2. The method as claimed in claim 1, wherein the range locking database, the file block mapping database, and the pre-allocation database are accessed in memory of the file server computer. 3. The method as claimed in claim 2, which includes the file server computer maintaining the file block mapping database as a cache of on-disk file system metadata, wherein the file server computer maintains the file block mapping database as a hierarchical data structure including an inode containing metadata of an on-disk inode of the file, and including an indirect block containing metadata of an on-disk indirect block of the file. 4. The method as claimed in claim 3, wherein the metadata changes include changes to metadata of the indirect block of the file, and wherein the method includes the file server computer accessing the file block mapping database to commit the metadata changes by acquiring a shared lock on the inode in the file block mapping database, and then acquiring an exclusive lock on the indirect block in the file block mapping database, and then writing the changes to the metadata of the indirect block of the file to the indirect block in the file block mapping database. 5. The method as claimed in claim 1, wherein the file server computer commits the metadata changes to the file by accessing the file block mapping database to acquire exclusive access to old block metadata of the file, accessing the pre-allocation database to acquire exclusive access to new block metadata of the file, and then transferring the new block metadata from the pre-allocation database to the file block mapping database. 6. The method as claimed in claim 1, wherein the file server computer accesses the metadata of the file to obtain the block mapping for the file by accessing the range locking database to set the respective exclusive byte range lock, and then accessing the file block mapping database, and then accessing the pre-allocation database, and wherein the file server computer commits the metadata changes to the file by accessing the range locking database to release the respective exclusive byte range lock, and then accessing the file block mapping database, and then accessing the pre-allocation database, and then writing the metadata changes to the storage. 7. The method as claimed in claim 1, wherein the file server computer writes the metadata changes to the storage by writing the metadata changes to a file system log in storage. 8. The method as claimed in claim 1, which further includes the file server computer responding to a concurrent read request from at least one client by: accessing the range locking database to set a respective shared byte range lock, and accessing the file block mapping database to obtain a block mapping for the concurrent read request, and then reading data from the file using the block mapping for the concurrent read request, and sending the data read from the file to said at least one client, and then accessing the range locking database to release the respective shared byte range lock, and writing a file access metadata change to the storage of the file server computer. 9. A method of operating a file server computer for providing clients with concurrent write access to respective byte ranges of a file in storage of the file server computer, the method comprising: the file server computer responding to a concurrent write request from a client by accessing metadata of the file to obtain a block mapping for the file, and then asynchronously writing data from the client to the file using the block mapping for the file, and then committing metadata changes to the file the metadata changes including a change in an allocation of file blocks to the file, wherein the file server computer accesses the metadata of the file to obtain the block mapping for the file by accessing a range locking database in the file server computer to set a respective exclusive byte range upon one of the respective byte ranges of the and then accessing a file block mapping database in the file server computer to read file block metadata, and then accessing a pre-allocation database in the file server computer to pre-allocate a new file block to which the data from the client is written; wherein the file server computer commits the metadata changes to the file by accessing the range locking database to release the respective exclusive byte range lock, and then accessing the file block mapping database to acquire exclusive access to old block metadata, accessing the pre-allocation database to acquire exclusive access to new block metadata, and then transferring the new block metadata from the pre-allocation database to the file block mapping database to commit the new file block to the file in the storage of the file server computer. 10. The method as claimed in claim 9, which includes the file server computer maintaining the file block mapping database in memory of the file server computer as a cache of on-disk file system metadata, wherein the file block mapping database is maintained as a hierarchical data structure, the hierarchical data structure including an inode containing metadata of an on-disk inode of the file, and including an indirect block containing metadata of an on-disk indirect block of the file. 11. The method as claimed in claim 10, wherein the metadata changes include changes to metadata of the indirect block of the file, and wherein the method includes the file server computer accessing the file block mapping database to commit the metadata changes by acquiring a shared lock on the inode in the file block mapping database, and then acquiring an exclusive lock on the indirect block in the file block mapping database, and then writing the changes to the metadata of the indirect block of the file to the indirect block in the file block mapping database. 12. The method as claimed in claim 9 which further includes the file server computer responding to a concurrent read request from at least one client by: accessing the range locking database to set a respective shared byte range lock, and accessing the file block mapping database to obtain a block mapping for the concurrent read request, and then reading data from the file using the block mapping for the concurrent read request, and sending the data read from the file to said at least one client, and then accessing the range locking database to release the respective shared byte range lock, and writing a file access metadata change to the storage of the file server computer. 13. The method as claimed in claim 9, wherein the committing of the metadata changes to the file by the file server computer further includes the file server writing the metadata changes to a file system log in the storage. 14. A file server comprising: storage for storing a file, at least one processor coupled to the storage for access to the file, and memory for containing a range locking database, a file block mapping database, and a pre-allocation database, wherein said at least one processor is coupled to the memory and programmed for providing clients with concurrent write access to respective byte ranges of the file by the file server responding to a concurrent write request from a client by accessing metadata of the file to obtain a block mapping for the concurrent write request, and then writing data from the client to the file using the block mapping for the concurrent write request, and then committing metadata changes to the file, the metadata changes including a change in an allocation of file blocks to the file, wherein said at least one processor is programmed for accessing the metadata of the file to obtain the block mapping for the concurrent write request by accessing the range locking database in the memory to set a respective exclusive byte range lock upon one of the respective byte ranges of the file, accessing the file block mapping database in the memory, and accessing the pre-allocation database in the memory to pre-allocate a new file block to which the data from the client is written, and wherein said at least one processor is programmed for committing the metadata changes to the file by accessing the range locking database in the memory to release the respective exclusive byte range lock, accessing the file block mapping database in the memory, accessing the pre-allocation database in the memory, and writing the metadata changes to the storage to commit the new file block to the file in the storage of the file server. 15. The file server as claimed in claim 14, wherein said at least one processor is programmed for maintaining the file block mapping database in the memory as a cache of on-disk file system metadata, the cache of on-disk file system metadata including a hierarchical data structure, the hierarchical data structure including an inode containing metadata of an on-disk inode of the file, and an indirect block containing metadata of an on-disk indirect block of the file. 16. The file server as claimed in claim 15, wherein the metadata changes include changes to metadata of the indirect block of the file, and wherein said at least one processor is programmed for accessing the file block mapping database to commit the metadata changes by acquiring a shared lock on the inode in the file block mapping database, and then acquiring an exclusive lock on the indirect block in the file block mapping database, and then writing the changes to the metadata of the indirect block of the file to the indirect block in the file block mapping database. 17. The file server as claimed in claim 14, wherein said at least one processor is programmed for committing the metadata changes to the file by accessing the file block mapping database to acquire exclusive access to old block metadata of the file, accessing the pre-allocation database to acquire exclusive access to new block metadata of the file, and then transferring the new block metadata from the pre-allocation database to the file block mapping database. 18. The file server as claimed in claim 14, wherein said at least one processor is programmed for accessing the metadata of the file to obtain the block mapping for the file by accessing the range locking database in the memory to set the respective exclusive byte range lock, and then accessing the file block mapping database in the memory, and then accessing the pre-allocation database in the memory, and wherein said at least one processor is programmed for committing the metadata changes to the file by accessing the range locking database in the memory to release the respective exclusive byte range lock, and then accessing the file block mapping database in the memory, and then accessing the pre-allocation database in the memory, and then writing the metadata changes to the storage. 19. The file server as claimed in claim 14, wherein said at least one processor is programmed to write the metadata changes to the storage by writing the metadata changes to a file system log in storage. 20. The file server as claimed in claim 14, wherein said at least one processor is further programmed for responding to a concurrent read request from at least one client by: accessing the range locking database in the memory to set a respective shared byte range lock, and accessing the file block mapping database in the memory to obtain a block mapping for the concurrent read request, and then reading data from the file using the block mapping for the concurrent read request, and sending the data read from the file to said at least one client, and then accessing the range locking database in the memory to release the respective shared byte range lock, and writing a file access metadata change to the storage. 21. A method of operating a file server computer having storage storing a file, memory containing a range locking database, a file mapping database, and a pre-allocation database, and at least one processor coupled to the storage for access to the file and coupled to the memory for access to the range locking database, the file mapping data base, and the pre-allocation database, and said method comprising: said at least one processor providing clients with concurrent read-write access to non-overlapping byte ranges of the file including concurrent write access changing an allocation of file blocks to the file in the storage by pipelined processing of client requests for read-write access to the file though a sequence of three steps including a first step of metadata access followed by a second step of asynchronous reading or writing to the file followed by a third step of metadata commitment; said at least one processor pipelining operations within the first step of metadata access through a first stage of byte range locking for concurrent setting of byte range locks upon the non-overlapping byte range of the file, followed by a second stage of reading block mapping metadata, followed by a third stage of reading and updating a pre-allocation map for write access; and said at least one processor pipelining operations within the third step of metadata commitment through a first stage of releasing the byte range locks, followed by a second stage of accessing old block metadata for write access, followed by a third stage of updating metadata and flushing the pre-allocation map for write access. 22. The method as claimed in claim 21, wherein the updating of the metadata includes changes to metadata of an indirect block of the file, and wherein said at least one processor accesses the file block mapping database to commit the metadata changes by acquiring a shared lock on the inode in the file block mapping database, and then acquiring an exclusive lock on the indirect block in the file block mapping database, and then writing the changes to the metadata of the indirect block of the file to the indirect block in the file block mapping database. 23. The method as claimed in claim 21, wherein said at least one processor commits the metadata changes to the file by accessing the file block mapping database to acquire exclusive access to old block metadata of the file, accessing the pre-allocation database to acquire exclusive access to new block metadata of the file, and then transferring the new block metadata from the pre-allocation database to the file block mapping database. 24. A file server comprising: storage storing a file; at least one processor coupled to the storage for access to the file; and memory containing a range locking database, a file block mapping database, and a pre-allocation database; wherein said at least one processor is coupled to the memory for access to the range locking data base, the file mapping database, and the pre-allocation database, and said at least one processor is programmed to provide clients with concurrent read-write access to non-overlapping byte ranges of the file including concurrent write access changing an allocation of file blocks to the file in the storage by pipelined processing of client requests for read-write access to the file though a sequence of three steps including a first step of metadata access followed by a second step of asynchronous reading or writing to the file followed by a third step of metadata commitment; said at least one processor is programmed to pipeline operations within the first step of metadata access through a first stage of byte range locking for concurrent setting of byte range locks upon the non-overlapping byte range of the file, followed by a second stage of reading block mapping metadata, followed by a third stage of reading and updating a pre-allocation map for write access; and said at least one processor is programmed to pipeline operations within the third step of metadata commitment through a first stage of releasing the byte range locks, followed by a second stage of accessing old block metadata for write access, followed by a third stage of updating metadata and flushing the pre-allocation map for write access. 25. The file server as claimed in claim 24, wherein the updating of the metadata includes changes to metadata of an indirect block of the file, and wherein said at least one processor is programmed to access the file block mapping database to commit the metadata changes by acquiring a shared lock on the inode in the file block mapping database, and then acquiring an exclusive lock on the indirect block in the file block mapping database, and then writing the changes to the metadata of the indirect block of the file to the indirect block in the file block mapping database. 26. The file server as claimed in claim 24, wherein said at least one processor is programmed to commit the metadata changes to the file by accessing the file block mapping database to acquire exclusive access to old block metadata of the file, accessing the pre-allocation database to acquire exclusive access to new block metadata of the file, and then transferring the new block metadata from the pre-allocation database to the file block mapping database.