Red Hat, Inc.

Anand Vishweswaran Avati

Pranith Kumar Karampuri

Amar Tumballi Suryanarayan

Shishir Nagaraja Gowda

Jeffrey Jon Darcy

Mohammed Junaid Ahmed

Raghavendra Gowdappa

Vijay Kamalanath Bellur

Vijay Bellur

Doug Williams

Systems and methods implementing a path resolver facilitating client access to a distributed file system. An example method may comprise: receiving, by a processing device, a file identifier comprising a symbolic link; producing, by a user space process being executed by the processing device, a modified file identifier, by replacing a pre-defined sequence of characters within the file identifier by a path to a mount point of a distributed file system; and identifying, in view of the modified file identifier, a data structure comprising information about a file identified by the file identifier.

Path resolver for client access to distributed file systems

Systems and methods for migrating file locks in distributed file systems. An example method may comprise: receiving, by a file system server, over a first connection initiated by a file system client, a connection identifier comprising a file identifier; identifying, in view of the connection identifier, a second connection initiated by the file system client, the second connection associated with a file lock with respect to a file identified by the file identifier; and associating the file lock with the first connection.

Migrating file locks in distributed file systems

A caseless file lookup in a distributed file system is disclosed. A request to store a file in a volume may be received. In response to the request, the type of client system issuing the request may be identified. Based on the type of client system that has been identified, a first hash value or a second hash value may be calculated for the name of the file to generate and assign a hash value to the file. The file may be stored in a storage resource based on the first or second hash value that has been generated for the file.

Caseless file lookup in a distributed file system

Systems and methods for file replication using file content location identifiers. An example method comprises: receiving, by a processing device, an index node number identifying a first index node associated with a file residing on a first file server, the first index node referencing a physical location of contents of the file; identifying a replica of the file residing on a second file server; assigning the index node number of the first index node to a second index node referencing a physical location of contents of the replica of the file on the second file server; performing, by the processing device, a file system operation by accessing the replica of the file referenced by the index node number.

File replication using file content location identifiers

Delayed asynchronous file replication in a distributed file system is described. A first server receives requests to perform a updates to a first replica of a file. The first server sends, to a second server, an outcast instruction to set a second replica of the file to an out-of-date state. The first server performs the updates to the first replica without sending the updates to the second server. The first server receives a request for updates for the second replica from the second server. The first server transmits the updates to the second server to facilitate a heal operation of the second replica, where completion of the heal operation causes the out-of-date state of the second replica to be changed to an up-to-date state.

Delayed asynchronous file replication in a distributed file system

A method includes receiving, by a first computing device of a distributed file system from a second computing device, a first timestamp associated with a first version of a set of objects stored on the second computing device, the first timestamp corresponding to a modification time of the first version of the set of objects, or a first transfer time of the first version of the set of objects from at least one of the first computing device or a third computing device of the distributed file system to the second computing device. The method also includes identifying a second version of the set of objects stored on the first computing device, the second version of the set of objects having a second timestamp, the second timestamp corresponding to a modification time of the second version of the set of objects or a second transfer time. The method further includes transferring the second version of the set of objects to the second computing device to be stored on the second computing device.

Transferring objects between different storage devices based on timestamps

Systems and methods implementing a path resolver facilitating client access to a distributed file system. An example method may comprise: receiving, by a processing device, file identifier comprising a symbolic link; producing, by a user space process being executed by the processing device, a modified file identifier, by replacing a pre-defined sequence of characters within the file identifier by a path to a mount point of a distributed file system; and identifying, in view of the modified file identifier, a data structure comprising information about a file identified by the file identifier.

A request to perform an operation on an object in a first storage system may be received from a client computing device via a local area network or a wide area network. Mapping data that associates an account identifier from the request to perform the operation on the object in the first storage system to a volume of a file system of a second storage system may be received. The second storage system may be mounted to perform the operation using the file in the second storage system that corresponds to the object in the first storage system. The second storage system may be mounted by using the account identifier from the mapping data.

Unified file and object data storage

A distributed file system includes a plurality of computing devices that are coupled to a plurality of storage devices. A first computing device transfers objects to an additional computing device. The first computing device determines times when multiple computing devices, including the first computing device, transferred objects to the additional computing device. The first computing device identifies the earliest of the times and may store this information on the additional computing devices. A second computing device resumes transferring data to the additional computing device when the first computing device becomes unavailable or inoperable. The second computing device may use the earliest of the times to determine which objects should be transferred to the additional computing device.

A processing device receives a request for access to a source file that is stored in an initial location in a file system. The processing device determines that the source file is associated with a migration to a new location. The processing device reads the source file from the initial location if the request is a read request and writes to the source file at the initial location and writes to a destination file at the new location if the request is a write request.

Open file rebalance

An outcast index in a distributed file system is described. A first server can receive an indication that a first replica stored on the first server is to be modified in view of a second replica stored on a second server. The first replica and the second replica are replicas of a same file. The first server updates metadata associated with the first replica to indicate an outcast state of the first replica. The first server receives an indication that the modification of the first replica is complete. The first server updates the metadata associated with the first replica to remove the outcast state of the first replica.

Outcast index in a distributed file system

Systems and methods for compacting change logs using file content location identifiers. An example method may comprise: identifying a first change log record comprising an identifier of a first data structure referencing a first physical location of contents of a file before a first file system operation, the first change log record further comprising an identifier of a second data structure referencing a second physical location of the contents of the file after the file first system operation; identifying a second change log record comprising the identifier of the second data structure referencing the second physical location of the contents of the file before a second file system operation, the second change log record further comprising an identifier of a third data structure referencing a third physical location of the contents of the file after the second file system operation; and replacing the first change log record and the second change log record with a third change log record comprising the identifier of the first data structure and the identifier of the third data structure.

Compacting change logs using file content location identifiers

Systems and methods for file replication using file content location identifiers. An example method may comprise: receiving an identifier of a data structure associated with a file residing on a first file server, the data structure referencing a physical location of the contents of the file; identifying a file system operation to be performed with respect to a replica of the file residing on a second file server; and performing the file system operation by accessing the replica of the file using a file name alias comprising the identifier of the data structure.

A management process coordinates a number of servers to create a crash-consistent distributed snapshot. The management process instructs the servers to enter an ambiguity mode in which acknowledgement of barrier operations is delayed, instructs the servers to generate portion snapshots, and instructs the servers to exit the ambiguity mode and acknowledge barrier operations.

Growing community of inventors

Mountain View, CA, United States of America

Anand Vishweswaran Avati