Multi-log Checkpoint Transaction Order in Storage Logs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file system operations face challenges in maintaining consistency and scalability when modifying multiple logs or chunks, particularly in scenarios where one log/chunk is modified at a different time or partially at the same time as another, leading to inefficiencies and potential inconsistencies.

Innovation Solution

The implementation employs a checkpoint-based system that uses a set of log holds and memory buffer lists to track the synchronization of modified system metadata, allowing for parallel journalling and synchronization of transaction log entries across multiple chunks, without relying on a global bitmap or strict ordering constraints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a global bitmap is used to track log chunk modifications, then consistency of file system metadata can be maintained, but device complexity and validation overhead increase

Engineering Contradiction:
Improveconsistency of file system metadataVSAvoidcomplexity of log tracking system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the global bitmap mechanism from the log management system and replaces it with individual sequence numbers assigned to each log chunk. This removes the complex centralized tracking structure while maintaining the ability to verify consistency through simpler per-chunk sequence validation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the centralized global bitmap tracking into distributed sequence number tracking across individual log chunks. Each chunk maintains its own sequence number, eliminating the need for a unified global state and reducing overall system complexity while preserving consistency verification capabilities.

Inventive Principle:
Principle #1Segmentation

2Reliability

If strict ordering constraints are enforced for log chunk modifications, then consistency can be maintained, but productivity and operational efficiency decrease

Engineering Contradiction:
Improveconsistency of file system metadataVSAvoidoperational efficiency of log modifications
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces dynamic sequence numbers that are assigned independently to each log chunk based on modification time. This allows the system to adapt to parallel modifications without requiring predetermined ordering, enabling concurrent operations while maintaining consistency through sequence number comparison.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent assigns sequence numbers to log chunks in advance during the modification process, rather than requiring sequential processing. This preliminary assignment of identification markers enables parallel execution of log modifications while maintaining the ability to verify consistency through sequence number validation.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple log chunks are modified in parallel, then productivity increases, but the risk of inconsistencies and validation complexity increases

Engineering Contradiction:
Improvespeed of log modification operationsVSAvoidconsistency of file system metadata
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback through sequence number validation, where the system continuously monitors and compares sequence numbers of modified log chunks. This feedback mechanism detects inconsistencies caused by parallel modifications and triggers appropriate validation or rollback actions, ensuring consistency while allowing parallel operations.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces sequence numbers as intermediary identifiers that mediate between parallel log modification operations and consistency verification. These intermediaries carry timing information that enables the system to resolve potential conflicts without requiring complex coordination protocols, maintaining both parallelism and consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If validation of all modified metadata is performed before releasing log space, then consistency is ensured, but loss of time and operational overhead increase

Engineering Contradiction:
Improveconsistency of file system metadataVSAvoidtime to release log storage objects
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs partial validation by checking only the sequence numbers of log chunks rather than validating all modified metadata content. This selective validation approach verifies consistency sufficient to detect errors while avoiding the time cost of comprehensive validation, enabling faster log space release.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12298914B2Multi-log checkpoint-based retirement transaction order in multi-chunk log
Publication Date: 2025.05.13 DELL PROD LP
  • US12298914B2 patent drawing
  • US12298914B2 patent drawing
  • US12298914B2 patent drawing

AI summary

Described is technology that facilitates journalling a transaction log entry to chunks of storage while allowing for obtaining of modified system metadata associated therewith in the case of a computing device issue. An associated method comprises at least storing, by a system operatively coupled to a processor, a set of transaction log entries at log space of a storage log associated with a file system, wherein the transaction log entries comprise instructions for fulfilling a set of transactions, and wherein the transactions define changes to the file system, generating a checkpoint marker corresponding to a set of log storage objects of the storage log at which the transaction log entries are stored, and based on the checkpoint marker, preventing, by the system, reuse of the log space until writing of all modified system metadata corresponding to the transaction log entries has been executed.