Flexible and adaptive read and write storage system architecture
AssigneeExanet, Inc.
InventorsShahar Frank, Nir Peleg, Menachem Rosin
Life of this patent
Estimating the term…
Abstract
A distributed shared file system (DSFS) comprising a network file system (NFS) capable of receiving at least a request from at least a client, a distributed cache, a metadata storage containing metadata information related to files stored in the NFS, a mapper capable of handling pointers to point to locations of data within the files and the metadata information, an agent capable of handling said request, and a relocator capable of relocating data within the NFS operative with said agent.
Claims46
A distributed shared file system (DSFS) comprising:
- a network file system (NFS) capable of receiving at least a request from at least a client;
- a distributed cache;
- a metadata storage containing metadata information related to files stored in the NFS;
- a mapper capable of handling pointers to point to locations of data within the files and the metadata information;
- an agent capable of handling said request;
- a relocator capable of relocating data within the NFS operative with said agent.
A method for a write operation initiated by a client using a distributed shared file system (DSFS), wherein said method comprises:
- a) receiving a write request from said client;
- b) retrieving metadata attributes required for performing said write request;
- c) determining from the metadata if write operation is permitted.
- d) if write is not permitted returning a invalid notification, otherwise continuing with the write operation;
- e) writing a log to non-volatile random access memory (NVRAM);
- f) invalidating portions of a distributed cache of said DSFS that related to previous versions of data involved in the write operation;
- g) performing a remap;
- g) notifying completion of said write request.
A method for a read operation initiated by a client using a distributed shared file system (DSFS), wherein said method comprises:
- a) receiving a read request from the client;
- b) retrieving metadata attributes required for performing the read request;
- c) determining if the client had permission to read based on said metadata attributes;
- d) if read is not permitted returning a invalid notification, otherwise getting the data respective of said read request.
Dependencies are inferred from the claim text.