Drive Status Table for Self-Encrypting Storage Atomicity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Self-encrypting storage resources face indeterminate states due to drive events like power loss or reset, which can lead to incomplete configuration operations, lack of status visibility for sub-steps, and inability to guarantee atomicity of multi-step commands, resulting in potential data integrity issues and session loss.
Innovation Solution
Implementing a drive status table in a persistent storage area to track the completion status of commands, allowing the host system processor to access and take remedial actions in case of drive events, ensuring visibility into command status and integrity of address ranges.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multi-step commands are used to reconfigure self-encrypting drives, then configuration capability is improved, but atomicity cannot be guaranteed due to drive events like power loss or reset
Solution Approach 1:
The patent applies preliminary action by creating a status table entry before executing multi-step commands. This entry records the command details and initial state, allowing the system to track progress and recover if a drive event occurs. The status table is prepared in advance with all necessary tracking structures, enabling atomicity verification even when commands span multiple steps and may be interrupted by power loss or reset events.
2Loss of information
If drive status table is implemented in persistent storage, then visibility into command status is improved, but device complexity increases
Solution Approach 1:
The patent applies copying by creating a status table that copies and tracks command information in persistent storage. Rather than modifying the original command structure or adding complex state machines, the system creates a parallel status representation that mirrors command progress. This copy-based approach provides complete visibility into command status without fundamentally altering the command execution path, thereby limiting the increase in device complexity.
3Ease of operation
If session-based commands are used, then ease of operation is improved, but session state is lost during drive events
Solution Approach 1:
The patent introduces an intermediary status table that mediates between session-based commands and persistent state requirements. The status table acts as a bridge, storing command information and progress independently of session lifecycle. When drive events occur and sessions are lost, this intermediary structure preserves the necessary state information, allowing the system to recover command context without requiring sessions to be inherently persistent.
Data Source
AI summary
An information handling system may include a host system processor and a storage resource communicatively coupled to the host system processor. The storage resource may be configured to, responsive to receiving a command from the host system processor relating an address range of the storage resource, create an entry in a drive status table stored in a persistent storage area of the storage resource, the entry setting forth information indicative of the address and a completion status of the command and update a status of the address range in the drive status table as steps of the command are completed by the storage resource, such that, if a drive event occurs preventing full completion of the command, the host system processor may access the drive status table to determine a status of the command, and take a remedial action based on the status of the command.

