Concurrent access and transactions in a distributed file system

• US 9,697,227 B2
• Filed: 10/27/2014
• Issued: 07/04/2017
• Est. Priority Date: 10/27/2014
• Status: Active Grant

• Current Assignee: Cohesity, Inc.
• Original Assignee: Cohesity, Inc.
• Inventors: Aron, Mohit, Shanmuganathan, Ganesha
• Primary Examiner(s): Ly, Anh
• Application Number:
  US14/524,979
• Publication Number:
  US 20160117336A1
• Time in Patent Office: 981 Days
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/1767 Concurrency control, e.g. optimistic or pessimistic approaches
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/1865 Transactional file systems

Abstract

Embodiments described herein provide techniques for maintaining consistency in a distributed system (e.g., a distributed secondary storage system). According to one embodiment of the present disclosure, a first set of file system objects included in performing the requested file system operation is identified in response to a request to perform a file system operation. An update intent corresponding to the requested file system operation is inserted into an inode associated with each identified file system object. Each file system object corresponding to the inode is modified as specified by the update intent in that inode. After modifying the file system object corresponding to the inode, the update intent is removed from that inode.

Claims

1. A method for performing a transaction in a distributed file system, the method comprising:

in response to a request to perform a file system operation, identifying a first set of file system objects modified in performing the requested file system operation, wherein each file system object has an associated inode;

upon determining that a first one of the inodes in the first set of file system objects stores an update intent from an incomplete file system operation;

identifying, in the update intent from the incomplete file system operation, a first ordered sequence of inodes, the first ordered sequence associated with the incomplete file system operation,

retrieving, as available, the inodes specified by the first ordered sequence, and

upon determining (i) that a first set of one or more inodes at the beginning of the first ordered sequence includes the update intent related to the incomplete file system operation and (ii) that a second set of one or more inodes following the first set of indoes does not include the update intent related to the incomplete file system operation, removing the update intent from each inode specified by the first ordered sequence that includes the update intent;

inserting an update intent corresponding to the requested file system operation into the inode associated with each identified file system object, wherein the inserted update intent specifies a second ordered sequence of inodes, the second ordered sequence being associated with the requested file system operation; and

for each inode in the second ordered sequence;

modifying either the inode or the file system object corresponding to the inode as specified by the update intent in that inode, and

after modifying the inode or the file system object corresponding to the inode, removing the update intent from that inode.

2. The method of claim 1, wherein completing the incomplete file system operation comprises:

upon determining that (i) the first set of one or more inodes at the beginning of the first ordered sequence does not include the update intent related to the incomplete file system operation and that (ii) the second set of one or more inodes following the first set of inodes each includes the update intent related to the incomplete file system operation, completing the file system as specified by the update intent in the second set of nodes according to the first ordered sequence.

3. The method of claim 2, further comprising, removing the update intent from each of the second set of inodes.

4. The method of claim 1, wherein the update intent specifies an identifier corresponding to the requested file system operation, the operation to be performed, and the second ordered sequence of the inodes modified in performing the requested operation.

5. The method of claim 1, further comprising, prior to inserting the update intent corresponding to the requested operation, obtaining a node-specific lock and a process-specific lock on each inode to be modified.

6. The method of claim 1, wherein the distributed file system is exposed to clients as a Network File System (NFS), Server Message Block (SMB), or Common Internet File System (CIFS) mount point, and wherein the requested file system operation is an NFS, SMB, or CIFS operation from a client sent to a node of the distributed file system.

7. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform an operation for performing a transaction in a distributed file system, the operation comprising:

in response to a request to perform a file system operation, identifying a first set of file system objects modified in performing the requested file system operation, wherein each file system object has an associated inode;

upon determining that a first one of the inodes in the first set of file system objects stores an update intent from an incomplete file system operation;

identifying, in the update intent from the incomplete file system operation, a first ordered sequence of inodes, the first ordered sequence associated with the incomplete file system operation,

retrieving, as available, the inodes specified by the first ordered sequence, and

upon determining (i) that a first set of one or more inodes at the beginning of the first ordered sequence includes the update intent related to the incomplete file system operation and (ii) that a second set of one or more inodes following the first set of inodes does not include the update intent related to the incomplete file system operation, removing the update intent from each inode specified by the first ordered sequence that includes the update intent;

inserting an update intent corresponding to the requested file system operation into the inode associated with each identified file system object, wherein the inserted update intent specifies a second an ordered sequence of inodes, the second ordered sequence being associated with the requested file system operation; and

for each inode in the second ordered sequence;

modifying either the inode or the file system object corresponding to the inode as specified by the update intent in that inode, and

after modifying the inode or the file system object corresponding to the inode, removing the update intent from that inode.

8. The computer-readable medium of claim 7, wherein the update intent specifies an identifier corresponding to the requested file system operation, the operation to be performed, and the ordered sequence of the inodes modified in performing the requested operation.

9. The computer-readable medium of claim 7, wherein the operation further comprises, prior to inserting the update intent corresponding to the requested operation, obtaining a node-specific lock and a process-specific lock on each inode to be modified.

10. The computer-readable medium of claim 7, wherein the distributed file system is exposed to clients as a Network File System (NFS), Server Message Block (SMB), or Common Internet File System (CIFS) mount point, and wherein the requested file system operation is an NFS, SMB, CIFS operation from a client sent to a node of the distributed file system.

11. A system comprising:

a processor; and

a memory storing program code, which, when executed on the processor performs an operation for performing a transaction in a distributed file system, the operation comprising;

in response to a request to perform a file system operation, identifying a first set of file system objects modified in performing the requested file system operation, wherein each file system object has an associated inode;

upon determining that a first one of the inodes in the first set of file system objects stores an update intent from an incomplete file system operation;

identifying, in the update intent from the incomplete file system operation, a first ordered sequence of inodes, the first ordered sequence associated with the incomplete file system operation;

retrieving, as available, the inodes specified by the first ordered sequence; and

upon determining (i) that a first set of one or more inodes at the beginning of the first ordered sequence includes the update intent related to the incomplete file system operation and (ii) that a second set of one or more inodes following the first set of inodes does not include the update intent related to the incomplete file system operation, removing the update intent from each inode specified by the first ordered sequence that includes the update intent,

inserting an update intent corresponding to the requested file system operation into the inode associated with each identified file system object, wherein the inserted update intent specifies a second ordered sequence of inodes, the second ordered sequence being associated with the requested file system operation, and

for each inode;

modifying either the inode or the file system object corresponding to the inode as specified by the update intent in that inode, and

after modifying the inode or the file system object corresponding to the inode, removing the update intent from that inode.

12. The system of claim 11, wherein completing the incomplete file system operation comprises:

upon determining that (i) the first set of one or more inodes at the beginning of the first ordered sequence does not include the update intent related to the incomplete file system operation and that (ii) the second set of one or more inodes following the first set of inodes each includes the update intent related to the incomplete file system operation, completing the file system as specified by the update intent in the second set of nodes according to the first ordered sequence.

13. The system of claim 12, wherein the operation further comprises, removing the update intent from each of the second set of inodes.

14. The system of claim 11, wherein the operation further comprises, prior to inserting the update intent corresponding to the requested operation, obtaining a node-specific lock and a process-specific lock on each inode to be modified.

15. The system of claim 11, wherein the distributed file system is exposed to clients as a Network File System (NFS), Server Message Block (SMB), or Common Internet File System (CIFS) mount point, and wherein the requested file system operation is an NFS, SMB, or CIFS operation from a client sent to a node of the distributed file system.