File System Metadata Validation Using Summary Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional File System Checking (FSCK) utilities face inefficiencies in validating and repairing file systems with replicated files, as they repetitively evaluate shared metadata between files and snapshot copies, leading to high storage and memory resource consumption.

Innovation Solution

Implementing a summary table to store validation information for metadata, allowing each inode and its snapshot copies to share validation results, thus avoiding redundant processing of shared metadata blocks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional FSCK utilities validate file system metadata for each inode independently, then completeness of validation is ensured, but storage and memory resource consumption increases due to redundant evaluation of shared metadata

Engineering Contradiction:
Improvevalidation completenessVSAvoidstorage resource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges the validation results for shared metadata blocks by creating a summary table that consolidates validation information across multiple inodes. When metadata blocks are shared between inodes (as in snapshot copies), the validation results are combined in the summary table, allowing a single validation result to serve multiple inodes and reducing redundant storage of validation data.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The summary table structure serves multiple functions: it stores validation results for shared metadata, enables efficient lookup of validation status for any inode, and reduces the overall data required for validation processing. This multi-functional approach allows the system to maintain validation completeness while significantly reducing storage resource consumption.

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

2Reliability

If conventional FSCK utilities process each inode and its metadata independently, then validation thoroughness is maintained, but processing time increases due to repetitive evaluation of shared metadata blocks

Engineering Contradiction:
Improvevalidation thoroughnessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary validation of shared metadata blocks and stores the results in the summary table before processing individual inodes. This preliminary action allows subsequent inode processing to skip redundant validation steps by simply looking up the pre-computed validation results in the summary table, significantly reducing processing time while maintaining validation thoroughness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The summary table provides feedback about the validation status of shared metadata blocks to the inode processing mechanism. When an inode needs validation, the system checks the summary table for existing validation results of shared metadata, uses this feedback to determine whether full validation is needed or can skip to already-validated portions, thereby reducing processing time without compromising thoroughness.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If validation information is stored for each inode separately, then ease of retrieval is maintained, but memory utilization decreases due to redundant storage of shared metadata validation results

Engineering Contradiction:
Improvevalidation result retrievalVSAvoidmemory utilization
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent creates a simplified copy of validation information in the summary table that represents shared metadata blocks. Instead of storing complete validation results for each inode separately, the summary table maintains a condensed copy of validation status that can be efficiently retrieved and applied to multiple inodes, reducing memory utilization while maintaining ease of retrieval through the summary structure.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8954383B1Analyzing mapping objects of file systems
Publication Date: 2015.02.10 EMC IP HLDG CO LLC
  • US8954383B1 patent drawing
  • US8954383B1 patent drawing
  • US8954383B1 patent drawing

AI summary

A method is used in analyzing mapping objects of file systems. Each mapping object of a set of mapping objects of files of a file system is analyzed by iterating over the set of mapping objects. A file is associated with a first mapping object of the set of mapping objects and a snapshot copy of the file is associated with a second mapping object of the set of mapping objects. The second mapping object shares a subset of a set of storage objects associated with the first mapping object. Information for each storage object of the set of storage objects associated with each mapping object of the set of mapping objects is stored. Based on the stored information, each storage object of the set of storage objects associated with each mapping object of the set of mapping objects is processed.