Checksum-Based Data Object Handle Integrity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In clustered storage systems, corrupted or dangling data object handles can lead to incorrect data access due to inconsistencies, where data object handles may point to erroneous or deleted data objects, causing file system failures.

Innovation Solution

A checksum is generated for each data object handle upon creation and stored with it, allowing for later comparison to detect corruption or dangling issues. The system scans logical data containers to correct corrupted handles by updating the redirector file and deletes entries for dangling handles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data object handles are used to reference data objects in a clustered storage system, then data access efficiency is improved, but data integrity deteriorates due to corruption and dangling handles

Engineering Contradiction:
Improvedata access efficiencyVSAvoiddata integrity
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies preliminary action by generating and storing a checksum of the data object handle at the time of data object creation. This preemptive measure allows the system to detect corruption or dangling handles before they cause access failures, thereby maintaining both fast data access through handle usage and high data integrity through预先 stored verification data.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If checksum verification is performed on data object handles, then data integrity is improved, but system complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by introducing a checksum parameter that is stored alongside the data object handle. This additional parameter enables verification of handle integrity without fundamentally changing the data access mechanism. The checksum is computed and compared as a simple parameter verification step, maintaining system simplicity while significantly improving data integrity.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the system scans logical data containers to correct corrupted handles, then data integrity is improved, but processing time increases

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies self-service by implementing an automatic correction mechanism that scans logical data containers and repairs corrupted or dangling data object handles without requiring manual intervention. The system autonomously detects issues through checksum verification and corrects them by updating the handle or removing invalid references, thereby improving data integrity while minimizing processing time through automated operations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9128863B2Detection and correction of corrupted or dangling data object handles
Publication Date: 2015.09.08 NETAPP INC
  • US9128863B2 patent drawing
  • US9128863B2 patent drawing
  • US9128863B2 patent drawing

AI summary

Exemplary embodiments provide various techniques for detecting and correcting corrupted or dangling data object handles. In one example, a method is provided for correcting corrupted data object handles. In this method, a redirector file stored on a first logical data container is accessed. This redirector file includes a forward object handle pointing to a first data object stored on a second logical data container and includes a first checksum of the forward object handle. A second checksum of the forward object handle is determined and a comparison is made between the first and second checksums. If a mismatch is detected, the data objects stored on the second logical data container are scanned to extract backward object handles. A backward object handle can be identified to point back to the redirector file. The forward object handle can then be restored to point to the second data object based on the identification.