System and method for maintaining cache coherency

• US 9,313,271 B2
• Filed: 05/05/2015
• Issued: 04/12/2016
• Est. Priority Date: 08/06/2012
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Venkat, Narayan, Lively, David, Speer, Kenny
• Primary Examiner(s): Rutz, Jared
• Assistant Examiner(s): Ahmed, Hamdy S
• Application Number:
  US14/704,059
• Publication Number:
  US 20150237135A1
• Time in Patent Office: 343 Days
• Field of Search: 711/133
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0808 with cache invalidating means G06F12/0815 takes precedence
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 12/0877 Cache access modes
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0683 Plurality of storage devices
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Described herein is a system and method for maintaining cache coherency. The system and method may maintain coherency for a cache memory that is coupled to a plurality of primary storage devices. The system and method may write data to the cache memory and associate the data with a cache generation identification (ID). A different cache generation ID may be associated with each new set of data that is written to the cache memory. The cache generation ID may be written to the primary storage devices. A backup restore operation may be performed on one of the primary storage devices and a backup restore notification may be received. In response to the notification, the system and method may compare the cache generation ID with the generation ID stored on the restored primary storage device and invalidate data stored on the cache memory for the restored primary storage device.

Claims

1. A system comprising:

a processor;

a cache memory coupled to the processor and configured to store cache data, the cache memory assigned a current generation identifier (ID) associated with a last time the cache data was written to the cache memory, and

a memory coupled to the processor and configured to store one or more processes, the one or more processes when executed by the processor operable to;

receive a notification that a device generation ID stored on a primary storage device coupled to the cache memory is less than the current generation ID of the cache memory, wherein the device generation ID is associated with a restored backup of the primary storage device, and

based on receiving the notification;

(1) mark first cache data, of the cache data stored in the cache memory, as invalid based on the first cache data associated with a different generation ID that is greater than the device generation ID stored on is the primary storage device, (2) receive a first data access request for the first cache data from a client, and (3) prevent transmitting the first cache data from the cache memory to the client based on marking the first cache data as invalid.

2. The system of claim 1, wherein the current generation ID of the cache memory corresponds to a latest generation ID assigned to the cache memory.

3. The system of claim 1, wherein the current generation ID assigned to the cache memory is incremented each time the cache data is written to the cache memory.

4. The system of claim 1, wherein the device generation ID is stored on a data block of a partition of the primary storage device.

5. The system of claim 1, wherein the one or more processes are further operable to maintain a cache generation ID data structure that stores an association between (1) the first cache data and the different generation ID and (2) second cache data of the cache data and a third generation ID.

6. The system of claim 5, wherein the second cache data is marked as valid based on the third generation ID being less than or equal to the device generation ID stored on the primary storage device.

7. The system of claim 1, wherein the first cache data is marked as invalid by modifying a header associated with the first cache data.

8. The system of claim 6, wherein the one or more processes are further configured to:

receive a second data access request for the second cache data from the client, and

transmit the second cache data to the client based on marking the second cache data as valid.

9. A method comprising:

receiving a notification that a device generation identifier (ID) stored on a primary storage device coupled to a cache memory of a storage system is less than a current generation ID of the cache memory, wherein the current generation ID is associated with a last time cache data was written to the cache memory and wherein the device generation ID is associated with a restored backup of the primary storage device; and

based on receiving the notification;

(1) marking, by a processor of the storage system, first cache data of the cache data as invalid based on the first cache data being associated with a different generation ID that is greater than the device generation ID stored on the primary storage device,

(2) receiving a first data access request for the first cache data from a client, and

(3) preventing transmission of the first cache data from the cache memory to the client based on marking the first cache data as invalid.

10. The method of claim 9, wherein the current generation ID of the cache memory corresponds to a latest generation ID assigned to the cache memory.

11. The method of claim 9, wherein the current generation ID assigned to the cache memory is incremented each time the cache data is written to the cache memory.

12. The method of claim 9, wherein the device generation ID is stored on a data block of a partition of the primary storage device.

13. The method of claim 9, further comprising maintaining a cache generation ID data structure that stores an association between (1) the first cache data and the different generation ID and (2) second cache data of the cache data and a third generation ID.

14. The method of claim 13, further comprising marking the second cache data as valid based on the third generation ID being less than or equal to the device generation ID stored on the primary storage device.

15. The method of claim 9, wherein the first cache data is marked as invalid by modifying a header associated with the first cache data.

16. The method of claim 14, further comprising:

receiving a second data access request for the second cache data from the client, and

transmitting the second cache data to the client based on marking the second cache data as valid.

17. A non-transitory computer readable storage medium containing executable program instructions configured for execution by a processor and further configured for storage on the non-transitory computer readable storage medium, the computer readable storage medium comprising:

program instructions that receive a notification that a device generation identifier (ID) stored on a primary storage device coupled to a cache memory of a storage system is less than a current generation ID of the cache memory, wherein the current generation ID is associated with a last time cache data was written to the cache memory and wherein the device generation ID is associated with a restored backup of the primary storage device; and

based on receiving the notification, program instructions that;

(1) mark first cache data of the cache data as invalid based on the first cache data being associated with a different generation ID that is greater than the device generation ID stored on the primary storage device, (2) receive a first data access request for the first cache data from a client, and (3) prevent transmission of the first cache data from the cache memory to the client based on marking the first cache data as invalid.

18. The non-transitory computer readable storage medium of claim 17, wherein the current generation ID of the cache memory corresponds to a latest generation ID assigned to the cache memory.

19. The non-transitory computer readable storage medium of claim 17, wherein the current generation ID assigned to the cache memory is incremented each time the cache data is written to the cache memory.

20. The non-transitory computer readable storage medium of claim 17, wherein the device generation ID is stored on a data block of a partition of the primary storage device.