Placement Hint Tag Replication Across Heterogeneous File Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern data centers face challenges in interoperability, replication, and mobility of file systems with different layouts due to varying locations of placement hint tags, which hinders seamless data management and efficient storage utilization across different file system nodes.

Innovation Solution

A global scale system abstracts layout differences by storing placement hint tags in either inodes or extended attributes based on file system versions, enabling unified namespace replication and migration without significant upgrades, using a federated unified namespace server to redirect clients to appropriate file system nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If file systems evolve to different versions with different tag layouts, then new features and improved space utilization are achieved, but interoperability and replication between different file system nodes deteriorate

Engineering Contradiction:
Improvefile system feature setVSAvoidinteroperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the tag data structure into multiple possible layouts (Layout A, Layout B, etc.), where each layout version is self-contained and can be independently processed. This allows different file system nodes to use different layouts while maintaining compatibility through version identification fields that enable proper routing and processing of tags across version boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary translation layer that converts tags between different layouts. When a tag is created or modified, the system determines the appropriate layout version and translates it to the destination node's expected layout format. This intermediary process ensures seamless interoperability without requiring all nodes to use the same layout version.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If placement hint tags are stored in different locations in different file system versions, then version-specific optimizations are achieved, but replication and migration between nodes become complex

Engineering Contradiction:
Improvestorage efficiencyVSAvoidreplication complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent changes the parameter of tag storage location based on the file system version. Each layout version specifies different parameters for where tags are stored (e.g., in inode, in extended attributes, in separate metadata structures). The system dynamically adjusts these parameters based on the source and destination node versions, allowing optimization for each version while maintaining replication capability through automatic parameter translation.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If data is replicated across multiple remote sites for disaster recovery, then data availability is improved, but storage capacity requirements increase

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements selective copying of only the essential file metadata and placement hint tags during replication operations, rather than copying entire file contents. This allows multiple remote sites to maintain synchronized metadata information for disaster recovery while consuming significantly less storage capacity, as the replicated data structures are compact representations rather than full data copies.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11675671B1Sending records for replication of tags in global scale systems
Publication Date: 2023.06.13 DELL PROD LP
  • US11675671B1 patent drawing
  • US11675671B1 patent drawing
  • US11675671B1 patent drawing

AI summary

A source node creates a file and a grouping tag for the file. The source node stores the grouping tag in a location in metadata for the file. When preparing for replication, the source node retrieves the grouping tag from the location in the metadata. If the legacy location in the metadata includes any value which was stored after the most recent replication involving the file, and the size of the legacy location in the metadata was changed after the most recent replication involving the file, then the system enables a destination node to store the grouping tag in the legacy location in the metadata by sending records comprising a request to replace a record stored at the legacy location in the metadata with a larger record, and combining the grouping tag with any value which changed the size of the metadata after a most recent replication involving the file.