Storage Metadata Synchronization During Block Reclamation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern storage systems face challenges in efficiently reclaiming storage blocks while writing new data, as new data can potentially replace relocated data during the reclaiming process, making it difficult to ensure that applications receive the correct file portions and complicating data storage.

Innovation Solution

A computing system is configured with a reclamation module and an invalidity module to select and relocate valid data, and a groomer module to perform grooming operations by identifying data to copy to a different append point within the storage log, while tracking storage operations to invalidate data that has become invalid due to new data being written.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If storage blocks are reclaimed by relocating data during the reclaiming process, then storage efficiency is improved, but data integrity may be compromised when new data replaces relocated data

Engineering Contradiction:
Improvestorage reclamation efficiencyVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by marking data as invalid in the metadata structure before the actual relocation completes, and uses preliminary validation checks to ensure that only valid data is relocated. This prevents new data from overwriting invalid or partially relocated data, thus maintaining data integrity while enabling efficient reclamation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms through metadata structures that track the validity status of data blocks. The reclamation process continuously checks metadata to determine which data is valid and should be relocated, and updates metadata in real-time to reflect the current state of data validity, ensuring that reclamation operations do not compromise data integrity.

Inventive Principle:
Principle #23Feedback

2Reliability

If metadata is updated continuously to track data validity during reclamation, then data integrity is maintained, but system complexity increases

Engineering Contradiction:
Improvedata validity trackingVSAvoidmetadata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The metadata structure is segmented into distinct components that track different aspects of data validity independently. This segmentation allows the system to manage complexity by organizing metadata into manageable units that can be updated and processed separately, reducing the overall system complexity while maintaining comprehensive validity tracking.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary metadata layer that acts as a mediator between the reclamation process and the actual data storage. This metadata intermediary simplifies complexity by providing a standardized interface for tracking data validity, allowing the reclamation process to operate efficiently without directly managing the complex details of data integrity verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If data is relocated to internal append points during garbage collecting, then storage log utilization is improved, but ensuring data correctness becomes more difficult

Engineering Contradiction:
Improvestorage log utilizationVSAvoiddata correctness verification
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

Before relocating data to internal append points, the system performs preliminary validation by checking the metadata to confirm the data is valid and should be relocated. This preliminary action ensures that only correct data is moved, and the metadata updates provide a verification trail that simplifies detecting and measuring data correctness after relocation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses copying mechanisms where metadata entries are copied and updated to reflect the new locations of relocated data. This copying approach maintains a verified record of data correctness at the new append points, making it easier to detect and measure data correctness without compromising storage log utilization efficiency.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10114576B2Storage device metadata synchronization
Publication Date: 2018.10.30 SANDISK TECHNOLOGIES LLC
  • US10114576B2 patent drawing
  • US10114576B2 patent drawing
  • US10114576B2 patent drawing

AI summary

Embodiments are disclosed relating to garbage collecting storage blocks in a storage device. In one embodiment, data is selected for relocation from a storage block in a storage device during reclaiming of the storage block. The data may be selected based on metadata that identifies whether data is valid at a time when the reclaiming is initiated. In some embodiments, prior to relocating data from the storage block, the metadata is captured from a data structure that identifies whether data on the storage device is valid. In one embodiment, a determination of whether the selected data has become invalid due to other data that is stored during the reclaiming is made. In some embodiments, in response to determining that the selected data has become invalid, the selected data is specified as invalid in the data structure.