Intent Log Testing via File System Copying

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for testing the accuracy and integrity of intent logs in file systems are inefficient and require manual system crashes, leading to potential delays and inaccuracies in delta commitment and file system operations.

Innovation Solution

A method for automatically testing intent log integrity by creating a frozen file system, generating and storing deltas in the intent log, copying the system to commit these deltas, and comparing the original and copied systems to validate log accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual crashing methods are used to test intent log accuracy, then testing can be performed, but system operations are disrupted and testing efficiency is reduced

Engineering Contradiction:
Improveintent log accuracyVSAvoidtesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by creating a frozen copy of the file system before performing test operations. The freeze command captures the current state of the file system including all pending deltas in the intent log, allowing subsequent commit operations to be tested on the frozen copy without affecting the live system. This enables automated testing to proceed efficiently while maintaining system reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If deltas are committed to the file system, then the intent log is updated, but system operations must be blocked until space is available

Engineering Contradiction:
Improvedelta accuracyVSAvoidoperation delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent uses copying by creating a frozen copy (second file system) of the original file system. All delta commit operations are performed on the frozen copy instead of the live system. This allows unlimited delta commits to be tested without blocking system operations, as the frozen copy is a static snapshot that does not require space management during testing.

Inventive Principle:
Principle #26Copying

3Measurement precision

If the intent log is tested using conventional methods, then accuracy can be verified, but the process is manual and time-consuming

Engineering Contradiction:
Improveintent log validation accuracyVSAvoidtesting process complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements self-service by creating an automated testing methodology where the system tests itself. The freeze command, delta generation, commit operations, and comparison processes are all performed automatically through a structured sequence of commands. This eliminates manual intervention while maintaining high validation accuracy, reducing both time consumption and operational complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7490096B2Automatic intent log testing
Publication Date: 2009.02.10 ORACLE AMERICAN INC
  • US7490096B2 patent drawing
  • US7490096B2 patent drawing
  • US7490096B2 patent drawing

AI summary

A method for testing an intent log for a file system that includes creating a first file system, issuing a command to freeze the first file system, performing a plurality of commands on the first file system to obtain a plurality of deltas, wherein each of the plurality of deltas is stored in the intent log and is not committed to the first file system, copying the first file system to obtain a second file system, committing each of the plurality of deltas in the intent log to the second file system, unfreezing the first file system and committing each of the deltas in the intent log to the first file system, and comparing the first file system, after committing each of the deltas in the intent log, to the second file system to determine whether the intent log is valid.