# US 2014/0372686 A1 · Methods and systems for marking data in a flash-based cache as invalid

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0372686 A1
- Document ID: US20140372686A1
- Status: Published application
- Kind: A1
- Application number: 14/473,992
- Filed: 2014-08-29
- Published: 2014-12-18
- Earliest claimed: 2010-07-14
- Assignees: Nimble Storage, Inc.
- Applicants: Nimble Storage, Inc.
- Inventors: Umesh Maheshwari; Varun Mehta
- Web page: https://patentgrep.com/patent/US20140372686A1

## CPC

- G06F 12/0888: using selective caching, e.g. bypass
- G06F 3/0616: {in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/0685: {Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays}
- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 12/0866: for peripheral storage systems, e.g. disk cache
- G06F 2212/1036: Life time enhancement
- G06F 2212/1044: Space efficiency improvement
- G06F 2212/222: Non-volatile memory
- G06F 2212/28: Using a specific disk cache architecture
- G06F 2212/466: Metadata, control data
- G06F 2212/60: Details of cache memory
- G06F 2212/604: Details relating to cache allocation
- G06F 2212/7202: Allocation control and policies
- G06F 2212/7205: Cleaning, compaction, garbage collection, erase control
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A storage device includes a flash memory-based cache for a hard disk-based storage device and a controller that is configured to limit the rate of cache updates through a variety of mechanisms, including determinations that the data is not likely to be read back from the storage device within a time period that justifies its storage in the cache, compressing data prior to its storage in the cache, precluding storage of sequentially-accessed data in the cache, and/or throttling storage of data to the cache within predetermined write periods and/or according to user instruction.

## Claims

### Claim 1

A method for a storage device having a flash-based cache, a non-volatile random access memory (NVRAM) and a disk-based storage unit, the method comprising:
storing, by a controller of the storage device, a first version of data at an address in the flash-based cache;
storing, by the controller, a second version of the data in the disk-based storage unit but not in the flash-based cache, the second version of the data being different than the first version of the data; and
in response to storing the second version of the data in the disk-based storage unit but not in the flash-based cache, storing, by the controller, the address of the first version of the data in an invalidate buffer instantiated on the NVRAM so as to mark the first version of the data in the flash-based cache as invalid.

### Claim 2 (depends on 1)

The method of claim 1, further comprising, in response to a failure of the invalidate buffer, purging all data from the flash-based cache so as to prevent the controller from serving stale data from the flash-based cache.

### Claim 3 (depends on 1)

The method of claim 1, further comprising, in response to the controller being unable to store further addresses in the invalidate buffer, invalidating data in the flash-based cache that has been marked as invalid in the NVRAM.

### Claim 4 (depends on 1)

The method of claim 1, wherein a maximum amount of information that can be stored in the NVRAM is less than a maximum amount of information that can be stored in the flash-based cache.

### Claim 5

A storage device, comprising a flash-based cache, a disk-based storage unit, a non-volatile random access memory (NVRAM) and a controller, the controller (i) communicatively coupled to the flash-based cache, the disk-based storage unit and the NVRAM; and (ii) configured to:
store a first version of data at an address in the flash-based cache;
store a second version of the data in the disk-based storage unit but not in the flash-based cache, the second version of the data being different than the first version of the data; and
in response to storing the second version of the data in the disk-based storage unit but not in the flash-based cache, store the address of the first version of the data in an invalidate buffer instantiated on the NVRAM so as to mark the first version of the data in the flash-based cache as invalid.

### Claim 6 (depends on 5)

The storage device of claim 5, wherein the controller is further configured to, in response to a failure of the invalidate buffer, purge all data from the flash-based cache so as to prevent the controller from serving stale data from the flash-based cache.

### Claim 7 (depends on 5)

The storage device of claim 5, wherein the controller is further configured to, in response to the controller being unable to store further addresses in the invalidate buffer, invalidate data in the flash-based cache that has been marked as invalid in the NVRAM.

### Claim 8 (depends on 5)

The storage device of claim 5, wherein a maximum amount of information that can be stored in the NVRAM is less than a maximum amount of information that can be stored in the flash-based cache.

### Claim 9

A non-transitory computer-readable storage medium comprising software instructions that, when executed by a controller of a storage device, cause the controller to:
store a first version of data at an address in a flash-based cache of the storage device;
store a second version of the data in a disk-based storage unit of the storage device but not in the flash-based cache, the second version of the data being different than the first version of the data; and
in response to storing the second version of the data in the disk-based storage unit but not in the flash-based cache, store the address of the first version of the data in an invalidate buffer instantiated on a non-volatile random access memory (NVRAM) of the storage device so as to mark the first version of the data in the flash-based cache as invalid.

### Claim 10 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, further comprising software instructions that, when executed by the controller, cause the controller to, in response to a failure of the invalidate buffer, purge all data from the flash-based cache so as to prevent the controller from serving stale data from the flash-based cache.

### Claim 11 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, further comprising software instructions that, when executed by the controller, cause the controller to, in response to the controller being unable to store further addresses in the invalidate buffer, invalidate data in the flash-based cache that has been marked as invalid in the NVRAM.

### Claim 12 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein a maximum amount of information that can be stored in the NVRAM is less than a maximum amount of information that can be stored in the flash-based cache.
