Abstract:
A system and method caches and distributes meta-data for one or more data containers stored on a plurality of volumes configured as a striped volume set (SVS) and served by a plurality of nodes interconnected as a cluster. The SVS comprises one meta 5data volume (MDV) configured to store a canonical copy of certain meta-data, including access control lists and directories, associated with all data containers stored on the SVS, and one or more data volumes (DV) configured to store, at least, data content of those containers. In addition, for each data container stored on the SVS, one volume is designated a container attribute volume (CAV) and, as such, is configured to store ("cache") a io canonical copy of certain, rapidly-changing attribute meta-data, including time stamps and container length, associated with that container.
Abstract:
An apparatus for data storage includes a cluster of NFS servers. Each server has network ports for incoming file system requests and cluster traffic between servers. The apparatus includes a plurality of storage arrays in communication with the servers. The servers utilize a striped file system for storing data. A method for data storage. A method for establishing storage for a file. A method for removing a file from storage. A method for reading data in a file. A method for writing data in a file.
Abstract:
An apparatus for handling file level and block level remote file accesses. The apparatus includes a block level server. The apparatus includes a file level server. The apparatus includes a storage layer implementing an inode layer performing inode operations, and storing data accessed by the file level and block level servers. The apparatus includes a management layer connected to the storage layer underlying the block and file level servers, which performs data management operations upon the underlying data. A method of handling file level and block level network file accesses. The method includes the steps of performing management operation by a management layer for a block level server and a file level server. Then there is the step of performing the servers' data accessing and updating operations using a vnode layer implemented on top of an inode layer. Then there is the step of storing data from the block level server or the file level server in a storage layer connected to the management layer (Fig 1).
Abstract:
A system implementing method for responding to file system requests having file IDs comprising V, a volume identifier specifying the file system being accessed, and R, an integer, specifying the file within the file system being accessed. The system (10) includes D disk elements (12) storing files; a switching fabric (14) connected to the D disk elements (12) to route requests to a corresponding disk element; and N network elements (16) each having a mapping function that, for every value of V, specifies one or more elements (12) from the set D that store the data specified by volume V, which receives the requests, and causes the switching fabric to route the requests by their file ID according to the mapping function.