Embedded Metadata Blocks for File System Map Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file systems face difficulties in recovering from corrupted directory or block information maps, particularly in NAND storage, where metadata is not stored with data, leading to potential loss of data and metadata information.

Innovation Solution

An apparatus and method that stores both data and metadata together, with a controller processor generating metadata parameters to facilitate partial repair of the block information map during data writing and retrieving, sorting, and rebuilding the map based on valid metadata during recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If metadata is stored separately from data in traditional file systems, then the file system structure is simple and easy to manage, but the block information map becomes vulnerable to corruption and difficult to recover

Engineering Contradiction:
Improveblock information map recoveryVSAvoidfile system structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines metadata and data into the same storage location by embedding metadata within data blocks. Each data block contains both the data payload and associated metadata (such as file ID, block order, and validity flags), eliminating the separate metadata storage structure and enabling self-contained recovery units that can be independently validated and used to rebuild the block information map.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the file system into independent data blocks, each containing its own metadata. This segmentation allows individual blocks to be validated and recovered independently without requiring access to a centralized metadata structure, enabling partial recovery of the block information map even when some blocks are corrupted.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If metadata is not stored with data, then storage space is optimized and metadata management is simplified, but data integrity cannot be verified and recovery is difficult when corruption occurs

Engineering Contradiction:
Improvedata and metadata recoveryVSAvoidstorage structure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges metadata with data within the same block structure, ensuring that each data block contains all necessary information for its own validation and recovery. This includes embedding file identification, block ordering information, and validity flags directly with the data, eliminating the risk of data-metadata separation and enabling complete recovery units.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary embedding of metadata with data during the write operation, so that recovery information is already in place before any potential corruption occurs. This preliminary action ensures that when recovery is needed, all necessary information is already associated with the data blocks, eliminating the need for complex reconstruction processes.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If the block information map is stored centrally, then map management is efficient and consistent, but the entire map is lost when corruption occurs

Engineering Contradiction:
Improveblock information map managementVSAvoidmap corruption resistance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized block information map into distributed metadata entries embedded within each data block. Each block contains its own identification and ordering information, eliminating the single point of failure in centralized map storage. This segmentation allows the system to reconstruct the block information map by gathering metadata from individual blocks rather than relying on a central structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses embedded metadata within data blocks as an intermediary that carries block information map data. Instead of maintaining a separate central map, the system uses the metadata fields within each block (file ID, block order, validity flags) as intermediaries to convey the necessary information for map reconstruction, eliminating the vulnerability of centralized storage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11436101B2Rebuild directory/block allocation map from embedded data block information in file system disk
Publication Date: 2022.09.06 SAMSUNG ELECTRONICS CO LTD
  • US11436101B2 patent drawing
  • US11436101B2 patent drawing
  • US11436101B2 patent drawing

AI summary

According to one general aspect, an apparatus may include a storage element configured to store both data and metadata, wherein each piece of data is associated with and stored with a corresponding piece of metadata. The apparatus may include a controller processor. The controller processor may be configured to, in response to a piece of data being written to the apparatus: generate a piece of metadata that includes a set of parameters to facilitate a at least partial repair of a block information map, and embed the piece of metadata with the corresponding piece of data.