LTFS File Deletion via In-Memory Index Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Linear Tape File System (LTFS) experiences timeouts and inefficiencies when accessing files due to varying access times based on file location, leading to issues with file synchronization and management between primary and secondary storage, resulting in accumulation of unnecessary files and increased mount/unmount times.
Innovation Solution
A method that deletes a file from a primary file system by updating the directory entry in an in-memory index and index cache of a secondary file system, and setting a dirty flag to TRUE, allowing for file deletions without mounting the secondary storage, using a computer-implemented method and system with program instructions stored on non-transitory media.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If files are moved from primary storage to secondary storage using HSM migration policy, then storage efficiency is improved by archiving inactive files, but file synchronization problems occur when deleted or updated files remain in secondary storage
Solution Approach 1:
The system performs preliminary actions by maintaining an in-memory index that tracks file deletions and updates before they occur in the secondary storage. When a file is deleted or updated in primary storage, the in-memory index is immediately updated, and the dirty flag is set, preparing the system to handle synchronization without requiring immediate secondary storage access.
Solution Approach 2:
The in-memory index acts as an intermediary between primary storage and secondary storage, tracking file operations (deletions, updates) that need to be reflected in secondary storage. This intermediary layer allows the system to defer actual synchronization operations until the secondary storage is mounted, avoiding immediate mount/unmount cycles while maintaining synchronization awareness.
2Reliability
If the secondary storage is mounted to remove deleted files or update file copies, then file synchronization is improved, but mount/unmount time increases and operational efficiency decreases
Solution Approach 1:
The system performs preliminary updates to the in-memory index and sets the dirty flag when files are deleted or updated in primary storage, so that when secondary storage is mounted, the synchronization can proceed efficiently without requiring previous mount/unmount cycles. This preliminary tracking eliminates the need for immediate mount operations to maintain synchronization.
Solution Approach 2:
The system uses the existing mount event of secondary storage for dual purposes: both for normal operations and for synchronizing deleted/updated files. By tracking changes in the in-memory index and using the dirty flag, the system automatically performs synchronization during the next mount event without requiring separate mount/unmount operations, making the mount operation serve multiple functions.
3Speed
If the secondary storage is not mounted when a file is deleted or updated, then operational speed is improved, but the secondary storage must be mounted, previously deleted files removed, unmounted, and remounted before available for use
Solution Approach 1:
The system performs preliminary tracking of file deletions and updates in the in-memory index without requiring secondary storage to be mounted. This allows rapid operation in the primary storage while deferring the actual removal of files from secondary storage until the next mount event, eliminating unnecessary mount/unmount/remount cycles.
Solution Approach 2:
The system maintains continuous tracking of file operations through the in-memory index and dirty flag mechanism, ensuring that synchronization is always ready to proceed when secondary storage is mounted. This continuous awareness of file changes eliminates gaps in functionality and ensures storage availability is restored quickly when mounting occurs.
Data Source
AI summary
An approach for deleting a file from a primary file system. The approach deletes a directory entry, associated with a file, from an in-memory index associated with a secondary file system. The approach updates an index cache associated with a secondary file system, based on the in-memory index. The approach updates a dirty flag, associated with the secondary file system, to a value of TRUE.