Fastboot Procedure for Data Storage Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data storage systems experience prolonged boot times, rendering them unavailable for I/O requests during the initial boot process, which can take several minutes and involves unnecessary activities even during simple reboots if the system state remains intact.
Innovation Solution
Implementing a fastboot procedure that selectively performs only critical activities instead of a full-boot procedure, utilizing a fastboot flag to determine the necessary boot process, thereby reducing the time to return to normal operating mode by skipping avoidable tasks such as firmware version comparisons and power-on self-test checks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full-boot procedure is performed to ensure system integrity and reliability, then the system reliability is improved, but the boot time increases significantly causing data unavailability
Solution Approach 1:
The boot procedure is segmented into two distinct modes: full-boot procedure for initial booting to ensure system integrity, and fastboot procedure for subsequent reboots to reduce boot time. The system divides the boot process based on the boot type (cold boot vs. warm boot), performing comprehensive checks only when necessary and skipping redundant activities during warm reboots when system integrity is already established.
2Reliability
If comprehensive boot activities including firmware version comparison and partition validation are performed, then the system reliability is improved, but the productivity during reboot operations deteriorates
Solution Approach 1:
The system applies partial action by performing only the necessary subset of boot activities based on the boot type. During warm boots, the system performs partial boot activities (skipping firmware version comparison, partition validation, and other comprehensive checks) since the system is already in a known good state. This selective execution of boot activities maintains reliability while significantly improving reboot speed and productivity.
3Measurement precision
If the data storage system performs all booting activities including checking for power-on self-test errors and validating partitions, then the measurement precision of system state verification is improved, but the time required to reach normal operating mode increases
Solution Approach 1:
The system dynamically adjusts the boot procedure based on the current system state and boot type. The boot process is not static but adapts its level of verification: comprehensive verification (full-boot) is performed when transitioning from an off state, while minimal verification (fastboot) is performed during warm reboots. This dynamic approach maintains measurement precision when needed while reducing verification overhead when the system state is already known to be valid.
Data Source
AI summary
A technique involves performing, in a data storage system, a full-boot procedure which includes a set of critical boot activities and a set of avoidable boot activities. The technique further involves providing, in response to completion of the full-boot procedure, a fastboot notification indicating to the data storage system that a fastboot procedure is to be performed in response to a warm boot event. The technique further involves placing, after providing the fastboot notification, the data storage system into a normal operating mode in which the data storage system performs data storage operations in response to data storage requests from a set of external host computers. Such operation enables the data storage system to subsequently perform a fastboot procedure that avoids the set of avoidable boot activities in response to the next warm boot event.