Per-Extent Checksum Algorithms in File Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file systems lack the ability to optimize data integrity by allowing different checksum algorithms for different extents of a file system object, leading to inefficient storage utilization and performance issues, particularly in systems with varying data importance.

Innovation Solution

A file system that allows different checksum algorithms to be used for different extents of a file system object, enabling optimal selection based on data importance, with the capability to change and manage checksum algorithms independently for each extent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single checksum algorithm is used for the entire file system object, then the system complexity is low and ease of operation is maintained, but storage utilization efficiency deteriorates and performance deteriorates due to inability to optimize for different data importance levels

Engineering Contradiction:
Improvestorage utilization efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent divides the file system object into multiple extents, allowing different checksum algorithms to be applied to different extents. This segmentation enables optimization of storage utilization for critical extents while using simpler or no checksums for less critical extents, thereby improving overall productivity without requiring complete system redesign

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different checksum algorithms to different extents based on their specific data importance and access patterns. Critical data extents use more robust checksum algorithms for higher reliability, while less critical extents use simpler algorithms or none at all, optimizing storage utilization efficiency locally for each extent's requirements

Inventive Principle:
Principle #3Local quality

2Reliability

If computationally complex checksum algorithms are used for all extents, then data integrity protection is improved, but processing speed deteriorates and performance deteriorates

Engineering Contradiction:
Improvedata integrity protectionVSAvoidprocessing speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent applies different checksum algorithms to different extents based on their specific data importance and access patterns. Critical data extents use more robust checksum algorithms for higher reliability, while less critical extents use simpler algorithms or none at all, optimizing storage utilization efficiency locally for each extent's requirements

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies checksum algorithms selectively only to extents that require data integrity protection, rather than uniformly to all extents. This partial action approach maintains reliability for critical data while avoiding the performance penalty of computing checksums for all data, thereby improving processing speed overall

Inventive Principle:
Principle #16Partial or excessive action

3Speed

If no checksum algorithm is used for any extent, then processing speed is maximized and performance is improved, but data integrity protection deteriorates

Engineering Contradiction:
Improveprocessing speedVSAvoiddata integrity protection
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies different checksum algorithms to different extents based on their specific data importance and access patterns. Critical data extents use more robust checksum algorithms for higher reliability, while less critical extents use simpler algorithms or none at all, optimizing storage utilization efficiency locally for each extent's requirements

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies checksum algorithms selectively only to extents that require data integrity protection, rather than uniformly to all extents. This partial action approach maintains reliability for critical data while avoiding the performance penalty of computing checksums for all data, thereby improving processing speed overall

Inventive Principle:
Principle #16Partial or excessive action

4Adaptability or versatility

If a checksum algorithm is applied uniformly to the entire file system object, then ease of operation is maintained and system complexity is low, but adaptability deteriorates due to inability to tailor checksum algorithms to different data requirements

Engineering Contradiction:
Improveadaptability to different data requirementsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the file system object into multiple extents, allowing different checksum algorithms to be applied to different extents. This segmentation enables optimization of storage utilization for critical extents while using simpler or no checksums for less critical extents, thereby improving overall productivity without requiring complete system redesign

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different checksum algorithms to different extents based on their specific data importance and access patterns. Critical data extents use more robust checksum algorithms for higher reliability, while less critical extents use simpler algorithms or none at all, optimizing storage utilization efficiency locally for each extent's requirements

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10102218B2File system with per-extent checksums
Publication Date: 2018.10.16 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10102218B2 patent drawing
  • US10102218B2 patent drawing
  • US10102218B2 patent drawing

AI summary

A file system allows a different checksum algorithm to be used for different extents of a file system object independently of other extents of the file system object. The checksum algorithm can be a selectable attribute of an extent or range of extents of a file system object, such that some extents of a file system object can use a first checksum algorithm, while other extents of the file system object can use a second checksum algorithm. An extent of the file system object also may have no associated checksum algorithm. The file system stores, for each extent of a file system object, data indicating a checksum for the extent and an indication of any checksum algorithm used for the extent.