Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Systems and methods for compacting change logs using file content location identifiers.

Abstract: 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.

Abstract: 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.

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

Abstract: Systems and methods for write-behind caching in distributed file systems. An example method may comprise: receiving, over a network, a direct write request referencing data to be written to a file residing on a persistent data storage device, the file containing at least part of an image of a virtual machine disk; writing, by a processing device, the data to a cache entry of a memory-resident cache, the cache entry corresponding to at least a part of the file; acknowledging the write request as completed; and committing, asynchronously with respect to the acknowledging, the cache entry to the persistent data storage device.

Abstract: Data connections from a remote login session are identified and an identification query may be transmitted by the remote login session to endpoints (e.g., servers) of the data connections. In response to the identification query, identification information may be received from the endpoints. Furthermore, the identification information may be compared with a local identification of a local server that hosts the remote login session. A file created by the remote login session may be stored at an endpoint over a data connection where the local identification matches a portion or all of the identification information of the endpoint of the data connection.

Abstract: 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.

Abstract: Systems and methods for compacting change logs using file content location identifiers.

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

Abstract: Data connections from a remote login session are identified and an identification query may be transmitted by the remote login session to endpoints (e.g., servers) of the data connections. In response to the identification query, identification information may be received from the endpoints. Furthermore, the identification information may be compared with a local identification of a local server that hosts the remote login session. A file created by the remote login session may be stored at an endpoint over a data connection where the local identification matches a portion or all of the identification information of the endpoint of the data connection.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Systems and methods for write-behind caching in distributed file systems. An example method may comprise: receiving, over a network, a direct write request referencing data to be written to a file residing on a persistent data storage device, the file containing at least part of an image of a virtual machine disk; writing, by a processing device, the data to a cache entry of a memory-resident cache, the cache entry corresponding to at least a part of the file; acknowledging the write request as completed; and committing, asynchronously with respect to the acknowledging, the cache entry to the persistent data storage device.