File System Data Inconsistency Management via Client Notification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing file system management technologies fail to effectively manage data inconsistencies, leading to data loss and unavailability due to automatic zeroing of inconsistent file system blocks without client intervention, which prevents users from taking corrective actions.

Innovation Solution

A method where a client is informed of data inconsistencies in a file system block, allowing it to determine and execute appropriate actions, such as taking the logical volume offline or starting a backup, instead of automatically writing zeros to the block, thereby enabling efficient recovery and minimizing data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automatic zeroing of inconsistent file system blocks is performed, then data consistency is restored, but data loss occurs

Engineering Contradiction:

Improvedata consistencyVSAvoiddata loss

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

The system performs preliminary detection of inconsistent file system blocks and notifies the client before any corrective action is taken. This allows the client to prepare backup copies of the data in advance, so that when zeroing is performed to restore consistency, the data can be recovered from the backup rather than being permanently lost.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If automatic zeroing of inconsistent blocks is performed, then file system integrity is improved, but client control is reduced

Engineering Contradiction:

Improvefile system integrityVSAvoidclient control

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements a feedback mechanism where the file system detects inconsistencies and notifies the client, who then decides on the appropriate corrective action. The client can choose to take the logical volume offline, start a backup, or perform other actions based on the notification. This feedback loop maintains file system integrity while preserving client control and flexibility in handling different scenarios.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If manual intervention is required for inconsistent blocks, then data recovery options increase, but response time increases

Engineering Contradiction:

Improvedata recovery optionsVSAvoidresponse time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary notification to the client about inconsistent blocks, providing advance warning that allows manual intervention if needed. However, the system is designed so that the notification itself triggers automated backup processes or prepares recovery options in advance, reducing the actual response time when manual intervention is required. The client receives timely notifications with pre-prepared recovery options.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10262023B1Managing data inconsistencies in file systems

Publication Date: 2019.04.16 EMC IP HLDG CO LLC

AI summary

A method is used in managing data inconsistencies in file systems. A data inconsistency is detected in a file system data block of a file system. The file system includes a set of file system data blocks. Information regarding the data inconsistency is provided to a client of the file system. Based on the information, the client is enabled to determine an action for recovering from the data inconsistency.