Zero Block Elimination Reporting in File Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional file systems fail to accurately account for storage space reduction due to zero block elimination (ZBE) in efficiency statistics, leading to overcounting and inaccurate storage savings, as zero blocks are not included in logical data and multiple writes to the same storage region are counted multiple times.

Innovation Solution

A data management component (DMC) associates zero extents with sparse regions during write operations, tracks the number of zero blocks eliminated, and adjusts storage efficiency statistics to accurately reflect storage space savings by linking zero references with sparse regions and incrementing counters only when new zero extents are created.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If zero blocks are eliminated from write operations to reduce storage space usage, then storage efficiency is improved, but accurate tracking of storage savings becomes difficult leading to overcounting in efficiency statistics

Engineering Contradiction:
Improvestorage space usageVSAvoidstorage efficiency statistics accuracy
Core Design Contradiction:
Quantity of substanceVSMeasurement precision

Solution Approach 1:

The patent introduces zero extents as intermediary data structures that represent eliminated zero blocks. These zero extents serve as mediators between the physical elimination of zero blocks and the logical tracking of storage savings. By maintaining zero extent maps that track which storage regions contain only zero blocks, the system can accurately measure storage efficiency without actually writing the zero blocks to disk, thus preventing overcounting while maintaining measurement precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements feedback mechanisms through zero extent counters and tracking structures that monitor the number of zero blocks eliminated. This feedback allows the system to adjust efficiency statistics dynamically, ensuring that storage savings are accurately reflected in efficiency metrics. The feedback loop prevents overcounting by comparing actual zero block elimination against tracked statistics, enabling continuous correction and accurate measurement of storage efficiency improvements.

Inventive Principle:
Principle #23Feedback

2Ease of manufacture

If multiple writes to the same storage region are counted multiple times for efficiency statistics, then calculation simplicity is improved, but storage savings are overcounted leading to inaccurate statistics

Engineering Contradiction:
Improvestatistics calculation simplicityVSAvoidstorage savings accuracy
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The patent creates copies of zero block information in the form of zero extent entries in zero extent maps. Instead of directly tracking each write operation, the system maintains a copy of the zero block metadata that can be efficiently queried and counted. This copying mechanism allows for simple aggregation of storage savings across multiple writes while preventing overcounting through deduplication logic that identifies when the same storage region is written multiple times with zero blocks.

Inventive Principle:
Principle #26Copying

3Quantity of substance

If zero blocks are not included in logical data, then storage space is reduced, but accurate accounting of total data written becomes difficult

Engineering Contradiction:
Improvephysical storage spaceVSAvoiddata written accounting information
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent performs preliminary action by creating zero extent entries before actually eliminating zero blocks from write operations. These pre-created metadata structures contain all necessary information about the zero blocks (storage region locations, sizes, etc.), enabling accurate accounting of total data written even though the actual zero block data is not physically written to storage. This preliminary metadata creation ensures that information about eliminated data is preserved for accounting purposes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11347692B1Zero block elimination reporting for a file system
Publication Date: 2022.05.31 EMC IP HLDG CO LLC
  • US11347692B1 patent drawing
  • US11347692B1 patent drawing
  • US11347692B1 patent drawing

AI summary

Zero block elimination (ZBE) and statistical accounting for reduction in storage space used in a memory component of a file system due to ZBE can be managed. During a write operation, in response to eliminating a zero block from the write operation, a data management component (DMC) can associate a zero extent with a sparse region that represents a block in the memory component where the zero block was to have been written, unless a zero extent is already associated with that block. DMC can determine a number of zero blocks eliminated from write operations due to ZBE based on the number of zero extents associated with files stored in the memory component, to facilitate determining an amount of reduction of use of storage space in the memory component, or a data reduction ratio, storage efficiency ratio, or zero reduction ratio associated with the memory component, due to ZBE.