File System Space Reclamation via Dummy File Expansion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
File systems, particularly thin-provisioned systems, inefficiently utilize free space after file deletion, leading to wasted space and out-of-space errors, and snapshot implementations unnecessarily freeze freed space, affecting storage utilization and performance.
Innovation Solution
Creating a dummy file that fills the volume and maps its locations to reclaim the corresponding space, allowing for efficient reuse of freed space and improving snapshot performance by avoiding redundant space and read-modify-write operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a thin provisioned file system advertises more space than actually available to avoid fragmentation, then storage utilization increases, but out-of-space errors occur when new files cannot be written to previously freed regions
Solution Approach 1:
The system performs preliminary actions by proactively reclaiming space from deleted files before new files need to be written. The file system actively identifies and reclaims space from regions previously occupied by deleted files, ensuring this space is available for future allocations rather than waiting until out-of-space conditions occur.
Solution Approach 2:
The file system serves itself by automatically managing space reclamation without external intervention. The system continuously monitors for deleted files and automatically reclaims their space, making the file system self-sufficient in managing its own storage resources and avoiding out-of-space errors.
2Adaptability or versatility
If the file system takes a snapshot of the volume, then point-in-time recovery capability is provided, but freed space is frozen and cannot be reused until the snapshot is deleted
Solution Approach 1:
The system segments the volume into snapshot regions and non-snapshot regions. When a snapshot is taken, only the necessary portions are frozen while other regions remain available for new allocations. This segmentation allows the file system to maintain snapshot capability while still providing space for new files in non-snapshot regions.
Solution Approach 2:
The system dynamically manages snapshot space by identifying and releasing space that is no longer needed by snapshots. As snapshots are deleted or expire, their associated space is dynamically reclaimed and made available for new file allocations, allowing the system to adapt space availability based on current snapshot requirements.
3Ease of operation
If the file system marks regions as free after file deletion, then space is available for future use, but the space is not efficiently utilized and may be wasted
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring the file system for deleted files and their associated free space. This feedback loop enables the system to identify reclaimable space and trigger reclamation operations, ensuring that freed space is actively managed and reused rather than left wasted.
Solution Approach 2:
The file system maintains continuous useful action by constantly monitoring for deleted files and immediately reclaiming their space. This continuous process ensures that space is rapidly transitioned from a deleted state back to an available state for new allocations, minimizing the duration of space waste and maintaining high storage efficiency.
Data Source
AI summary
Technologies are provided for reclaiming a file system coupled to a block device. In these technologies, a dummy file is created. The dummy file is expanded to fill a volume in the block device. A mapping of the dummy file to locations in the volume is retrieved. When the mapping of the dummy file to the locations in the volume is retrieved, corresponding space in the volume is reclaimed. This space may include the locations in the volume corresponding to the mapping of the dummy file. When this space in the volume is reclaimed, the dummy file is deleted.