Active File Instant Cloning via Block Map and Stub Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for creating new instances of active files are resource-intensive and inefficient, requiring significant computing resources and failing to optimize data storage and transmission effectively.

Innovation Solution

The technique involves generating a new stub in the user namespace and cloning the block map file, which includes offsets and location pointers from the original file, without copying user file data, and using deduplication mechanisms to manage data segments, allowing for efficient cloning and modification of active files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional file copying mechanisms are used to create new instances of active files, then complete file data is replicated, but significant computing resources and storage capacity are consumed

Engineering Contradiction:
Improvedata integrityVSAvoidcomputing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The file system is segmented into metadata structures (block maps, stubs) and actual data segments. When cloning a file, only the metadata structures are copied while data segments are shared through references, separating the cloning operation from actual data replication and reducing resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of copying actual file data, the patent copies only the block map file and creates a new stub in the user namespace. The cloned file references the same data segments as the original through shared references, achieving file instantiation without data duplication.

Inventive Principle:
Principle #26Copying

2Productivity

If traditional file cloning methods are used, then new file instances can be created, but the process is resource-intensive and inefficient

Engineering Contradiction:
Improvefile cloning efficiencyVSAvoidstorage resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

Multiple file instances share common data segments through shared references in their block maps. This merging approach allows multiple cloned files to coexist without duplicating storage resources, as they all reference the same underlying data segments.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The cloning process copies only lightweight metadata structures (block maps and stubs) rather than actual file data. This creates new file instances rapidly with minimal resource consumption, as the copied metadata is negligible compared to actual file content.

Inventive Principle:
Principle #26Copying

3Quantity of substance

If data is compressed to save storage resources, then storage efficiency improves, but compression and decompression require additional processing overhead

Engineering Contradiction:
Improvestorage capacityVSAvoidprocessing overhead
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The deduplication system automatically identifies and eliminates duplicate data segments across files without requiring manual intervention or complex compression algorithms. The system self-manages storage optimization by comparing data segments and creating shared references, reducing both storage capacity and processing overhead.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9020909B2Active file Instant Cloning
Publication Date: 2015.04.28 QUEST SOFTWARE INC
  • US9020909B2 patent drawing
  • US9020909B2 patent drawing
  • US9020909B2 patent drawing

AI summary

Techniques and mechanisms are provided to instantly clone active files including active optimized files. When a new instance of an active file is created, a new stub is generated in the user namespace and a block map file is cloned. The block map file includes the same offsets and location pointers that existed in the original block map file. No user file data needs to be copied. If the cloned file is later modified, the behavior can be same as what happens when a de-duplicated file is modified.