Concurrent access and transactions in a distributed file system

Patent metadata

Field	Value
Publication number	US-12505074-B2
Application number	US-202318197503-A
Country	US
Kind code	B2
Filing date	May 15, 2023
Priority date	Oct 27, 2014
Publication date	Dec 23, 2025
Grant date	Dec 23, 2025

Abstract

An inode is associated with an incomplete file system operation to a file system object is determined based on an update intent stored in the inode. It is determined that a set of inodes is associated with the incomplete file system operation based on the update intent stored in the inode. The update intent indicates the set of inodes is associated with the incomplete file system operation. It is determined to complete the incomplete file system operation based on evaluating the set of inodes that is associated with the incomplete file system operation. Evaluating the set of inodes that is associated with the incomplete file system operation includes determining whether the set of inodes that is associated with the incomplete file system operation stores a corresponding update intent. The incomplete file system operation is completed based on the evaluation of the set of inodes that is associated with the incomplete file system operation.

First claim

What is claimed is:

1 . A method, comprising:
determining, by processing circuitry of a data platform that manages a distributed file system concurrently accessed by multiple client devices, and based on an update intent stored in an inode, that the inode is associated with an incomplete file system operation to a file system object provided by the distributed file system, wherein the inode includes a data structure that describes the file system object; determining, by the processing circuitry, that a set of inodes is associated with the incomplete file system operation based on the update intent stored in the inode, wherein the update intent specifies an update identifier associated with the incomplete file system operation, an intended action that specifies a type of the incomplete file system operation, and an entity list that indicates that the set of inodes is associated with the incomplete file system operation associated with the update identifier; determining, by the processing circuitry, to complete the incomplete file system operation based on determining whether each inode of the set of inodes that is associated with the incomplete file system operation stores a corresponding update intent specifying the same update identifier; obtaining, by the processing circuitry and after determining to complete the incomplete file system operation, a lock for the file system object provided by the distributed file system; completing, by the processing circuitry, the incomplete file system operation; and removing, by the processing circuitry, after completing the incomplete file system operation, the lock for the file system object provided by the distributed file system and, for each inode of the set of inodes that is associated with the incomplete file system operation, the corresponding update intent.

2 . The method of claim 1 , wherein the file system object is a file.

3 . The method of claim 1 , wherein the file system object is a directory.

4 . The method of claim 1 , wherein the type of the incomplete file system operation is a copy operation, a rename operation, a delete operation, a create operation, or a write operation.

5 . The method of claim 1 , wherein the entity list identifies the set of inodes that is associated with the incomplete file system operation.

6 . The method of claim 1 , wherein the update intent indicates an order in which an intended action is to be performed.

7 . The method of claim 1 , further comprising aborting the incomplete file system operation in response to determining that at least a last inode of the set of inodes that is associated with the incomplete file system operation does not store the corresponding update intent.

8 . The method of claim 1 , wherein completing the incomplete file system operation comprises completing, in response to determining that at least a first inode of the set of inodes that is associated with the incomplete file system operation does not store the corresponding update intent and at least a last inode of the set of inodes that is associated with the incomplete file system operation stores the corresponding update intent, the incomplete file system operation.

9 . A computer program product, the computer program product including non-transitory computer readable storage media storing instructions that, when executed, cause processing circuitry of a data platform that manages a distributed file system concurrently accessed by multiple client devices to:
determine, based on an update intent stored in an inode, that the inode is associated with an incomplete file system operation to a file system object provided by the distributed file system, wherein the inode includes a data structure that describes the file system object; determine that a set of inodes is associated with the incomplete file system operation based on the update intent stored in the inode, wherein the update intent specifies an update identifier associated with the incomplete file system operation, an intended action that specifies a type of the incomplete file system operation, and an entity list that indicates that the set of inodes is associated with the incomplete file system operation associated with the update identifier; determine to complete the incomplete file system operation based on determining whether each inode of the set of inodes that is associated with the incomplete file system operation stores a corresponding update intent specifying the same update identifier; obtain, after determining to complete the incomplete file system operation, a lock for the file system object provided by the distributed file system; complete the incomplete file system operation based on whether the set of inodes that is associated with the incomplete file system operation stores the corresponding update intent; and remove, after completing the incomplete file system operation, the lock for the file system object provided by the distributed file system and, for the inode and, for each inode of the set of inodes that is associated with the incomplete file system operation, the corresponding update intent.

10 . The computer program product of claim 9 , wherein the incomplete file system operation is not completed in response to determining that at least a last inode of the set of inodes that is associated with the incomplete file system operation does not store the corresponding update intent.

11 . The computer program product of claim 9 , wherein the instructions that, when executed, cause the processing circuitry to complete the incomplete file system operation comprise instructions that, when executed, cause the processing circuitry to complete the incomplete file system operation in response to determining that the set of inodes that is associated with the incomplete file system operation stores the corresponding update intent specifying the same update identifier.

12 . The computer program product of claim 9 , wherein the instructions that, when executed, cause the processing circuitry to complete the incomplete file system operation comprises instruction that, when executed, cause the processing circuitry to complete the incomplete file system operation in response to determining that at least a first inode of the set of inodes that is associated with the incomplete file system operation does not store the corresponding update intent and at least a last inode of the set of inodes that is associated with the incomplete file system operation stores the corresponding update intent.

13 . A data platform configured to manage a distributed file system concurrently accessed by multiple client devices, the data platform comprising:
a memory configured to store instructions; and a processor coupled to the memory and configured to execute the instructions to:
determine, based on an update intent stored to an inode, the inode is associated with an incomplete file system operation to a file system object provided by the distributed file system, wherein the inode includes a data structure that describes the file system object;
determine that a set of inodes is associated with the incomplete file system operation based on the update intent stored in the inode, wherein the update intent specifies an update identifier associated with the incomplete file system operation, an intended action that specifies a type of the incomplete file system operation, and an entity list that indicates that the set of inodes is associated with the incomplete file system operation associated with the update identifier;
determine to complete the incomplete file system operation based on determining whether each inode of the set of inode

Assignees

• Cohesity Inc

Inventors

• Aron Mohit
• Shanmuganathan Ganesha

Classifications

• G06F16/9024

  Graphs; Linked lists (G06F16/9027 takes precedence) · CPC title

• G06F16/1767 Primary

  Concurrency control, e.g. optimistic or pessimistic approaches · CPC title