Abstract: To leverage the attributes of object storage for applications/systems created to interface with a network files system, an object storage backed file system can accept the defined file system commands from the applications/systems and transform the file system commands into requests that target object storage. The file system is “backed” by object storage because attributes and content of file system entities are stored in objects. For instance, content data and metadata of a file are stored in objects in object storage. This object storage backed file system can be considered a bridge between a client perceived hierarchical file system namespace and a flat namespace of an object storage.

Abstract: A system has been designed that uses defined, abstracted object commands to facilitate adaptation to heterogeneous backend targets. The backend targets are heterogeneous at least in terms of data access protocols. The architecture of the system allows the system to adapt to changes in data access protocols and addition of data access protocols. The system can operate as a bridge between multiple instances of multiple file systems and the heterogeneous backend targets. The system directs the abstracted object commands to an object storage adapter. The object storage adapter is designed to route a defined, abstracted object command to at least one of a number of modules that translate the abstracted object command.

Abstract: To leverage the attributes of object storage for applications/systems created to interface with a network files system, an object storage backed file system can accept the defined file system commands from the applications/systems and transform the file system commands into requests that target object storage. The file system is “backed” by object storage because attributes and content of file system entities are stored in objects. For instance, content data and metadata of a file are stored in objects in object storage. This object storage backed file system can be considered a bridge between a client perceived hierarchical file system namespace and a flat namespace of an object storage.

Abstract: A system and method for replicating object-based operations generated based on file system commands. In one aspect, a object storage backed file system cache includes a replication engine that selects, from an intent log, records for multiple transaction groups. Each of the records may associate an object-based operation with a transaction group identifier that is associated with a file system command from which the object-based operation was generated. The replication engine identifies transaction groups that each include at least one object-based operation associated with a same transaction group identifier and reads object data associated with at least one of the object-based operations. The replication engine determines operation dependencies among the transaction groups based on the object data and sequences the transaction groups for replication based on the determined operation dependencies.

Abstract: A system and method for managing file system commands directed to an object storage. The method includes an OSFS cache receiving, from an object backed storage file system, a transaction request that includes a transaction group of one or more object-based operations generated from a file system command. The OSFS cache determines whether the transaction request is an update request, and in response to the determining that the transaction request is an update request, the OSFS cache records the object-based operations in an intent log record that associates the object-based operations with the transaction group. In response to recording all of the object-based operations within the transaction group, the OSFS cache issues a completion signal to the object backed storage file system.