Hard Drive Physical Location Mapping in Cluster Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In conventional cluster storage systems, system administrators face difficulties in identifying the physical location of an abnormal hard drive within a storage device, as the firmware and Linux OS only provide logical device names without corresponding slot information, making it challenging to retrieve or replace the faulty drive.
Innovation Solution
A method involving a series of Linux commands (sg_map, sg_ses, sg_vpd) is executed to map logical device names to generic device names and slot numbers, establishing correspondence information that allows for the determination of the physical location of a designated hard drive by linking expander names to logical device names and slot numbers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the firmware of the storage device is used to detect abnormal hard drives, then the detection standard is strict and reliable, but only hard drives that are not able to operate are detected and the physical location information is not provided
Solution Approach 1:
The patent introduces an intermediary mapping relationship between logical device names and physical slot locations. The system maintains a correspondence table that links logical device names (provided by firmware) to physical slot locations, allowing the intermediary mapping mechanism to bridge the gap between reliable firmware detection and the need for physical location information.
Solution Approach 2:
The patent adds another dimension of information by creating a mapping layer between the logical identification dimension (device names) and the physical location dimension (slot numbers). This dimensional transformation allows the system to retrieve physical location information without compromising the reliability of the original firmware detection mechanism.
2Adaptability or versatility
If the Linux OS or third-party computer program is used to detect abnormal hard drives, then additional abnormal conditions can be detected, but only the logical device name is outputted without physical slot information
Solution Approach 1:
The patent performs preliminary action by pre-establishing the mapping relationship between logical device names and physical slot locations before abnormal hard drive detection occurs. The correspondence table is built in advance, so when the Linux OS or third-party program detects an abnormal hard drive, the physical location information can be immediately retrieved without additional operational complexity.
3Adaptability or versatility
If only logical device names are provided for abnormal hard drives, then the detection flexibility is improved, but the system administrator cannot recognize which physical slot the hard drive is installed in
Solution Approach 1:
The patent creates a copied mapping relationship that replicates the connection between logical device names and physical slot locations. Instead of modifying the original detection mechanisms, the system creates a parallel mapping structure that preserves the flexibility of logical device name detection while providing access to physical slot identification information through the copied relationship.
Data Source
AI summary
A method of determining a physical location of a hard drive includes the steps of: executing commands to obtain generic device names of expanders, addresses of hard drives connected to the expanders, slot numbers corresponding to the addresses, logical device names of the hard drives, the address of the hard drives; establishing correspondence information by using the address to link the generic device name of the expander to the logical device name of the hard drive connected to the expander, and to the slot number; and determining, according to the correspondence information, the generic device name of the expander to which a hard drive is connected and the slot number corresponding to the hard drive is installed, so as to locate the hard drive.