Shared filesystem for distributed data storage system
AssigneeSap SE
InventorIvan Schreter
Life of this patent
Estimating the term…
Abstract
A method for controlling access to a shared filesystem stored in a distributed data storage system is provided. The method can include storing a file comprising a shared filesystem as an inode object and a series of data block objects comprising the shared filesystem. Responding to a request from a client to open the file can include generating, in the shared filesystem, a client object, an open file object, and a client index object. The client object can be linked to the open file object and the client index object. The open file object and the client index object can be further linked to the inode object to indicate the file being accessed by the client. Related systems and articles of manufacture, including computer program products, are also provided.
Claims16
A distributed data storage system, comprising:
- at least one data processor;
- and
- at least one memory storing instructions which, when executed by the at least one data processor, cause operations comprising:
- storing, at the distributed data storage system, a file that is part of a shared filesystem, the file being stored as an inode object and a series of data block objects in the shared filesystem;
- generating the inode object corresponding to the one or more data blocks storing the file of the shared file system, wherein the inode object is linked to another inode object corresponding to a directory, wherein the inode object and the other inode object are further linked to a directory entry object and/or to a directory entry index object to at least indicate the file corresponding to the inode object is part of the directory corresponding to the other inode object;
- and
- responding to a first request from a client to open the file at least by generating, in the shared filesystem, a first open file object and a client index object, the first open file object and the client index object being linked to a client object corresponding to the client, the first open file object and the client index object further being linked to the inode object to at least indicate the file being accessed by the client.
A method, comprising:
- storing, at the distributed data storage system, a file that is part of a shared filesystem, the file being stored as an inode object and a series of data block objects in the shared filesystem;
- generating the inode object corresponding to the one or more data blocks storing the file of the shared file system, wherein the inode object is linked to another inode object corresponding to a directory, wherein the inode object and the other inode object are further linked to a directory entry object and/or to a directory entry index object to at least indicate the file corresponding to the inode object is part of the directory corresponding to the other inode object;
- and
- responding to a first request from a client to open the file at least by generating, in the shared filesystem, a first open file object and a client index object, the first open file object and the client index object being linked to a client object corresponding to the client, the first open file object and the client index object further being linked to the inode object to at least indicate the file being accessed by the client.
A non-transitory computer readable medium storing instructions, which when executed by at least one data processor, result in operations comprising:
- storing, at the distributed data storage system, a file that is part of a shared filesystem, the file being stored as an inode object and a series of data block objects in the shared filesystem;
- generating the inode object corresponding to the one or more data blocks storing the file of the shared file system, wherein the inode object is linked to another inode object corresponding to a directory, wherein the inode object and the other inode object are further linked to a directory entry object and/or to a directory entry index object to at least indicate the file corresponding to the inode object is part of the directory corresponding to the other inode object;
- and
- responding to a first request from a client to open the file at least by generating, in the shared filesystem, a first open file object and a client index object, the first open file object and the client index object being linked to a client object corresponding to the client, the first open file object and the client index object further being linked to the inode object to at least indicate the file being accessed by the client.
Dependencies are inferred from the claim text.