Write-back storage cache based on fast persistent memory

• US 10,592,416 B2
• Filed: 11/03/2011
• Issued: 03/17/2020
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Baddepudi, Bharat Chandra, Loaiza, Juan R., Hu, Wei-Ming, Umamageswaran, Kothanda, Tsukerman, Alex, Erlikhman, Boris, Lee, J. William, Shi, Jia, Goyal, Kiran B., Aya, Selcuk
• Primary Examiner(s): Sain, Gautam
• Application Number:
  US13/288,785
• Publication Number:
  US 20130086330A1
• Time in Patent Office: 3,057 Days
• Field of Search: 711143
• CPC Class Codes: G06F 12/08 in hierarchically structured memory systems, e.g. virtual memory systems
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 2212/502 using adaptive policy

Abstract

A storage device uses non-volatile memory devices for caching. The storage device operates in a mode referred to herein as write-back mode. In write-back mode, a storage device responds to a request to write data by persistently writing the data to a cache in a non-volatile memory device and acknowledges to the requestor that the data is written persistently in the storage device. The acknowledgement is sent without necessarily having written the data that was requested to be written to primary storage. Instead, the data is written to primary storage later.

Claims

1. A method, comprising steps of:

a storage device receiving from a storage device client a data block write request to write a data block to said storage device;

wherein said storage device comprises one or more primary storage devices and one or more flash cache devices comprising non-volatile memory;

selecting a victim cache copy stored in said one or more flash cache devices to which to replace with said data block;

wherein-persistent cache metadata stored in said one or more flash cache devices;

maps a cache block address of said victim to a primary block address of the data block of which said victim is a cache copy;

contains a dirty flag that specifies that said victim is clean;

associates with said victim a block check value;

overwriting said victim in said flash cache device with contents of said data block;

encountering a storage device failure before updating said persistent cache metadata to reflect said overwriting of said victim; and

said storage device performing recovery, wherein performing recovery includes;

generating a block check value based on content of the data block stored in place of said victim,

making a comparison between (1) the block check value generated based on content of the data block stored in place of said victim and (2) the block check value associated with said victim by said persistent cache metadata, and

based on the comparison, detecting that the persistent cache metadata contains a false dirty flag that specifies that the data block stored in place of said victim is clean.

2. The method of claim 1, further including:

before said storage device receiving from said storage device client said data block write request;

storing, to a flash cache device of said one or more flash cache devices, a particular data block as a cache copy of a version of said particular data block stored in said one or more primary storage devices, said victim cache copy being said cache copy version of said particular data block;

generating said block check value associated with said victim cache copy;

updating persistent cache metadata stored in said one or more flash cache devices to map said cache copy of said particular data block and to store, in association with said said cache copy of said particular data block, said block check value associated with said victim cache copy.

3. One or more non-transitory storage media storing sequences of instructions, wherein said sequences of instructions, when executed by one or more processors, cause:

a storage device receiving from a storage device client a data block write request to write a data block to said storage device;

wherein said storage device comprises one or more primary storage devices and one or more flash cache devices comprising non-volatile memory;

selecting a victim cache copy stored in said one or more flash cache devices to which to replace with said data block;

wherein-persistent cache metadata stored in said one or more flash cache devices;

maps a cache block address of said victim to a primary block address of the data block of which said victim is a cache copy;

contains a dirty flag that specifies that said victim is clean;

associates with said victim a block check value;

overwriting said victim in said flash cache device with contents of said data block;

encountering a storage device failure before updating said persistent cache metadata to reflect said overwriting of said victim; and

said storage device performing recovery, wherein performing recovery includes;

generating a block check value based on content of the data block stored in place of said victim,

making a comparison between (1) the block check value generated based on content of the data block stored in place of said victim and (2) the block check value associated with said victim by said persistent cache metadata, and

based on the comparison, detecting that the persistent cache metadata contains a false dirty flag that specifies that the data block stored in place of said victim is clean.

4. The one or more non-transitory storage media of claim 3, the sequences of instructions further including instructions that, when executed by said one or more processors, cause:

before said storage device receiving from said storage device client said data block write request;

storing, to a flash cache device of said one or more flash cache devices, a particular data block as a cache copy of a version of said particular data block stored in said one or more primary storage devices, said victim cache copy being said cache copy version of said particular data block;

generating said block check value associated with said victim cache copy;

updating persistent cache metadata stored in said one or more flash cache devices to map said cache copy of said particular data block and to store, in association with said said cache copy of said particular data block, said block check value associated with said victim cache copy.