CN109542808B - Method and device for controlling hard disk access - Google Patents
Method and device for controlling hard disk access Download PDFInfo
- Publication number
- CN109542808B CN109542808B CN201811220101.4A CN201811220101A CN109542808B CN 109542808 B CN109542808 B CN 109542808B CN 201811220101 A CN201811220101 A CN 201811220101A CN 109542808 B CN109542808 B CN 109542808B
- Authority
- CN
- China
- Prior art keywords
- hard disk
- storage array
- category identification
- matched
- array
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
- G06F13/1694—Configuration of memory controller to different memory types
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a method and a device for controlling hard disk access, wherein the method is executed by an array controller of a storage array, and the method comprises the following steps: after detecting that a hard disk is connected to the storage array, acquiring the address of a preset reserved area of the hard disk; acquiring parameters of the hard disk from a reserved area of the hard disk indicated by the address; matching the acquired parameters with preset information to obtain a matching result; and determining whether to access the hard disk according to the matching result, which is beneficial to improving the accuracy of accessing the hard disk into the storage array.
Description
Technical Field
The present application relates to the field of storage, and more particularly, to a method and apparatus for controlling access to a hard disk.
Background
The storage array is a large-capacity hard disk group consisting of a plurality of hard disks so as to provide data storage space for users. In general, a new hard disk needs to be accessed to a storage array for the purpose of increasing the storage capacity of the storage array or replacing a hard disk that cannot normally operate in the storage array.
At present, in an access process of a hard disk, a target hard disk to be accessed is connected with an array controller of a storage array, the array controller acquires physical characteristics of the hard disk, such as sector size and medium type, of the target hard disk, and then the array controller determines whether the target hard disk meets the requirements of the storage array on the physical characteristics of the hard disk, if the physical characteristics of the target hard disk meet the requirements of the storage array on the physical characteristics of the hard disk, the array controller allows the target hard disk to be accessed into the storage array, and if the physical characteristics of the target hard disk do not meet the requirements of the storage array on the physical characteristics of the hard disk, the array controller prohibits the target hard disk from being accessed into the storage array.
In the above-described hard disk access mechanism, only the physical characteristics of the hard disk are used as conditions for judging whether the target hard disk can be accessed to the storage array, so that after part of the hard disks are accessed to the storage array, the storage array cannot normally operate due to the fact that the software characteristics of the hard disks cannot meet the requirements of the storage array on the software characteristics of the hard disks, and the probability that the hard disks are successfully accessed to the storage array is reduced. For example, the target hard disk is a Solid State Drive (SSD) that supports a Non-Volatile Memory host controller interface specification (NVMe) version of 1.3, but the array controller supports an NVMe version of 1.2, and at this time, if the physical characteristics of the target hard disk match the physical characteristics of the hard disk supported by the array controller, the array controller allows the target hard disk to access the storage array, but because there is a difference between the reset commands defined in the NVMe specifications of the two versions, the target hard disk cannot recognize the reset command sent by the array controller, and finally the reset of the array controller fails.
Disclosure of Invention
The application provides a method and a device for controlling hard disk access, which are beneficial to improving the accuracy of accessing a hard disk into a storage array.
In a first aspect, a method for controlling access to a hard disk, performed by an array controller of a storage array, includes: after detecting that a hard disk is connected to the storage array, acquiring the address of a preset reserved area of the hard disk; acquiring parameters of the hard disk from a reserved area of the hard disk indicated by the address; matching the acquired parameters with preset information to obtain a matching result; and determining whether to access the hard disk according to the matching result.
The matching result comprises that the acquired parameters are matched with the preset information or the acquired parameters are not matched with the preset information.
The determining whether to access the hard disk according to the matching result may include: when the acquired parameters are matched with the preset information, allowing the hard disk to access the storage array; and when the acquired parameters are not matched with the preset information, the hard disk is forbidden to be accessed into the storage array.
In the embodiment of the application, the array controller can read and judge whether the parameters required by the hard disk can be accessed from the reserved area of the hard disk, and finally judge whether the hard disk can be accessed according to the matching of the read parameters and the preset information. The situation that whether the hard disk can be accessed or not is judged only according to the physical attributes of the hard disk in the prior art, so that the accessed hard disk is not matched or not compatible with the array controller is avoided, and the accuracy of accessing the hard disk into the storage array is improved.
Alternatively, the parameters of the hard disk may be understood as parameters for determining whether the hard disk matches the array controller. For example, the class identification of the hard disk and/or the version of the software product supported by the hard disk. The version of the software product supported by the hard disk is also called the version of the software product of the array controller supported by the hard disk.
In a possible implementation manner, the parameter is a category identifier of the hard disk, the preset information is a white list, the white list records a category identifier of a hard disk that the storage array is allowed to access, and determining whether to access the hard disk according to the matching result includes: when the category identification of the hard disk is matched with the category identification recorded in the white list, allowing the hard disk to access the storage array; and when the category identification of the hard disk is matched with the category identification recorded in the white list, forbidding the hard disk to access the storage array.
In the embodiment of the application, whether the hard disk is accessed is determined according to the white list and the category identification of the hard disk, which is beneficial to improving the accuracy of accessing the hard disk to the storage array.
The category identifier of the hard disk is generated according to the hard disk type of the target hard disk, and the hard disk type may include at least one of the following information: the protocol version to which the hard disk complies, e.g., the Nvme protocol version; performance data of the hard disk, e.g., speed of reading and writing data by the hard disk; physical properties of the hard disk, such as hard disk capacity, hard disk speed, hard disk rotational speed, interface, etc.; the characteristic list supported by the hard disk, for example, the characteristic list is used to indicate whether the hard disk supports the characteristic of the self-check, and the characteristic list may also indicate whether the hard disk supports the characteristic of the multi-stream transmission.
In the embodiment of the application, the class identification of the hard disk is generated according to the type of the hard disk, so that the hard disk can be reasonably classified.
In a possible implementation manner, the preset information further includes a blacklist, where the blacklist records a category identifier of a hard disk to which the storage array is prohibited from accessing, and the determining whether to access the hard disk according to the matching result includes: when the category identification of the hard disk is matched with the category identification recorded in the blacklist, the hard disk is prohibited from accessing the storage array; when the category identification of the hard disk is not matched with the category identification recorded in the blacklist, judging whether the category identification is matched with the category identification in the white list; and when the category identification is matched with the category identification in the white list, allowing the hard disk to access the storage array.
In the embodiment of the application, the category identification of the hard disk is matched with the blacklist and the white list, and whether the hard disk is accessed is determined according to the matching result, so that the accuracy of accessing the hard disk to the storage array is improved.
In a possible implementation manner, the parameters further include versions of product software supported by the hard disk, and the preset information further includes versions of software products running in the storage array, and the method further includes: when the category identification is not matched with the category identification in the white list, reading the version of the product software from a reserved area of the hard disk; judging whether the read version of the product software is matched with the version number of the software product running in the storage array or not; if the read version of the product software is matched with the version number of the software product running in the storage array, allowing the hard disk to access the storage array; and if the read version of the product software is not matched with the version number of the software product running in the storage array, the hard disk is prohibited from accessing the storage array.
In the embodiment of the application, the hard disk which does not belong to the white list can be matched with the version number of the software product running in the storage array according to the version of the software product stored in the hard disk, so that the accuracy of accessing the hard disk to the storage array is improved.
In a possible implementation manner, the parameter includes a version of a software product supported by the hard disk, and the preset information further includes a version of a software product running in the storage array; the determining whether to access the hard disk according to the matching result comprises: when the version number of the software product is matched with the version number of the software product running in the storage array, allowing the hard disk to access the storage array; and when the version number of the software product is not matched with the version number of the software product running in the storage array, the hard disk is prohibited from accessing the storage array.
In the embodiment of the application, the version number of the software product stored in the hard disk can be matched with the version number of the software product operated in the storage array, so that the accuracy of accessing the hard disk to the storage array is improved.
In a possible implementation manner, the determining, according to the matching result, whether to access the hard disk includes: when the category identification of the hard disk is matched with the category identification recorded in the blacklist, the hard disk is prohibited from accessing the storage array; and when the category identification of the hard disk is not matched with the category identification recorded in the blacklist, allowing the hard disk to access the storage array.
In the embodiment of the application, whether the hard disk is accessed is determined according to the blacklist and the category identification of the hard disk, which is beneficial to improving the accuracy of accessing the hard disk to the storage array.
In a second aspect, a hard disk is provided, comprising: the data area is provided for the host to use by the storage array after the hard disk is accessed to the storage array; the reserved area is used for the host not to access after the hard disk is accessed to the storage array; the reserved area stores parameters of the hard disk, and the parameters are used for indicating whether the hard disk is allowed to be accessed to a storage array connected with the hard disk.
In a possible implementation manner, the hard disk further includes a backup reserved area, and the backup reserved area is used for storing backup data of the parameters in the reserved area.
In a possible implementation manner, the reserved area and the backup reserved area are located at two ends of the data area respectively.
In a third aspect, an array controller is provided, the array controller being applied to a storage array, the array controller comprising respective modules for performing the above method.
In a fourth aspect, an array controller is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program from the memory so that the controller executes the method of the above aspects.
In a fifth aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method of the above-mentioned aspects.
It should be noted that, all or part of the computer program code may be stored in the first storage medium, where the first storage medium may be packaged together with the processor or may be packaged separately from the processor, and this is not specifically limited in this embodiment of the present application.
In a sixth aspect, a computer-readable medium is provided, which stores program code, which, when run on a computer, causes the computer to perform the method of the above-mentioned aspects.
Drawings
Fig. 1 is an architecture diagram of a memory array to which the embodiments of the present application are applicable.
Fig. 2 is a flowchart of an access procedure of a conventional hard disk.
Fig. 3 is a schematic diagram of a structure of a hard disk according to an embodiment of the present application.
Fig. 4 is a flowchart of a method for controlling hard disk access according to an embodiment of the present application.
Fig. 5 is a flowchart of a method for controlling hard disk access according to an embodiment of the present application.
Fig. 6 is a flowchart of a method for hard disk access control according to another embodiment of the present application.
Fig. 7 is a flowchart of a method for hard disk access control according to another embodiment of the present application.
FIG. 8 is a schematic diagram of an array controller according to an embodiment of the present application.
FIG. 9 is a schematic diagram of an array controller according to another embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
For ease of understanding, the architecture of a memory array to which the embodiments of the present application are applicable will be described with reference to fig. 1. The storage array 100 shown in FIG. 1 includes an array controller 110 and a plurality of hard disks 120.
A plurality of hard disks 120 to provide storage resources for data.
And an array controller 110 connected to at least some of the plurality of hard disks for managing the hard disks in the storage array connected to the array controller.
If the storage array needs to be accessed to a new target hard disk for the reasons of capacity expansion or hard disk replacement. The conventional access procedure of the target hard disk can be seen in fig. 2. The method shown in fig. 2 includes steps 210 through 240.
210, the array controller obtains physical characteristics of the target hard disk. The physical characteristics of the target hard disk may include a sector size of the target hard disk, a media type of the target hard disk, and the like.
The array controller determines 220 whether the physical characteristics of the target hard disk satisfy the storage array's requirements for the physical characteristics of the hard disk.
For example, the array controller may determine whether the sector size of the target hard disk meets the storage array's requirements for the sector size of the hard disk. For another example, the array controller may determine whether the sector size of the target hard disk meets the storage array's requirements for the sector size of the hard disk.
And 230, if the physical characteristics of the target hard disk meet the requirements of the storage array on the physical characteristics of the hard disk, allowing the target hard disk to access the storage array by the array controller.
And 240, if the physical characteristics of the target hard disk do not meet the requirements of the storage array on the physical characteristics of the hard disk, the array controller forbids the target hard disk to access the storage array.
In the hard disk access mechanism described in fig. 2, the array controller only uses the physical characteristics of the hard disk as a condition for determining whether the target hard disk can access the storage array, and does not consider whether the software characteristics of the target hard disk meet the requirements of the storage array on the software characteristics of the hard disk, or whether the software characteristics of the target hard disk match the software characteristics of the array controller. Thus, the target hard disk may only satisfy the requirements of the storage array for the physical characteristics of the hard disk, but the software characteristics of the target hard disk do not match the software characteristics of the array controller, resulting in the target hard disk not working properly in the storage array.
For example, the target hard disk is a Solid State Drive (SSD) supporting a Non-Volatile Memory host controller interface specification (NVMe) version 1.3, but the array controller supports an NVMe version 1.2, and at this time, if the physical characteristics of the target hard disk meet the requirements of the array controller on the physical characteristics of the hard disk, the array controller allows the target hard disk to access the storage array. However, due to the difference between the reservation commands (reservation commands) defined in the NVMe specifications of the two versions, that is, the meaning of the same reservation command in the two versions is different, the target hard disk cannot correctly recognize the reservation command sent by the array controller.
In an application scenario of the reservation command, if one of the plurality of array controllers of the storage array is abnormal and the abnormal array controller cannot communicate with the other array controllers in the storage array to negotiate a storage space of data, there may be a case where the abnormal array controller and the other array controllers write respective write data to the same storage space, and one storage space cannot store the write data of the two array controllers at the same time. In order to avoid this, the array controller of the storage array needs to send a reservation command to the target hard disk to notify the array controller of the abnormality of the target hard disk, so that the target hard disk can store only the write data sent by the array controller that is operating normally. However, as described above, the NVMe specification supported by the target hard disk is different from the NVMe specification supported by the array controller, and the target hard disk may erroneously determine the array controller that normally operates as the abnormal array controller indicated by the reservation command, and write the write data of the truly abnormal array controller into the storage space, which still causes data storage confusion.
For another example, because the software for implementing the same function of products produced by different manufacturers may not be matched, when the manufacturer of the target hard disk is different from the manufacturer of the array controller, the array controller allows the target hard disk to access the storage array based on a conventional hard disk access mechanism, and does not determine whether the version of the software product of the hard disk matches the version of the software product running in the storage array, which may result in that the target hard disk may not recognize the control command sent by the array controller, and the target hard disk may certainly not work normally in the storage array.
For another example, because the array controllers of different generations implement the same function with different software, the array controller of the new generation may newly support a certain type of hard disk, and the array controller of the old generation may not support the hard disk of the certain type. If the hard disk of the model is connected with the array controller of the old generation by mistake, the array controller of the old generation allows the target hard disk to be accessed into the storage array based on the traditional hard disk access mechanism, but the array controller of the old generation does not support the hard disk of the model, and even if the target hard disk is accessed into the storage array, the target hard disk cannot work normally.
In order to improve the accuracy of accessing a hard disk into a storage array, the application provides a method for controlling the access of the hard disk. For ease of understanding, the structure of the hard disk used in the embodiment of the present application is specifically described with reference to fig. 3.
Fig. 3 shows a schematic diagram of a hard disk according to an embodiment of the present application. The hard disk shown in fig. 3 includes a data area 310 and a reserved area (also called a main reserved area) 320. The data area is provided for the host to use by the storage array after the hard disk is accessed to the storage array; the reserved area is used for the host not to access after the hard disk is accessed to the storage array; the reserved area stores parameters of the hard disk, and the parameters are used for indicating whether the hard disk is allowed to be accessed to a storage array connected with the hard disk.
Optionally, the hard disk may further include a backup reserved area 330. The backup reserved area is used for backing up parameters of the hard disk stored in the main reserved area. The main reserved area 320 and the backup reserved area may be located at both ends of the data area of the target hard disk, respectively.
The main and backup reservations may be made invisible to the host (or user) because they do not generally need to be known by the host due to the parameters of the hard disk stored in the main and backup reservations.
The storage addresses of the main reserved area and the backup reserved area can be informed to a manufacturer of the array controller in advance, so that the manufacturer of the array controller configures the target array controller to read the class identifier of the target hard disk from the storage address of the main reserved area or the backup reserved area.
Based on the above-described structures of the storage array and the hard disk, a flow of a method for controlling access to the hard disk according to an embodiment of the present application is described below with reference to fig. 4.
Fig. 4 is a flowchart of a method for controlling hard disk access according to an embodiment of the present application. The method shown in fig. 4 may be performed by an array controller. For the sake of convenience, the array controller executing the method shown in fig. 4 is hereinafter referred to as a target array controller, and the hard disk to be accessed to the storage array, i.e., the detected hard disk connected to the storage array, is referred to as a target hard disk.
And 410, acquiring the address of a preset reserved area of the target hard disk after detecting that the target hard disk is connected to the storage array.
The target hard disk is connected to the storage array, and it can be understood that the target hard disk is only connected to the storage array, but the storage space of the target hard disk cannot be used as the storage space of the storage array for a while, and the array controller in the storage array cannot manage the storage space of the target hard disk.
And 420, acquiring the parameters of the target hard disk from the reserved area of the target hard disk indicated by the address.
The parameters of the hard disk described above may be understood as parameters for determining whether the hard disk matches the array controller. For example, the class identification of the hard disk and/or the version of the software product supported by the hard disk. The version of the software product supported by the hard disk is also called the version of the software product of the array controller supported by the hard disk.
430, matching the acquired parameters with preset information to obtain a matching result.
The matching result comprises that the acquired parameters are matched with the preset information or the acquired parameters are not matched with the preset information.
And 440, determining whether to access the target hard disk according to the matching result.
The determining whether to access the hard disk according to the matching result may include: when the acquired parameters are matched with the preset information, allowing the hard disk to access the storage array; and when the acquired parameters are not matched with the preset information, the hard disk is forbidden to be accessed into the storage array.
After the target array controller allows the target hard disk to access the storage array, the array controller can control and manage the target hard disk.
In the embodiment of the application, the array controller can read and judge whether the parameters required by the hard disk can be accessed from the reserved area of the hard disk, and finally judge whether the hard disk can be accessed according to the matching of the read parameters and the preset information. The situation that whether the hard disk can be accessed or not is judged only according to the physical attributes of the hard disk in the prior art, so that the accessed hard disk is not matched or not compatible with the array controller is avoided, and the accuracy of accessing the hard disk into the storage array is improved.
The following describes an access procedure of the target hard disk by taking the parameter of the target hard disk as the class identifier of the hard disk in conjunction with fig. 5. Fig. 5 is a flowchart of a method for controlling hard disk access according to another embodiment of the present application. The method shown in fig. 5 includes steps 510 to 550.
510, the target array controller obtains the class identifier of the target hard disk from the target hard disk, where the class identifier of the target hard disk is generated according to the hard disk type of the target hard disk.
The hard disk type may include at least one of the following information: the protocol version to which the hard disk complies, e.g., the Nvme protocol version; performance data of the hard disk, e.g., speed of reading and writing data by the hard disk; physical properties of the hard disk, such as hard disk capacity, hard disk speed, hard disk rotational speed, interface, etc.; the characteristic list supported by the hard disk, for example, the characteristic list is used to indicate whether the hard disk supports the characteristic of the self-check, and the characteristic list may also indicate whether the hard disk supports the characteristic of the multi-stream transmission.
The category identifier of the target hard disk may be stored in a reserved area of the target hard disk as attribute information of the target hard disk. Further, in order to improve the reliability of storing the class identifier of the target hard disk, the class identifier of the target hard disk may be stored in both the main reserved area and the backup reserved area of the target hard disk, so that when the target array controller fails to read the class identifier of the target hard disk stored in the main reserved area, the class identifier of the target hard disk may be read from the backup reserved area.
A tester (e.g., a manufacturer of the array controller) may classify known hard disks according to hard disk types, test different types of hard disks, obtain matching conditions between various types of hard disks and a target array controller, and configure class identifiers for the hard disks of different hard disk types, so that the target array controller identifies the hard disk types of the hard disks.
After obtaining the matching condition between each type of hard disk and the target array controller, the tester can make a white list, wherein the white list records the category identification of the hard disk which can be matched with the target array controller in each type of hard disk to be tested, so as to be used in the control flow of hard disk access in the following.
Correspondingly, after obtaining the matching condition between each type of hard disk and the target array controller, the tester can also make a blacklist, and the blacklist records the category identification of the hard disk which cannot be matched with the target array controller in each type of hard disk to be tested, so that the blacklist can be used in the control flow of hard disk access in the following.
The target array controller determines whether the class identifier of the target hard disk belongs to a white list 520 and/or the target array controller determines whether the class identifier of the target hard disk belongs to a black list.
521, if the class identifier of the target hard disk belongs to the blacklist, the target array controller executes step 550, that is, the target hard disk is prohibited from accessing the storage array, and the hard disk type corresponding to the class identifier recorded in the blacklist is not matched with the target array controller.
522, if the class identifier of the target hard disk belongs to the white list, the target array controller executes step 540, that is, the target hard disk is allowed to access the storage array, and the hard disk type corresponding to the class identifier recorded in the white list is matched with the target array controller.
It should be noted that, in the access control flow of the hard disk, only the white list may be used, or only the black list may be used, or the black list and the white list may be used in combination.
If only the white list is used in the access control process of the hard disk, the hard disk corresponding to the category identifier that does not belong to the white list may be determined by the array controller according to the hard disk access mechanism shown in fig. 2 whether the hard disk can access the storage array. Or, the array controller may also directly prohibit the hard disk corresponding to the category identifier that does not belong to the white list from accessing the storage array.
If only the blacklist is used in the access control process of the hard disk, the hard disk corresponding to the category identifier that does not belong to the blacklist may be determined by the array controller according to the hard disk access mechanism shown in fig. 2 whether the hard disk can be accessed to the storage array. Or the array controller can directly allow the hard disk corresponding to the category identification which does not belong to the blacklist to access the storage array.
If the black list and the white list are used in combination, the target array controller may first determine whether the category identifier of the target hard disk belongs to the black list, and if the category identifier of the target hard disk does not belong to the black list (see 523), the target array controller may then determine whether the category identifier of the target hard disk belongs to the white list. If the category identification of the target hard disk belongs to the white list (see 522), step 540 is executed. If the category identifier of the target hard disk does not belong to the white list, the array controller described above may determine whether the hard disk may access the storage array according to the hard disk access mechanism shown in fig. 2. Or, the array controller may also directly prohibit the hard disk corresponding to the category identifier that does not belong to the white list from accessing the storage array.
The white list and/or black list may be stored in the target array controller in the form of a configuration file. Of course, the black list and/or white list stored in the array controller may also be updated to further improve the accuracy of accessing the hard disk to the storage array.
Optionally, the blacklist (or "hard disk class identifier blacklist") may be used in combination with a new hard disk class identifier blacklist and/or a deleted hard disk class identifier blacklist. And adding a hard disk class identification blacklist for supplementing the blacklist. For example, the blacklist obtained by the test is not accurate, and a hard disk which cannot be matched with the target array controller is found subsequently, at this time, since the blacklist is configured completely, in order to simplify the configuration process, the category identifier of the hard disk which cannot be matched with the target array controller and is found subsequently may be added to the newly added hard disk blacklist. And deleting the hard disk class identifier blacklist to remove the class identifier from the blacklist. For example, a black list obtained through testing is inaccurate due to errors in the testing process, and it is subsequently found that a hard disk corresponding to a hard disk class identifier in the black list can be matched with a target array controller.
And if the target array controller is simultaneously provided with a blacklist, a newly added hard disk class identification blacklist and a deleted hard disk class identification blacklist, the class identification of the target hard disk belongs to the blacklist or the newly added hard disk class identification blacklist, and the class identification of the target hard disk does not belong to the deleted hard disk class identification blacklist, the target array controller forbids the target hard disk to be accessed into the storage array. And if the category identification of the target hard disk belongs to the blacklist or the blacklist of the newly added hard disk category identification and the category identification of the target hard disk belongs to the blacklist of the deleted hard disk category identification, the target array controller allows the target hard disk to access the storage array.
Optionally, the white list (or "hard disk class identifier white list") may be used in combination with a new hard disk class identifier white list and/or a delete class identifier white list. And adding a hard disk class identification white list for supplementing the white list. For example, the white list obtained by the test is not accurate, and a hard disk that can be matched with the target array controller is found subsequently, at this time, since the white list is already configured, in order to simplify the configuration process, the category identifier of the hard disk that can be matched with the target array controller and is found subsequently may be added to the newly added hard disk white list. Deleting the white list of category identifications is used to remove the category identifications from the white list. For example, a white list obtained through testing is inaccurate due to errors in the testing process, and it is subsequently found that the hard disk corresponding to the hard disk class identifier in the white list is not matched with the target array controller.
And if the target array controller is simultaneously provided with a white list, a newly added hard disk class identification white list and a deleted hard disk class identification white list, the class identification of the target hard disk belongs to the white list or the newly added hard disk class identification white list, and the class identification of the target hard disk does not belong to the deleted hard disk class identification white list, the target array controller allows the target hard disk to be accessed into the storage array. And if the category identification of the target hard disk belongs to the white list or the newly added hard disk category identification white list and the category identification of the target hard disk belongs to the deleted hard disk category identification white list, the target array controller forbids the target hard disk to be accessed into the storage array.
The syntax listed below is an implementation of a configuration file for an array controller of an embodiment of the present application. The configuration file of the array controller includes a product version number (product version) of the array controller, a white list of hard Disk class identifiers (Disk ID white list), a newly added white list of hard Disk class identifiers (Disk ID white add list), a deleted white list of hard Disk class identifiers (Disk ID white del list), a black list of hard Disk class identifiers (Disk ID black list), a newly added black list of hard Disk class identifiers (Disk ID black add list), and a deleted black list of hard Disk class identifiers (Disk ID black del list).
[DISK_ID]
DiskInCheckSwitch＝on
ProductVersion＝VXXXRXXXCXX
Disk ID WhiteList0＝XXXXXXXX,XXXXXXXX
Disk ID WhiteAddList0＝XXXXXXXX,XXXXXXXX
Disk ID WhiteDelList0＝XXXXXXXX,XXXXXXXX
Disk ID BlackList0＝XXXXXXXX,XXXXXXXX
Disk ID BlackAddList0＝XXXXXXXX,XXXXXXXX
Disk ID BlackDelList0＝XXXXXXXX,XXXXXXXX
It should be noted that the hard disk category identification white list, the hard disk category identification black list, the newly added hard disk category identification white list, the deleted hard disk category identification white list, the newly added hard disk category identification black list, and the deleted hard disk category identification black list may be used in combination with each other, and the specific combination manner is not specifically limited in the embodiment of the present application. For example, only a hard disk blacklist and a hard disk whitelist may be included in the configuration file for the array controller. As another example, only a hard disk blacklist and a newly added hard disk blacklist may be included in the configuration file for the array controller. As another example, only a hard disk white list and a newly added hard disk white list may be included in the configuration file for the array controller.
The following describes an access procedure of the target hard disk with reference to fig. 6, taking the parameter of the target hard disk as the version of the software product supported by the target hard disk as an example. Fig. 6 is a flowchart of a method for controlling hard disk access according to another embodiment of the present application. The method shown in fig. 6 includes steps 610 through 640.
The target array controller retrieves 610 from the target hard disk the version of the software product running in the storage array that matches the target hard disk, e.g., the version of the software product of the array controller.
The version of the software product running in the storage array matched with the target hard disk may be stored in the target hard disk, and the storage manner may refer to the storage manner of the class identifier of the target hard disk described above, and for brevity, no further description is given here.
In addition, if there are multiple types of versions of software products running in the storage array that match the target hard disk, the versions of the software products running in the storage array that match the target hard disk may be stored in the target hard disk in a list.
A tester (e.g., a manufacturer of hard disks) may test for a match of the hard disks to known versions of each array controller and store the version of the software product running in the storage array that matches the hard disk in the hard disk.
Optionally, the version of the software product running in the storage array may be embodied by the version number of the software product running in the storage array. I.e., the version number of the software product running in the storage array, is used to indicate the version of the software product running in the storage array.
The target array controller determines 620 if the version of the software product running in the target storage array is the same as the version of the software product running in the storage array that the target hard disk matches.
The target storage array is the storage array where the target array controller is located.
621, if the version of the software product running in the target storage array is the same as the version of the software product running in the storage array, the target array controller executes step 630, i.e. the target hard disk is allowed to access the storage array.
The version of the software product of the target array controller is the same as the version of the software product of the array controller, which indicates that the version of the software product of the target array controller matches the version of the target hard disk.
If the version of the software product running in the target storage array is not the same as the version of the software product running in the storage array 622, the target array controller proceeds to step 640, where the target hard disk is prohibited from accessing the storage array.
The version of the software product running in the target storage array is different from the version of the software product running in the storage array, which indicates that the version of the software product running in the target storage array does not match with the version of the target hard disk.
It should be noted that the above-described method for controlling access to a hard disk based on a version of a software product running in a storage array matching a target hard disk stored in the target hard disk, which is described in fig. 6, may also be used in combination with the method for controlling access to a target hard disk based on a white list and a black list, which is described in fig. 5, and is described below in conjunction with fig. 7. It should be understood that the related description of the method steps shown in fig. 7 can refer to the description above in connection with fig. 5 and 6, and the description is omitted here for brevity.
Fig. 7 is a flowchart of a method for controlling hard disk access according to another embodiment of the present application. The method shown in fig. 7 includes steps 710 to 760. It should be understood that the method illustrated in FIG. 7 may be performed by the target array controller described above.
And 710, acquiring the class identifier of the target hard disk and the version of the software product running in the storage array matched with the target hard disk from the target hard disk.
It should be noted that the software product version and the category identifier may be obtained from the target hard disk by the target array controller at the same time, the target array controller may also obtain the category identifier of the target hard disk first, and then obtain from the target hard disk when the version of the software product running in the storage array matched with the target hard disk needs to be used, or the target array controller may also obtain the version of the software product running in the storage array matched with the target hard disk first, and then obtain from the target hard disk when the category identifier of the target hard disk needs to be used, which is not limited in this embodiment of the present application.
And 720, determining whether the category identification of the target hard disk belongs to a blacklist.
721, if the class id of the target hard disk belongs to the blacklist, step 750 is executed, i.e. the target hard disk is prohibited from accessing the storage array.
722, if the class id of the target hard disk does not belong to the blacklist, go to step 730.
730, it is determined whether the class identifier of the target hard disk belongs to the white list.
731, if the class id of the target hard disk belongs to the white list, step 760 is executed, i.e. the target hard disk is allowed to access the storage array.
732, if the class id of the target hard disk does not belong to the white list, then go to step 740.
740, it is determined whether the version of the software product running in the target storage array is the same as the version of the software product running in the storage array that matches the target hard disk.
741, if the version of the software product running in the target storage array is the same as the version of the software product running in the storage array matching the target hard disk, then step 760 is executed, i.e. the target hard disk is allowed to access the storage array.
742, if the version of the software product running in the target storage array is not the same as the version of the software product running in the storage array matched with the target hard disk, step 750 is executed, i.e., the target hard disk is prohibited from accessing the storage array.
It should be noted that the method shown in fig. 6 may also be used only in conjunction with the blacklist, that is, the hard disk is controlled to access the storage array based on the version of the software product running in the storage array matched with the target hard disk and the blacklist. Specifically, if the category identifier of the target hard disk belongs to the blacklist, the target array controller prohibits the target hard disk from accessing the storage array. If the category identifier of the target hard disk does not belong to the blacklist, the target array controller may determine whether the target hard disk can access the storage array according to the method steps shown in fig. 6.
On the other hand, the method shown in fig. 6 may also be used only in conjunction with a white list, controlling access of the hard disk to the storage array based on the version of the software product running in the storage array that matches the target hard disk and the white list. Specifically, if the class identifier of the target hard disk belongs to the white list, the target array controller allows the target hard disk to access the storage array. If the category identifier of the target hard disk does not belong to the white list, the target array controller may determine whether the target hard disk can access the storage array according to the method steps shown in fig. 6.
The method for controlling hard disk access according to the embodiment of the present application is described in detail above with reference to fig. 1 to 7, and the apparatus according to the embodiment of the present application is described in detail below with reference to fig. 8 and 9. It should be noted that the apparatuses shown in fig. 8 and fig. 9 can implement the steps in the above method, and are not described herein again for brevity.
FIG. 8 is a schematic diagram of an array controller according to an embodiment of the present application. The array controller 800 shown in FIG. 8 may implement the steps in FIG. 3, FIG. 4, FIG. 6, and FIG. 7. The array controller 800 shown in fig. 8 includes an acquisition unit 810, and a processing unit 820.
An obtaining unit 810, configured to obtain an address of a reserved area of a preset hard disk after detecting that the hard disk is connected to the storage array;
the obtaining unit 810 is further configured to obtain a parameter of the hard disk from a reserved area of the hard disk indicated by the address;
the processing unit 820 is configured to match the parameter obtained by the obtaining unit with preset information to obtain a matching result;
the processing unit 820 is further configured to determine whether to access the hard disk according to the matching result.
Optionally, the parameter is a category identifier of the hard disk, the preset information is a white list, the white list records a category identifier of a hard disk allowed to be accessed by the storage array, and the processing unit is specifically configured to: when the category identification of the hard disk is matched with the category identification recorded in the white list, allowing the hard disk to access the storage array; and when the category identification of the hard disk is matched with the category identification recorded in the white list, forbidding the hard disk to access the storage array.
Optionally, the preset information further includes a blacklist, where the blacklist records a category identifier of a hard disk to which the storage array is prohibited from accessing, and the processing unit is specifically configured to: when the category identification of the hard disk is matched with the category identification recorded in the blacklist, the hard disk is prohibited from accessing the storage array; when the category identification of the hard disk is not matched with the category identification recorded in the blacklist, judging whether the category identification is matched with the category identification in the white list; and when the category identification is matched with the category identification in the white list, allowing the hard disk to access the storage array.
Optionally, the parameter further includes a version of a software product supported by the hard disk, the preset information further includes a version of a software product running in the storage array, and the obtaining unit is further configured to: when the category identification is not matched with the category identification in the white list, reading the version of the software product from a reserved area of the hard disk; the processing unit is further to: judging whether the read version of the software product is matched with the version number of the software product running in the storage array; the processing unit is further to: if the read version of the software product is matched with the version number of the software product running in the storage array, allowing the hard disk to access the storage array; the processing unit is further to: and if the read version of the software product is not matched with the version number of the software product running in the storage array, the hard disk is prohibited from accessing the storage array.
Optionally, the parameter includes a version of a software product supported by the hard disk, the preset information further includes a version of a software product of the controller, and the processing unit is further configured to: when the version number of the software product is matched with the version number of the software product running in the storage array, allowing the hard disk to access the storage array; and when the version number of the software product is not matched with the version number of the software product running in the storage array, the hard disk is prohibited from accessing the storage array.
In an alternative embodiment, the obtaining unit 810 and the processing unit 820 may be a processor 920, and the array controller may further include an input/output interface 930 and a memory 910, as shown in fig. 9.
FIG. 9 is a schematic block diagram of an array controller according to another embodiment of the present application. The array controller 900 shown in fig. 9 may include: memory 910, processor 920, and input/output interface 930. The memory 910, the processor 920 and the input/output interface 930 are connected through a communication connection, the memory 910 is configured to store program instructions, the processor 920 is configured to execute the program instructions stored in the memory 920 to control the input/output interface 930 to receive input data and information and output data such as operation results, and the data and information received by the input/output interface 930 may be stored in the hard disk 940.
It should be understood that, in the embodiment of the present application, the processor 920 may adopt a general-purpose Central Processing Unit (CPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits, for executing related programs to implement the technical solutions provided in the embodiments of the present application.
The memory 910 may include both read-only memory and random-access memory, and provides instructions and data to the processor 920. A portion of processor 920 may also include non-volatile random access memory. For example, the processor 920 may also store information of device types.
In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 920. The method disclosed in the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 910, and the processor 920 reads the information in the memory 910, and performs the steps of the above method in combination with the hardware thereof. To avoid repetition, it is not described in detail here.
It should be understood that in the embodiments of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should be further understood that in this embodiment of the application, the hard disk (HDD) may be a Solid State Disk (SSD), a mechanical hard disk (mechanical hard disk), a hybrid hard disk (SSHD), and the like, as one of the storage media of the host site and the standby site.
It should be understood that in the embodiments of the present application, the transceiver is also called a communication interface, and the communication between the communication device (e.g., a terminal device or a network device) and other devices or a communication network is realized by using a transceiver device such as, but not limited to, a transceiver.
It will also be appreciated that in embodiments of the present application, the memory may comprise both read-only memory and random access memory, and may provide instructions and data to the processor. A portion of the processor may also include non-volatile random access memory. For example, the processor may also store information of the device type.
It should be understood that in the embodiment of the present application, "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.
It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be read by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Versatile Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (11)
1. A method of controlling access to a hard disk, performed by an array controller of a storage array, the method comprising:
after detecting that a hard disk is connected to the storage array, acquiring the address of a preset reserved area of the hard disk;
acquiring the version of the software product supported by the hard disk from the reserved area of the hard disk indicated by the address;
matching the obtained version of the software product supported by the hard disk with the version of the software product running in the storage array to obtain a matching result;
determining whether to access the hard disk according to the matching result, wherein when the version of the software product is matched with the version number of the software product running in the storage array, the hard disk is allowed to access the storage array;
and when the version number of the software product is not matched with the version number of the software product running in the storage array, the hard disk is prohibited from accessing the storage array.
2. The method of claim 1, wherein the reserved area further stores a class identifier of the hard disk, the array controller stores a white list recording class identifiers of hard disks allowed to be accessed by the storage array,
the obtaining the parameters of the hard disk from the reserved area of the hard disk indicated by the address comprises:
and when the category identification is not matched with the category identification in the white list, reading the version of the software product of the storage array supported by the hard disk from the reserved area.
3. The method of claim 2, wherein prior to said obtaining the version of the software product supported by the hard disk from the reserved area of the hard disk indicated by the address, the method further comprises:
acquiring parameters of the hard disk from the reserved area, wherein the parameters of the hard disk comprise a category identification of the hard disk;
judging whether the acquired parameters are matched with preset information or not, wherein the preset information comprises the white list;
when the category identification of the hard disk is matched with the category identification recorded in the white list, allowing the hard disk to access the storage array;
and when the category identification of the hard disk is not matched with the category identification recorded in the white list, forbidding the hard disk to access the storage array.
4. The method of claim 3, wherein the preset information further includes a blacklist, where the blacklist records a category identifier of a hard disk to which the storage array is prohibited from accessing;
the method further comprises the following steps:
when the category identification of the hard disk is matched with the category identification recorded in the blacklist, the hard disk is prohibited from accessing the storage array;
when the category identification of the hard disk is not matched with the category identification recorded in the blacklist, judging whether the category identification is matched with the category identification in the white list;
and when the category identification is matched with the category identification in the white list, allowing the hard disk to access the storage array.
5. A hard disk, comprising:
the data area is provided for the host to use by the storage array after the hard disk is accessed to the storage array;
the reserved area is used for the host not to access after the hard disk is accessed to the storage array;
the reserved area stores parameters of the hard disk, the parameters are used for indicating whether the hard disk is allowed to be accessed to a storage array connected with the hard disk, and the parameters comprise versions of software products supported by the hard disk.
6. The hard disk of claim 5, wherein the hard disk further comprises a backup reservation for storing backup data for the parameters in the reservation.
7. The hard disk of claim 6, wherein the reserved area and the backup reserved area are located at both ends of the data area, respectively.
8. An array controller for use with a storage array, comprising:
the acquisition unit is used for acquiring the address of a preset reserved area of the hard disk after detecting that the hard disk is connected to the storage array;
the obtaining unit is further configured to obtain, from the reserved area of the hard disk indicated by the address, an version of a software product supported by the hard disk;
the processing unit is used for matching the version of the software product supported by the hard disk acquired by the acquisition unit with the version of the software product running in the storage array to obtain a matching result;
the processing unit is further configured to determine whether to access the hard disk according to the matching result, wherein when the version of the software product matches the version number of the software product running in the storage array, the hard disk is allowed to access the storage array;
and when the version number of the software product is not matched with the version number of the software product running in the storage array, the hard disk is prohibited from accessing the storage array.
9. The array controller of claim 8, wherein the reserved area further stores a class identifier of the hard disk, the array controller stores a white list recording class identifiers of hard disks allowed to be accessed by the storage array,
the obtaining unit is further configured to:
and when the category identification is not matched with the category identification in the white list, reading the version of the software product of the storage array supported by the hard disk from the reserved area.
10. The array controller of claim 9,
the acquiring unit is further configured to acquire parameters of the hard disk from the reserved area, where the parameters of the hard disk include a category identifier of the hard disk;
the processing unit is specifically configured to:
judging whether the acquired parameters are matched with preset information or not, wherein the preset information comprises the white list;
when the category identification of the hard disk is matched with the category identification recorded in the white list, allowing the hard disk to access the storage array;
and when the category identification of the hard disk is not matched with the category identification recorded in the white list, forbidding the hard disk to access the storage array.
11. The array controller of claim 10, wherein the predetermined information further includes a blacklist of class identifications of hard disks to which the storage array is prohibited from accessing,
the processing unit is specifically configured to:
when the category identification of the hard disk is matched with the category identification recorded in the blacklist, the hard disk is prohibited from accessing the storage array;
when the category identification of the hard disk is not matched with the category identification recorded in the blacklist, judging whether the category identification is matched with the category identification in the white list;
and when the category identification is matched with the category identification in the white list, allowing the hard disk to access the storage array.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811220101.4A CN109542808B (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
| CN202011467433.XA CN112631965A (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811220101.4A CN109542808B (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011467433.XA Division CN112631965A (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109542808A CN109542808A (en) | 2019-03-29 |
| CN109542808B true CN109542808B (en) | 2020-12-18 |
Family
ID=65844157
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811220101.4A Active CN109542808B (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
| CN202011467433.XA Pending CN112631965A (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011467433.XA Pending CN112631965A (en) | 2018-10-19 | 2018-10-19 | Method and device for controlling hard disk access |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN109542808B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110989928B (en) * | 2019-11-20 | 2020-10-09 | 北京连山科技股份有限公司 | Management method and management device for storage unit in RAID0 |
| CN115048681B (en) * | 2022-05-10 | 2024-02-20 | 黄建邦 | Data security protection method and device, target equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776391A (en) * | 2016-12-13 | 2017-05-31 | 成都信息工程大学 | The control method and device of a kind of NAND Flash controllers |
| CN107273245A (en) * | 2017-06-12 | 2017-10-20 | 英业达科技有限公司 | Arithmetic unit and operation method |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100388678C (en) * | 2004-11-29 | 2008-05-14 | 中兴通讯股份有限公司 | Automatic obtaining method for telecommunication trausmission systen unit soft and hard ware version |
| WO2008041950A2 (en) * | 2006-10-04 | 2008-04-10 | Trek 2000 International Ltd. | Method, apparatus and system for authentication of external storage devices |
| US20090164744A1 (en) * | 2007-12-24 | 2009-06-25 | Unity Semiconductor Corporation | Memory access protection |
| US9575853B2 (en) * | 2014-12-12 | 2017-02-21 | Intel Corporation | Accelerated data recovery in a storage system |
| CN105005722A (en) * | 2015-06-26 | 2015-10-28 | 北京北信源软件股份有限公司 | Access control method and apparatus for mobile storage device |
| CN106250758A (en) * | 2016-07-06 | 2016-12-21 | 北京元心科技有限公司 | A kind of storage device connection control method and system |
| CN106815154A (en) * | 2017-01-16 | 2017-06-09 | 联想(北京)有限公司 | A kind of method and device of the mark for recognizing hard disk |
| US10394654B2 (en) * | 2017-03-31 | 2019-08-27 | Intel Corporation | Method and apparatus for hybrid firmware boot |
| CN108197457B (en) * | 2017-12-20 | 2021-04-06 | 新华三技术有限公司 | Hard disk security control method and device |
-
2018
- 2018-10-19 CN CN201811220101.4A patent/CN109542808B/en active Active
- 2018-10-19 CN CN202011467433.XA patent/CN112631965A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776391A (en) * | 2016-12-13 | 2017-05-31 | 成都信息工程大学 | The control method and device of a kind of NAND Flash controllers |
| CN107273245A (en) * | 2017-06-12 | 2017-10-20 | 英业达科技有限公司 | Arithmetic unit and operation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112631965A (en) | 2021-04-09 |
| CN109542808A (en) | 2019-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109462446B (en) | Radio frequency calibration method and device, electronic device and computer readable storage medium | |
| US8954805B2 (en) | Computer booting method and computer system | |
| US8423848B2 (en) | Server and method for testing inter-integrated circuit devices | |
| CN110618903A (en) | Electronic equipment testing method and device | |
| US20170286097A1 (en) | Method to prevent operating system digital product key activation failures | |
| US20120117367A1 (en) | Electronic apparatus and booting method thereof | |
| CN109542808B (en) | Method and device for controlling hard disk access | |
| US8214692B1 (en) | System and method for enforcing a third-party factory test | |
| CN112100027A (en) | Server maintenance method, device, equipment and machine readable storage medium | |
| CN108898012B (en) | Method and apparatus for detecting illegal program | |
| US10558513B2 (en) | System management apparatus and system management method | |
| CN111694684B (en) | Abnormal construction method and device of storage device, electronic device and storage medium | |
| US10620867B2 (en) | System and method for performing wear leveling at a non-volatile firmware memory | |
| KR20130096033A (en) | Computer system and siglature verification server | |
| US7475164B2 (en) | Apparatus, system, and method for automated device configuration and testing | |
| US9311195B2 (en) | SCSI reservation status information on a SAN disk | |
| US8738816B2 (en) | Management of detected devices coupled to a host machine | |
| US10838785B2 (en) | BIOS to OS event communication | |
| CN116225802A (en) | Fault testing method and device and computing equipment | |
| US20210141544A1 (en) | Method for processing data block and controller | |
| CN113190445A (en) | Interface test method, interface test device and interface test system | |
| CN117608618B (en) | Server firmware upgrading method and device, storage medium and electronic equipment | |
| US20230409729A1 (en) | Mandatory access control (mac) method and related device | |
| US20240104041A1 (en) | Method for starting computing device, computing device, and program product | |
| CN117667252A (en) | Method, system, equipment and storage medium for opening system-guided watchdog |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |