File System Extended Attributes for Database Reconstruction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to effectively recreate the file hierarchy in network-attached storage systems when the database storage area experiences a large-scale loss or software coding errors, despite the content of stored files remaining intact.

Innovation Solution

The use of file system extended attributes to store information about individual storage files, allowing the database to be reconstructed by scanning these attributes and recreating the hierarchical database structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a database is used to store file hierarchy information in object-based storage, then users can access files through a familiar hierarchical structure, but the system becomes vulnerable to large-scale database loss or corruption that prevents file hierarchy recreation

Engineering Contradiction:
Improvefile access interfaceVSAvoiddatabase integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates a backup copy of the file hierarchy information by storing it in two different locations: the primary database and the extended attributes of files themselves. This copying strategy ensures that if the primary database is lost or corrupted, the file hierarchy can be reconstructed from the extended attributes, thereby resolving the vulnerability while maintaining ease of operation.

Inventive Principle:
Principle #26Copying

2Reliability

If file system extended attributes are used to store file information, then the database can be reconstructed after corruption, but the storage system becomes more complex

Engineering Contradiction:
Improvedatabase recovery capabilityVSAvoidstorage system structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes the extended attributes serve multiple functions: they store traditional file metadata and simultaneously serve as a backup repository for file hierarchy information. This multi-functionality approach allows the system to gain database recovery capability without adding separate dedicated backup structures, thereby limiting the increase in system complexity.

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

3Productivity

If the database stores complete file hierarchy information, then file access is efficient, but the system suffers when the database experiences large-scale loss

Engineering Contradiction:
Improvefile access efficiencyVSAvoidfile hierarchy data
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent performs preliminary action by pre-storing file hierarchy information in the extended attributes of files before any potential database loss occurs. This advance preparation ensures that when large-scale database loss happens, the recovery process can immediately proceed using the pre-stored information in extended attributes, minimizing information loss and maintaining productivity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11853165B2Using file system extended attributes to update databases in hierarchical file systems
Publication Date: 2023.12.26 SANDISK TECHNOLOGIES LLC
  • US11853165B2 patent drawing
  • US11853165B2 patent drawing
  • US11853165B2 patent drawing

AI summary

Systems and methods are disclosed for reconstructing a file hierarchy by scanning attributes of stored files. Stored files can have a file hierarchy that is maintained in a database stored on a storage device. The files can be stored as objects on the device using a flat file structure. The file database provides the file hierarchy. The systems and methods disclosed herein store information in file system extended attributes for individual storage files such that the database can be reconstructed by scanning the storage files, using values in the extended attributes to recreate the hierarchical database.