Concurrent checkpointing and modifications in a transactional clustered file system

• US 8,516,021 B2
• Filed: 08/06/2012
• Issued: 08/20/2013
• Est. Priority Date: 08/25/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Aronovich, Lior, Toaff, Yair, Paz, Gil, Asher, Ron
• Primary Examiner(s): Casanova, Jorge A
• Application Number:
  US13/567,236
• Publication Number:
  US 20120303579A1
• Time in Patent Office: 379 Days
• Field of Search: 707/786, 707/826
• US Class Current: 707/826
• CPC Class Codes: G06F 12/0802 Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 12/0828 with concurrent directory accessing, i.e. handling multiple concurrent coherency transactions
• CPC Class Codes: G06F 12/084 with a shared cache
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/16 File or folder operations, e.g. details of user interfaces specifically adapted to file systems
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 16/1865 Transactional file systems
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2212/604 Details relating to cache allocation

Abstract

Systems, Methods, and Computer Program Products are provided for concurrent checkpointing and modifications in a transactional clustered file system (CFS). Shadow data segments, whose contents are identical to an original data segment currently being written by a checkpoint operation, for users that require access for modification to data segments concurrently being written within a checkpoint operation.

Claims

1. A method for concurrent checkpointing and modifications in a transactional clustered file system (CFS) using a processor device, the method comprising:

providing a shadow data segment, whose contents are identical to an original data segment currently being written by a checkpoint operation, for users that require access for modification to data segments concurrently being written within a checkpoint operation;

including a transaction journal in each node for storing committed transactions generated by users on that node;

scanning a list to identify the location of the latest contents of a data segment prior to the transaction using a rollback procedure;

for each modified data segment, identifying the location of the latest contents prior to the transaction using the rollback procedure by;

if the data segment was marked as modified in the cache at the time it was inserted into the list, then the latest contents of this data segment appears only in the journal,

otherwise, if the data segment was not marked as modified in the cache at the time the data segment was inserted into the list, then the latest contents of this data segment appears in its final location in the shared storage; and

recording a type of each data segment in the list during insertion of the data segment into the list, wherein;

all data segments in the list whose latest contents appear in a final location are discarded from the cache,

for all the other data segments in the list, latest contents for the all the other data segments are restored from the journal into the cache by scanning the local transaction journal from ending to beginning, and first occurrences of these data segments in the local transaction journals are considered, and a modification indication of the data segments is set as true, and

exclusive permissions on all the data segments involved in a cancellation transaction are released.

2. The method of claim 1, wherein the checkpoint operation is asynchronous.

3. The method of claim 1, further including, upon completion of the checkpoint operation, disassociating the original data segment stored in a cache from the original data segment written to a storage device during the checkpoint operation.

4. The method of claim 3, further including, upon completion of the checkpoint operation, replacing the original data segment in a cache with the shadow data segment to become a sole representation of the original data segment that participated in the checkpoint operation.

5. The method of claim 1, wherein the checkpoint operation marks all modified data segments in a cache as being written to a final storage location and generates associated write operations to an input/output subsystem for a background execution.

6. The method of claim 5, further including, upon completion of a write operation, clearing the mark of associated cache data segments.

7. The method of claim 6, further including unblocking users that are blocked on accessing the data segments whose writing to an input/output subsystem has been completed.

8. The method of claim 1, further including creating the shadow data segment in a cache for the data segments dispatched for the checkpoint operation.

9. A system concurrent checkpointing and modifications in a transactional clustered file system (CFS), the system comprising:

a cluster of nodes,

the transactional CFS including the cluster of nodes forming a computer cluster,

a distributed shared memory (DSM) agent within a node of the cluster of nodes;

a plurality of storage devices in communication with the transactional CFS,

a cache associated with the node,

a transaction journal associated with the transactional CFS, and

a processor device having a memory coupled to the processor device for controlling the transactional CFS, wherein the processor device is assigned to the node and the node is in communication with the plurality of storage devices, wherein the processor device;

provides a shadow data segment, whose contents are identical to an original data segment currently being written by a checkpoint operation, for users that require access for modification to data segments concurrently being written within a checkpoint operation,

includes the transaction journal in each node for storing committed transactions generated by users on that node,

includes a list to identify the location of the latest contents of a data segment prior to the transaction using a rollback procedure,

