Transaction Safe File System Dual Metadata Sets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

File systems are vulnerable to corruption due to power disruptions or interruptions during complex operations, leading to incomplete modifications and potential data loss.

Innovation Solution

A transaction-safe file system uses two sets of file allocation tables and bitmap images, where one set is modified while the other remains as a last known good set, with a pointer toggled to commit changes atomically, ensuring data integrity even during power outages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single set of file allocation tables and bitmap images is used for file modifications, then the file system structure is simple, but the system is vulnerable to corruption during power disruptions or interruptions

Engineering Contradiction:
Improvedata integrityVSAvoidfile system structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The file system divides the file allocation tables and bitmap images into two separate sets: a current set for active modifications and a last known good set for recovery. This segmentation allows the system to maintain a backup copy of the file system metadata, enabling corruption recovery while keeping the overall structure manageable through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by maintaining a pre-synchronized copy of the file allocation tables and bitmap images before modifications occur. This advance preparation ensures that a valid backup exists before any write operations, allowing the system to revert to the last known good state if power disruption occurs during modification.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If two sets of file allocation tables and bitmap images are maintained for transaction safety, then data integrity is protected during power failures, but storage space and system complexity increase

Engineering Contradiction:
Improvetransaction safetyVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The file system metadata is segmented into two distinct sets stored in different location ranges within the storage medium. This spatial segmentation allows efficient management of the dual sets, enabling the system to maintain transaction safety while optimizing storage utilization through structured organization of the backup and current metadata sets.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If file modifications are performed in multiple steps, then complex file operations can be completed, but the system becomes vulnerable to corruption if interruption occurs during the steps

Engineering Contradiction:
Improvefile operation capabilityVSAvoidcorruption resistance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary synchronization of the file allocation tables and bitmap images to the last known good set before initiating complex multi-step file operations. This preliminary action ensures that if interruption occurs during any step of the complex operation, the system can recover using the pre-synchronized backup, thus maintaining both operational versatility and corruption resistance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the completion status of file modification steps is continuously monitored. If an interruption is detected during multi-step operations, the feedback triggers a recovery process that uses the last known good set to restore consistency, ensuring that complex operations can be attempted without compromising system reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9239761B2Storage system format for transaction safe file system
Publication Date: 2016.01.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9239761B2 patent drawing
  • US9239761B2 patent drawing
  • US9239761B2 patent drawing

AI summary

A transaction safe file system uses two sets of file allocation tables and bitmap images to perform file modifications on one of the sets while the other set remains a last known good set. After a modification is complete, a pointer is changed to the newly modified set, and the newly modified set becomes the last known good set. The sets are then synchronized. The file allocation table is used to define cluster chains while the bitmap image is used to determine if a cluster is free or not. In some operations, only the bitmap image may need to be manipulated. The file system may be used in a transaction safe mode as well as a non-transaction safe mode.