File Replication Using Inode Identifiers to Prevent Redundant Copying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file replication methods in distributed systems face challenges with file renaming and hard links, leading to redundant copying and incorrect file identification, as they rely on file names rather than unique physical location identifiers.
Innovation Solution
Implementing file replication using file content location identifiers, such as inode identifiers, to uniquely identify files by their physical storage locations, rather than names, and creating file name aliases to manage replication and other operations like backup and self-healing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If file replication uses file names to identify files, then file operations are simple and straightforward, but redundant copying occurs when files are renamed and hard links cause incorrect file identification
Solution Approach 1:
The patent introduces inode identifiers as an intermediary between file names and physical file locations. Instead of directly using file names for replication identification, the system uses inode identifiers which remain constant regardless of file renaming or hard link creation. This intermediary layer resolves the contradiction by providing stable identification (improving reliability) while maintaining simple replication operations (preserving productivity).
Solution Approach 2:
The patent replaces the mechanical naming system (file names that change with renaming) with an identifier system based on inodes (which have stable physical location identifiers). This substitution eliminates the fundamental problem where file name changes cause redundant copying, as inode identifiers remain constant even when file names or hard links change.
2Ease of manufacture
If file replication tracks files by name, then implementation is straightforward, but file renaming causes deletion and recopying of unchanged files
Solution Approach 1:
By introducing inode identifiers as a mediator between the replication system and file names, the patent enables straightforward implementation (the replication agent simply compares inode identifiers) while eliminating redundant copying of renamed files (since the inode identifier remains constant). This resolves the contradiction by providing both implementation simplicity and time efficiency.
3Adaptability or versatility
If soft links are used to reference files, then file organization is flexible, but replication systems cannot distinguish between different files with the same name
Solution Approach 1:
The patent uses inode identifiers as an intermediary that provides unique identification for each file instance, even when multiple soft links or hard links point to files with identical names. The replication system compares inode identifiers rather than file names, enabling precise file distinction (improving measurement precision) while maintaining the flexibility of symbolic links and hard links (preserving adaptability).
Data Source
AI summary
Systems and methods for file replication using file content location identifiers. An example method comprises: receiving, by a processing device, an index node number identifying a first index node associated with a file residing on a first file server, the first index node referencing a physical location of contents of the file; identifying a replica of the file residing on a second file server; assigning the index node number of the first index node to a second index node referencing a physical location of contents of the replica of the file on the second file server; performing, by the processing device, a file system operation by accessing the replica of the file referenced by the index node number.