Transparent Compression Storage Writes During Out-of-Space States
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Storage devices with built-in transparent compression face challenges in handling out-of-space scenarios, particularly when used through filesystems, as they cannot differentiate between safe and unsafe write operations, leading to potential system unavailability.
Innovation Solution
Implementing a process in storage devices to differentiate between actively used and inactive logical block addresses (LBAs) and allowing only safe write requests, such as mount/unmount operations and metadata updates, during an out-of-space state, while rejecting unsafe write requests to prevent system unavailability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If in-storage transparent compression is implemented to expand LBA space beyond physical capacity, then storage cost reduction is achieved, but the system may enter out-of-space status when data compressibility falls below expected values
Solution Approach 1:
The patent implements preliminary actions by pre-identifying and marking actively used LBAs before the out-of-space condition occurs. The storage device proactively maintains a record of actively used LBAs and uses this information to make advance decisions about which write requests to permit or reject, preventing the system from reaching a completely full state where no operations can proceed.
Solution Approach 2:
The patent employs feedback mechanisms by continuously monitoring the compression ratio and comparing it against expected values. When the actual compression ratio deviates from expectations, the system receives feedback about the out-of-space condition and adjusts its behavior by selectively permitting or rejecting write requests based on LBA activity status, thereby maintaining system reliability.
2Reliability
If all write requests are rejected during out-of-space state to prevent data loss, then system safety is maintained, but filesystem operations become unavailable
Solution Approach 1:
The patent applies local quality by differentiating between individually safe and unsafe write requests rather than applying a uniform rejection policy. Each write request is evaluated based on the specific LBA activity status, allowing the system to permit operations on inactive LBAs (which are safe) while rejecting operations on active LBAs (which could cause data loss), thereby maintaining both safety and availability locally at the request level.
3Ease of operation
If the storage device permits write requests to inactive LBAs during out-of-space state, then filesystem availability is maintained, but there is risk of overwriting active data
Solution Approach 1:
The patent introduces an intermediary mechanism in the form of an LBA activity status indicator that mediates between the filesystem's write requests and the physical storage medium. This intermediary layer evaluates each write request against the activity status information, acting as a gatekeeper that permits requests to inactive LBAs while blocking requests to active LBAs, thus enabling safe write operations during out-of-space conditions.
Data Source
AI summary
A storage device that provides in-storage transparent compression and implements a process for processing write requests during an out-of-space state. The process includes: receiving a write request from a host involving a set of logical block addresses (LBAs); determining if each of the LBAs in the write request is an actively used LBAs; and in response to determining that each of the LBAs in the write request are actively used LBAs, allowing the write request to be served; and in response to determining that at least one of the LBAs in the write request is not an actively used LBAs, not allowing the write request to be served and returning an error to the host.