for each modified data segment, identifies the location of the latest contents prior to the transaction using the rollback procedure by;

if the data segment was marked as modified in the cache at the time it was inserted into the list, then the latest contents of this data segment appears only in the journal,

otherwise, if the data segment was not marked as modified in the cache at the time the data segment was inserted into the list, then the latest contents of this data segment appears in its final location in the shared storage, and

records a type of each data segment in the list during insertion of the data segment into the list, wherein;

all data segments in the list whose latest contents appear in a final location are discarded from the cache,

for all the other data segments in the list, latest contents for the all the other data segments are restored from the journal into the cache by scanning the local transaction journal from ending to beginning, and first occurrences of these data segments in the local transaction journal are considered, and a modification indication of the data segments is set as true, and

exclusive permissions on all the data segments involved in a cancellation transaction are released.

10. The system of claim 9, wherein the checkpoint operation is asynchronous.

11. The system of claim 9, wherein the processor device, upon completion of the checkpoint operation, disassociates the original data segment stored in a cache from the original data segment written to a storage device during the checkpoint operation.

12. The system of claim 11, wherein the processor device, upon completion of the checkpoint operation, replaces the original data segment in a cache with the shadow data segment to become a sole representation of the original data segment that participated in the checkpoint operation.

13. The system of claim 9, wherein the checkpoint operation marks all modified data segments in a cache as being written to a final storage location and generates associated write operations to an input/output subsystem for a background execution.

14. The system of claim 13, wherein the processor device, upon completion of a write operation, clears the mark of associated cache data segments.

15. The system of claim 14, wherein the processor device unblocks users that are blocked on accessing the data segments whose writing to an input/output subsystem has been completed.

16. The system of claim 9, wherein the processor device creates the shadow data segment in a cache for the data segments dispatched for the checkpoint operation.

17. A computer program product for performing concurrent transactional checkpoints from a plurality of file system agents residing on different nodes within in a clustered file system (CFS) using a processor device, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion that provides a shadow data segment, whose contents are identical to an original data segment currently being written by a checkpoint operation, for users that require access for modification to data segments concurrently being written within a checkpoint operation,

a second executable portion that includes a transaction journal in each node for storing committed transactions generated by users on that node;

a third executable portion that includes a list to identify the location of the latest contents of a data segment prior to the transaction using a rollback procedure;

for each modified data segment, a fourth executable portion that identifies the location of the latest contents prior to the transaction using the rollback procedure by;

if the data segment was marked as modified in the cache at the time it was inserted into the list, then the latest contents of the data segment appears only in the journal,

otherwise, if the data segment was not marked as modified in the cache at the time the data segment was inserted into the list, then the latest contents of this data segment appears in its final location in the shared storage; and

a fifth executable portion that records a type of each data segment in the list during insertion of the data segment into the list, where;

all data segments in the list whose latest contents appear in a final location are discarded from the cache,

for all the other data segments in the list, latest contents for the all the other data segments are restored from the journal into the cache by scanning the local transaction journal from ending to beginning, and first occurrences of these data segments in the local transaction journal are considered, and a modification indication of the data segments is set as true, and

exclusive permissions on all the data segments involved in a cancellation transaction are released.

18. The computer program product of claim 17, wherein the checkpoint operation is asynchronous.

19. The computer program product of claim 17, further including a sixth executable portion that, upon completion of the checkpoint operation, disassociates the original data segment stored in a cache from the original data segment written to a storage device during the checkpoint operation.

20. The computer program product of claim 19, further including a seventh executable portion that, upon completion of the checkpoint operation, replaces the original data segment in a cache with the shadow data segment to become a sole representation of the original data segment that participated in the checkpoint operation.

21. The computer program product of claim 17, wherein the checkpoint operation marks all modified data segments in a cache as being written to a final storage location and generates associated write operations to an input/output subsystem for a background execution.

22. The computer program product of claim 21, further including a sixth executable portion that, upon completion of a write operation, clears the mark of associated cache data segments.

23. The computer program product of claim 22, further including a seventh executable portion that unblocks users that are blocked on accessing the data segments whose writing to an input/output subsystem has been completed.

24. The computer program product of claim 17, further including a sixth executable portion that creates the shadow data segment in a cache for the data segments dispatched for the checkpoint operation.