NVRAM Logging for Shingled Magnetic Recording Drive Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Shingled magnetic recording (SMR) drives require sequential writes for data zones, leading to inefficiencies and increased latency due to the need to rewrite entire zones for non-sequential file system changes, and existing solutions lack efficient mechanisms for maintaining file system data structures and ensuring data consistency and recoverability.

Innovation Solution

The use of non-volatile random access memory (NVRAM) for logging file system changes and maintaining file system data structures, with atomic updates and checkpoint mechanisms to ensure data consistency and facilitate recovery, allowing for efficient and safe updates and storage of file system changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequential writes are used for SMR drive data zones, then data consistency is maintained, but write latency increases and productivity decreases

Engineering Contradiction:
Improvedata consistencyVSAvoidwrite speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the write operation into two independent parts: (1) logging file system changes sequentially in NVRAM, and (2) asynchronously transferring selected log entries to the SMR drive. This segmentation allows the file system to accept writes without waiting for SMR sequential writes, improving productivity while maintaining consistency through the log structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces NVRAM as an intermediary between the file system and the SMR drive. The NVRAM log structure acts as a mediator that buffers write operations, allowing the file system to operate independently while ensuring data consistency is maintained through the sequential log writing mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If entire zones are rewritten for non-sequential changes, then data consistency is ensured, but time consumption and latency increase

Engineering Contradiction:
Improvedata consistencyVSAvoidwrite latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by logging all file system changes sequentially in NVRAM before they are transferred to the SMR drive. This preliminary logging ensures that when data is eventually written to the SMR drive, consistency is already established, eliminating the need for time-consuming zone rewrites later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent discards the traditional approach of rewriting entire zones and instead recovers efficiency by selectively transferring only the necessary log entries from NVRAM to the SMR drive based on change detection, reducing time consumption while maintaining consistency.

Inventive Principle:
Principle #34Discarding and recovering

3Productivity

If NVRAM is used for logging file system changes, then update speed improves, but device complexity increases

Engineering Contradiction:
Improveupdate speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent makes the NVRAM log structure serve multiple functions: (1) buffering file system changes, (2) maintaining data consistency through sequential logging, (3) enabling fast updates via NVRAM speed, and (4) facilitating recovery through the persistent log structure. This multi-functionality justifies the added complexity by delivering comprehensive benefits.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent changes the storage medium parameter from traditional volatile RAM or direct SMR writing to non-volatile RAM with persistent logging capabilities. This parameter change enables both fast updates (through NVRAM speed) and data persistence (through non-volatility), improving productivity while the complexity is managed through the unified log structure.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If checkpoint mechanisms are implemented, then recoverability is improved, but device complexity and processing overhead increase

Engineering Contradiction:
ImproverecoverabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements checkpoint mechanisms that periodically mark points in the log structure where consistency is guaranteed. These preliminary checkpoint markers enable recovery operations to quickly identify valid log entries without complex analysis, improving recoverability while managing complexity through structured marking.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The checkpoint mechanism provides feedback to the system about the state of the log structure, enabling recovery processes to efficiently determine which log entries need to be applied. This feedback loop improves recoverability while the structured nature of checkpoint marking keeps the complexity manageable.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11150847B2Shingled magnetic recording drive mapping using nonvolatile random access memory for persistent updates
Publication Date: 2021.10.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11150847B2 patent drawing
  • US11150847B2 patent drawing
  • US11150847B2 patent drawing

AI summary

A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.