Removable Storage Transaction Recovery via Log Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional file systems do not support transactional operations for removable storage devices, leading to unreliability and potential data corruption during failure events, as they lack the capability to recover interrupted transactions upon reconnection to a different host.
Innovation Solution
A removable storage device with an input unit for metadata update operations, a log information storage unit, and a transaction manager that stores log file information before execution and performs recovery operations based on this information, ensuring atomicity and robustness even after failure events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional file systems are used for removable storage devices, then the device can be repeatedly installed and disconnected, but the system lacks transactional operation support leading to data corruption during failure events
Solution Approach 1:
The file system operations are segmented into discrete transactions with clear boundaries. Each transaction is independently managed with its own log file, allowing the system to handle multiple operations atomically. This segmentation enables recovery to be performed on a per-transaction basis rather than requiring system-wide recovery mechanisms.
Solution Approach 2:
Log file information is prepared and stored in advance before the actual metadata update operation is executed. This preliminary action creates a recovery checkpoint that allows the system to rollback to a known good state if a failure occurs during transaction execution, thereby improving reliability without requiring complex post-failure analysis.
2Reliability
If metadata update operations are executed without transactional support, then the operations can be performed quickly, but failure events interrupt execution resulting in non-updated or partially updated metadata
Solution Approach 1:
The log file information containing metadata update operations is prepared and staged before actual execution. This allows the system to validate the entire transaction sequence beforehand and only commit if all operations can complete successfully, preventing partial updates and ensuring data integrity.
Solution Approach 2:
The log file serves as an intermediary between the command received from the host and the actual metadata update on the removable storage device. This intermediary layer allows the system to buffer and manage transaction state, enabling recovery operations to retrieve and re-execute pending updates without direct host intervention.
3Reliability
If the removable storage device stores log file information before execution, then recovery operations can be performed after failure events, but the storage device requires additional storage capacity for log files
Solution Approach 1:
Log file information is discarded after successful transaction execution and is recovered (re-created) when needed for recovery operations. This approach allows the system to maintain reliability capabilities without permanently allocating additional storage space, as the log information is temporary and reused for each transaction cycle.
Solution Approach 2:
The storage allocation for log files is dynamic rather than static. The log file area is allocated as needed for active transactions and can be reused for subsequent transactions, allowing the system to adapt storage usage to actual operational needs rather than reserving fixed capacity.
4Reliability
If transactional operation support is implemented, then atomicity and robustness are ensured across reconnections, but the ease of operation becomes more complex due to additional recovery procedures
Solution Approach 1:
The removable storage device performs self-recovery operations autonomously using its internal transaction manager and stored log file information. When reconnected to a host, the device automatically detects interrupted transactions and recovers them without requiring complex host-side intervention or user action, maintaining operational simplicity despite enhanced robustness.
Solution Approach 2:
The system implements feedback mechanisms where the transaction manager continuously monitors transaction execution state and automatically initiates recovery procedures when failure events are detected. This closed-loop control ensures robustness while keeping the user unaware of the complexity, as recovery operations are triggered and managed automatically based on system state feedback.
Data Source
AI summary
A removable storage device operates in accordance with transactions defined by a connected host. The removable storage device includes an input unit receiving metadata update operation(s) and log file information, a log information storage storing the log file information, and a transaction manager controlling execution of the metadata update operation(s) and execution of a recovery operation for the transaction following a failure event interrupting the transaction in accordance with the stored log file information.