File System Data Replication Checksum Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data replication methods in file systems face challenges in efficiently managing data block replication and synchronization, especially when dealing with corrupted data blocks and large file systems, which can lead to resource inefficiencies and data integrity issues.

Innovation Solution

A method that involves determining primary data blocks to replicate by reading space map block entries, computing checksums, and comparing them between primary and secondary file systems to identify mismatches, with the option to replicate only mismatched blocks or all blocks allocated after a reliable snapshot, optimizing the replication process based on estimated time and resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all data blocks are replicated to ensure data integrity, then reliability is improved, but productivity deteriorates due to excessive resource consumption and time required for replication

Engineering Contradiction:
Improvedata integrityVSAvoidreplication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by computing checksums for only those data blocks that need verification rather than all blocks. The system identifies specific blocks requiring replication by comparing checksums between primary and secondary file systems, thereby avoiding the excessive resource consumption of replicating entire file systems while still ensuring data integrity for critical blocks.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent segments the file system into individual data blocks and processes them independently through checksum verification. This segmentation allows the system to identify and replicate only the specific blocks that have mismatches or corruption issues, rather than treating the entire file system as a single unit that requires complete replication.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If checksum verification is performed for all data blocks to detect corruption, then measurement precision is improved, but use of energy worsens due to increased computational overhead

Engineering Contradiction:
Improvecorruption detection accuracyVSAvoidcomputational resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent performs checksum verification selectively rather than universally. It computes checksums only for data blocks that require verification based on replication needs or corruption suspicion, thereby maintaining high detection accuracy for critical blocks while reducing overall computational energy consumption across the entire file system.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If frequent snapshots are taken to maintain data availability, then reliability is improved, but loss of time worsens due to resource consumption during snapshot operations

Engineering Contradiction:
Improvedata availabilityVSAvoidsnapshot operation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent takes snapshots selectively rather than continuously. It creates snapshots only when data changes require preservation or when corruption detection is needed, thereby maintaining data availability for critical recovery scenarios while minimizing the time loss associated with frequent snapshot operations across the entire file system.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8433683B2Systems and methods of data replication of a file system
Publication Date: 2013.04.30 ORACLE INT CORP
  • US8433683B2 patent drawing
  • US8433683B2 patent drawing
  • US8433683B2 patent drawing

AI summary

The invention relates to methods for replicating a primary file system on a primary host to a secondary file system on a secondary host including determining a primary data block to replicate by reading a space map block entry (b, e) of the primary data block, wherein b represents the first snapshot and e the last snapshot to use the primary data block; computing a checksum of a primary data block and sending its number to the secondary host and determining a secondary data block that corresponds and computing its checksum then comparing the primary and secondary data block checksums and replicating the primary data block on the secondary file system when the primary and secondary checksums mismatch for the primary file system. In another aspect of the method if the primary and secondary checksums mismatch the method sends all data blocks from the primary file system allocated after a reliable snapshot on the secondary file system to the secondary host to be written on the secondary file system.