WO2018059495A1

WO2018059495A1 - Solid state drive (ssd), storage device, and data storage method

Info

Publication number: WO2018059495A1
Application number: PCT/CN2017/104017
Authority: WO
Inventors: 江维; 张箭; 孙睿
Original assignee: 华为技术有限公司
Priority date: 2016-09-30
Filing date: 2017-09-28
Publication date: 2018-04-05
Also published as: CN107885457A; CN107885457B

Abstract

A solid state drive (SSD), a storage device, and a data storage method. The SSD comprises: a drive body, provided with a connector configured to connect to a redundant array of independent disks, and at least one memory module socket; a controller, configured in the drive body, the controller being electrically connected to the connector and the memory module socket, respectively; at least one memory module, detachably inserted into the at least one memory module socket, each of the at least one memory module being provided with at least two flash packages, which are used for storing data. The controller is used for reading and writing, by means of each memory module socket, data in the flash packages on the memory module connected to the memory module socket. The SSD in the present invention can be easily detached and replaced.

Description

Solid state hard disk SSD, storage device and data storage method

Technical field

The present invention relates to the field of storage technologies, and in particular, to a solid state hard disk SSD, a storage device, and a data storage method.

Background technique

Solid State Drives (English: Solid State Drives, SSD for short) are an important storage component of storage arrays. In the existing SSD production mode, SSD flash granules, controllers and other auxiliary components, such as capacitors, are soldered on a printed circuit board (English: Printed Circuit Board, PCB for short). The PCB is then packaged through two cover plates to form a complete SSD.

Therefore, in the existing SSD, since the flash memory particles and the controller are soldered on the same PCB, and any one of the flash memory particles or the controller is damaged, the SSD is invalidated, and the entire PCB needs to be removed for replacement, so the disassembly and replacement are complicated, and The cost of replacing the entire PCB is also high.

Summary of the invention

The present invention provides a solid state hard disk SSD, a storage device, and a data storage method for solving the technical problems of disassembly and replacement of the structure of the SSD in the prior art.

In a first aspect, an embodiment of the present invention provides a solid state hard disk SSD, including:

a disk body, the disk body is provided with a connection port for connecting with the disk array, at least one memory bar interface; a controller is disposed in the disk body, and the controller is respectively connected to the connection port and the storage The strip interface is electrically connected; at least one memory strip is pluggably inserted into the at least one memory strip interface, and at least two flash memory particles are disposed on each of the at least one memory strip, the flash memory The granules are used to store data, and the controller is configured to read and write data in the flash granules on the storage strips of each of the memory strip interface connections through each of the memory strip interfaces. By designing the memory strip in a pluggable form, it is easy to replace the memory stick without having to open the cover and replace the entire PCB as in the prior art, thereby also reducing the cost.

In one possible design, the SSD further includes at least two external cache partitions, each of the external cache partitions corresponding to one flash granule, each flash granule having an internal cache area; and the controller for receiving a data write request Obtaining, from the data write request, a target flash granule storing the data to be stored, determining a target external cache partition corresponding to the target flash granule, and storing the to-be-stored data in the target external cache partition; The data to be stored is stored from the target external cache partition to the target flash granule. Through the external cache partition, the data to be stored of each flash granule that is delivered to a storage strip is cached, and then stored separately to each target flash granule, and the data to be stored in the external cache partition is stored to each target flash memory. The particles can be performed in parallel, which not only saves the controller's scheduling processing, but also improves the processing speed and performance of the data write request.

In a possible design, the SSD further includes at least two backup external cache partitions, the at least two backup external cache partitions are in one-to-one correspondence with the at least two external cache partitions, and the controller is further configured to determine Backing up an external cache partition corresponding to the target external cache partition, and storing the to-be-stored data in the backup external cache partition; storing the to-be-stored data from the target external cache partition to the target flash granule Upon failure, the data to be stored is stored from the backup external cache partition to the target flash granule. By external caching The partition design backs up the external cache partition, and when the storage of the to-be-stored data from the target external cache partition fails to the target flash granule fails, the data can be stored to the target flash granule by backing up the external cache partition, thereby avoiding the target The data in the external cache partition is so lost that the data cannot be successfully written to the target flash granules.

In a possible design, the controller is further configured to determine backup flash granules of the target flash granule, determine an external cache partition corresponding to the backup flash granule, and store the to-be-stored data into the backup flash granule Corresponding external cache partition; storing the to-be-stored data from an external cache partition corresponding to the backup flash granule to the backup flash granule. By designing backup flash granules for the target flash granules and storing the data to be stored in the backup flash granules, data loss due to misfed memory sticks or flash granule failures can be avoided.

In one possible design, the controller is further configured to detect faulty flash granules; and when detecting faulty flash granules, the controller is further configured to determine where the faulty flash granules are located a memory strip and a location of the failed flash memory particle on the memory strip; the controller is further configured to report an identifier of a memory strip in which the faulty flash memory particle is located and the faulty flash memory particle in the memory strip The location on the top. Because the faulty flash granules are detected and reported in time, the user can be prompted to take timely action, such as replacing the failed flash granules or replacing the memory stick where the failed flash granules are located.

In a possible design, the disk body further includes a controller slot, and the circuit board where the controller is located is pluggable into the controller slot. This makes it easy to replace the controller without having to open the cover and replace the entire PCB as in the prior art.

In one possible design, the at least two flash memory particles are disposed on the memory strip in a patch. Compared with the prior art, the method of soldering the flash memory particles on the PCB is more convenient for the user to replace the flash memory particles.

In one possible design, each of the memory strip interfaces are connected in parallel, with each of the memory strip interfaces and the controller being connected in series. In this way, the data communication between the memory strip and the memory stick can be realized by the serial to parallel mode, so the processing speed and performance of the data write request can be improved.

In one possible design, the flash memory particles on each of the memory strips are connected in parallel, and the flash memory particles are in series with the memory strip interface to which the memory strip in which it is located is connected. In this way, the data communication between the flash memory particles inside the memory strip can be realized by the serial to parallel mode, so the processing speed and performance of the data write request can be improved.

In a possible design, the disk body is provided with a buffer slot, and the circuit board where the external cache partition is located is pluggable into the buffer slot. This makes it easy to replace a new external cache partition.

In one possible design, each flash ray can also have its own failure time based on its own degree of wear and send a failure time or alarm signal to the controller. The controller reports the number or identification of the memory stick where the flash granules to be deflated and the location of the flash granules to be deflated on the memory stick to the array system or host. In this way, it is convenient for the host or the array system to perform corresponding operations, such as data migration, and prompt the user to replace the flash granules that are to be invalidated in time.

In a second aspect, an embodiment of the present invention provides a storage device, including:

a frame, the frame is provided with at least one storage interface; a controller is disposed in the frame; at least one storage module is pluggably inserted on the at least one storage interface; at least one external cache partition, and The at least one storage module is in one-to-one correspondence; the controller is configured to: when receiving a data write request, acquire a target storage module that stores data to be stored from the data write request, and determine a target external location corresponding to the target storage module Cache partitioning, storing the data to be stored in the target external cache partition; storing the data to be stored from the target external cache partition to the target storage module through a storage interface connected to the target storage module. The data to be stored that is delivered to a storage module is cached by the external cache partition, and then stored in each target storage module, and the data to be stored in the external cache partition is stored in each target storage module in parallel. This can save the scheduling process of the controller and improve the processing speed and performance of the data write request.

In a possible design, at least two storage units are disposed on each of the at least one storage module, and an external cache partition corresponding to each of the storage modules includes a corresponding one of the at least two storage units. At least two external sub-cache partitions; the controller is configured to obtain a target storage unit that stores data to be stored from the data write request, determine a target external sub-cache partition corresponding to the target storage unit, and store the data to be stored And storing the to-be-stored data from the target external sub-cache partition to the target storage unit through a storage interface connected by the storage module where the target storage unit is located. Since at least two storage units are disposed on each storage module, the external cache partition corresponding to each storage module also includes at least two external sub-cache partitions corresponding to at least two storage units. Further, because the external sub-cache partition is used to cache the data to be stored that is sent to a certain storage unit, and then stored separately to each target storage unit, the data to be stored in the external sub-cache partition is stored to each target storage. Units can be performed in parallel, which not only saves the controller's scheduling processing, but also improves the processing speed and performance of data write requests.

In a possible design, the storage device further includes at least one backup external cache partition, the at least one backup external cache partition is in one-to-one correspondence with the at least one external cache partition, and the controller is further configured to determine the Backing up an external cache partition corresponding to the target external cache partition, and storing the to-be-stored data in the backup external cache partition; failing to store the to-be-stored data from the target external cache partition to the target storage module And storing the to-be-stored data from the backup external cache partition to the target storage module. By designing a backup external cache partition for the external cache partition, it avoids the loss of data in the target external cache partition so that data cannot be successfully written to the target storage module.

In a possible design, the controller is further configured to determine a backup storage module of the target storage module, determine an external cache partition corresponding to the backup storage module, and store the to-be-stored data in the backup storage module. Corresponding external cache partitions; storing the data to be stored from an external cache partition corresponding to the backup storage module to the backup storage module. By designing a backup storage module for the target storage module and storing the data to be stored in the backup storage module, data loss due to faulty storage module or storage module failure can be avoided.

In a third aspect, an embodiment of the present invention provides a data storage method for controlling a storage device according to the second aspect. This method is described from the perspective of the controller. In this method, the controller receives a data write request. The controller then acquires a target storage module storing the data to be stored from the data write request, and determines a target external cache partition corresponding to the target storage module. And then the controller stores the to-be-stored data in the target external cache partition; and stores the to-be-stored data from the target external cache partition to the target storage through a storage interface to which the target storage module is connected Module.

In a possible design, at least two storage units are disposed on each of the at least one storage module, and an external cache partition corresponding to each of the storage modules includes a corresponding one of the at least two storage units. At least two external sub-cache partitions; the controller acquires a target storage module storing data to be stored from the data write request, and determines a target external cache partition corresponding to the target storage module; and the controller Storing the data to be stored in the target external cache partition; and storing the data to be stored from the target external cache partition to the target storage module through a storage interface connected to the target storage module, including: the control Obtaining, from the data write request, a target storage unit storing data to be stored, determining a target external sub-cache partition corresponding to the target storage unit; and the controller storing the to-be-stored data in the target external sub-cache Partitioning; and passing the data to be stored from the target external sub-cache partition through the target storage list Interface memory storage where the memory module connected to the target storage unit.

In one possible design, the storage device further includes at least one backup external cache partition, the at least A backup external cache partition is in one-to-one correspondence with the at least one external cache partition, and is described from the perspective of the controller. The method further includes: the controller determining a backup external cache partition corresponding to the target external cache partition, and Depositing the to-be-stored data into the backup external cache partition; the controller, when the storage of the to-be-stored data from the target external cache partition fails to the target storage module, the data to be stored is The backup external cache partition is stored to the target storage module.

In a possible design, from the perspective of the controller, the method further includes: the controller determining a backup storage module of the target storage module, determining an external cache partition corresponding to the backup storage module; The controller stores the to-be-stored data in an external cache partition corresponding to the backup storage module; and stores the to-be-stored data from an external cache partition corresponding to the backup storage module to the backup storage module.

In a fourth aspect, an embodiment of the present invention provides a control apparatus for controlling the storage apparatus according to the second aspect. Specifically, the control device can be a controller. The control device has the function of implementing the controller in the method of the third aspect. These functions can be implemented in hardware or in software by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

In one possible design, the specific structure of the control device as the controller may include a receiving unit, a determining unit, and a processing unit. The receiving unit, the determining unit, and the processing unit may perform respective functions in the method of the above third aspect.

In a fifth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the control device described in the above fourth aspect, and including a program designed to execute the above aspects.

DRAWINGS

FIG. 1 is a structural diagram of an SSD according to an embodiment of the present invention;

2 is a structural diagram of another SSD according to an embodiment of the present invention;

3 is a structural diagram of a system according to an embodiment of the present invention;

4 is a schematic diagram of a visual management interface according to an embodiment of the present invention;

FIG. 5 is a structural diagram of a storage device according to an embodiment of the present invention;

FIG. 6 is a flowchart of a data storage method according to an embodiment of the present invention;

FIG. 7 is a functional block diagram of a control apparatus according to an embodiment of the present invention.

detailed description

The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

Please refer to FIG. 1 , which is a structural diagram of an SSD according to an embodiment of the present invention. The SSD includes a disk body 10 on which a connection port 101 for connecting to a disk array and at least one memory bar interface 102 are disposed. The connection port 101 is, for example, a Serial Attached Small Computer System Interface (SAS) or a Peripheral Component Interface Express (English: Peripheral Component Interface Express, PCIE or PCIe).

The SSD further includes a controller 20 disposed in the disk body 10. The controller 20 is electrically connected to the connection port 101 and the memory bar interface 102, respectively.

Optionally, the disk 10 further includes a controller slot, and the circuit board where the controller 20 is located is pluggable into the controller slot. This makes it easy to replace the controller 20 without having to disassemble the cover and replace the entire PCB as in the prior art.

The SSD also includes at least one memory stick 30 that is pluggably inserted into the at least one memory stick interface 102. Specifically, the memory stick 30 includes a connector 302. The memory strip 30 can be inserted into the disk body 10 or detached from the disk body 10 through the connector 302 and the memory bar interface 102.

Optionally, the memory stick 30 further includes a handle 303. The handle 303 facilitates the user to insert and remove the memory stick 30.

At least two flash memory (English: Flash) particles 301 are disposed on each of the at least one memory stick 30. Flash memory particles 301 are used to store data. The controller 20 can receive a data read/write request sent by an upper host or other entity through the connection port 101. The controller 20 is configured to read and write data in the flash memory particles 301 on the memory stick connected to each of the memory strip interfaces 102 through each of the memory strip interfaces 102 according to the data read/write request.

This makes it easy to replace the memory stick 30 without having to open the cover and replace the entire PCB as in the prior art, while also reducing the replacement cost.

Optionally, the flash granule 301 includes an internal buffer and a flash memory.

Optionally, a capacitor and a non-volatile random access memory (English: Non-Volatile Random Access Memory, NVRAM for short) can be placed on the memory stick 30. Capacitors and NVRAM can perform some auxiliary functions of SSD, such as rectification and filtering, to prevent the supply voltage of each part of the circuit from changing due to load changes, and to improve the speed of data access.

Optionally, the flash memory 301, the capacitor or the NVRAM on the memory stick 30 can be disposed on the memory stick 30 in a manner of being mounted on the PCB, compared to the flash memory 301, the capacitor or the NVRAM in the prior art. The way, the way of patching is more convenient for users to replace.

Optionally, the disk 10 further includes a storage strip slot 103. When the storage strip 30 is inserted into the storage strip interface 102, the storage strip 30 can be received in the storage strip slot 103, and the storage strip 30 can be fixed on the one hand. On the other hand, it is easy to carry SSD.

Please continue to refer to FIG. 1. In order to improve the data access speed, a two-stage serial-to-channel is provided in the present embodiment. In short, devices of the same type are connected in parallel and then connected in series with other devices. Specifically, the one-stage serial transmission channel is: each storage bar interface 102 is in parallel structure, and then each storage bar interface 102 and the controller 20 are connected in series. As such, the data communication of the channels between the memory stick 30 and the memory stick 30 is in a serial to parallel manner.

Alternatively, the communication bus 201 between the controller 20 and the memory stick interface 102 may be a PCIe serial bus.

The second stage serial transmission channel is: parallelizing the flash memory particles 301 inside the memory strip 30, and then connecting in series with the memory strip interface 102. In other words, the flash memory particles 301 are connected in parallel, but the flash memory particles and the memory strip interface 102 are connected in series. In this way, data communication between the flash memory particles 301 inside the memory strip can be realized by a serial to parallel method.

Optionally, the bus 202 between the memory strip interface 102 and the flash memory 301 may be a hot-swappable internal integrated circuit (English: Inter-Integrated Circuit, I ² C) bus.

Referring next to FIG. 2, the SSD also includes an external buffer area 40. The external buffer area 40 and the controller 20 can be interconnected by using a PCIe bus. The external buffer area 40 is divided into at least two external cache partitions 401. Each external cache partition 401 corresponds to one flash granule 301. Each flash granule 301 has an internal buffer 3011. As shown in FIG. 2, the external buffer area 40 includes four external cache partitions 401, which are external cache partitions C1 to C4, respectively. The external cache partition C1 corresponds to the flash granule 1 of the first memory stick. The flash memory particle 1 has an internal buffer area C1'. The external cache partition C2 corresponds to the flash granule 2 of the first memory stick. The flash memory 2 has an internal buffer area C2'. The external cache partition C3 corresponds to the flash memory particles 3 of the first memory stick. The flash memory chip 3 has an internal buffer area C3'. The external cache partition C4 corresponds to the flash memory particles 4 of the first memory stick. The flash memory 4 has an internal buffer area C4'.

Please refer to FIG. 3 as a system diagram after having an external buffer area. The host can write data to the SSD, and can also read data from the SSD. Therefore, the host can send a data read/write request to the controller 20 through the connection port 101, which can also be called input (English: Input, referred to as: I)/output ( English: Output, referred to as: O) Request.

In addition, in FIG. 3, the external buffer area 40 may further include an external cache partition C9 and an external cache partition C10. The external cache partition C9 and the external cache partition C10 correspond to the flash granules 9 and the flash granules 10 of the second memory strip, respectively.

It should be noted that, in FIG. 3, the solid arrow indicates the I/O interaction flow, that is, the I/O request is sent from the upper host to the external cache partition 401, and the external cache partition 401 stores the data to be stored to the flash memory. The internal buffer area 3011 of the particles 301. The dotted arrow indicates the logical processing flow, that is, the external cache partition 401 establishes a logical mapping relationship with the internal buffer area 3011 of the flash memory, or the external buffer area 40 establishes a logical mapping relationship with the external buffer area 50, which is a backup relationship. The contents of each other's backup relationship will be described in detail later.

Optionally, a buffer slot may be reserved on the disk body 10. The external buffer area 40 may be inserted into or removed from the disk body 10 through the buffer slot. In the event that the external cache area 40 is corrupted, the damaged external buffer area 40 can be unplugged, and the new external buffer area 40 or the external cache partition area 401 can be replaced offline.

In actual use, a correspondence mapping table between the external cache partition 401 and the flash memory 301 can be established and stored in the controller 20 or other storage unit. Of course, it is also possible to directly establish a correspondence mapping table between the external cache partition 401 and the internal cache area 3011. Through the mapping table, the controller 20 can determine which partition the external cache partition corresponding to each flash granule is.

When the controller 20 receives the data write request, for example, receiving a data write request sent by the host from the connection port 101, acquiring target flash memory particles storing the data to be stored from the data write request, determining that the target flash memory particle corresponds to a target external cache partition, storing the to-be-stored data in the target external cache partition; storing the to-be-stored data from the target external cache partition to the target flash granule.

For example, the controller 20 receives a data write request sent by the host through the connection port 101. The data write request may include data to be stored and a location of the target flash granule for storing the data to be stored, such as flash granule 1 on the memory stick 30 numbered 1. In this case, the controller 20 can acquire the target flash granules by a data write request, for example, the target flash granules are the flash granules 1 on the memory stick 30 numbered 1.

Optionally, the data write request may not include a location of the target flash granule for storing the data to be stored, and the controller 20 may store the request to be stored in the data write request according to a preset write data rule. The data identifies a target flash granule. For example, the determined target flash granule is the flash granule 1 on the memory stick 30 numbered 1.

Optionally, the controller 20 determines, for example, a target external cache partition corresponding to the target flash particle by using the foregoing mapping table.

For example, the controller 20 determines, according to the mapping table, the target external cache partition corresponding to the target flash particle as the external cache partition C1.

Next, the controller 20 stores the data to be stored in the target external cache partition, for example, into the external cache partition C1.

Optionally, storing the to-be-stored data from the target external cache partition to the target flash granule, Therefore, the data to be stored is directly migrated from the target external cache partition to the target flash granule, or the data to be stored in the target external cache partition may be copied and stored to the target flash granule.

Optionally, because the memory strip interface 102 is connected in series with the flash memory particles 301 on the memory stick 30 connected thereto, and the respective flash memory particles 301 are connected in parallel, the memory strip interface 102 can perform multiple data to be stored in parallel. The operation of the corresponding target flash granules. As such, the bank interface 102 can process multiple data write requests in parallel.

For example, the controller 20 migrates the data to be stored stored on the target external cache partition C1 to the flash granule 1 through the target flash granule, that is, the memory stick interface 102 to which the flash granule 1 is connected. At the same time, the controller 20 can also migrate the data to be stored stored on the target external cache partition C2 to the flash memory particles 2 through the target flash granules, that is, the memory strip interface 102 to which the flash granules 2 are connected, wherein the flash granules 1 and the flash granules 2 The connected memory strip interfaces are the same memory stick interface.

It should be noted that, if the data to be stored in the target external cache partition is copied to the target flash granules, the target flash granules can be successfully stored after the data to be stored is stored on the target flash granules. The response is given to the controller 20, and the controller 20 deletes the data to be stored stored on the target external cache partition according to the response to save storage space. If the storage is not successful, the controller 20 may repeatedly control to store the data to be stored from the target external cache partition to the target flash granules until the storage is successful.

Optionally, storing the data to be stored from the target external cache partition to the target flash granule may directly store the data to be stored from the target external cache partition to the flash memory of the target flash granule, or may be The data to be stored is stored from the target external cache partition into the internal cache area of the target flash granule, and then the controller of the target flash granule stores the data to be stored from the internal buffer in the flash memory of the target flash granule through the internal cache mechanism. .

As can be seen from the above description, the embodiment of the present invention caches the data to be stored of each flash granule that is sent to a certain storage strip 30 through the external cache partition 401, and then stores the data to each target flash granule, respectively. The storage of the data to be stored in the external cache partition 401 to each target flash granule can be performed in parallel, which can save the scheduling process of the controller 20 and improve the processing speed and performance of the data write request. For example, suppose a certain memory bar 30 contains four flash memory particles 301, and the host issues four data write requests to write data to the four flash memory particles respectively, and the controller 20 writes the four data write requests. The stored data is stored in the external cache partition corresponding to the four flash granules, and then the data to be stored stored in the external cache partition corresponding to the four flash granules 301 is stored in the four flash granules 301 in parallel.

Optionally, at least two external cache partitions are connected to each other, so the controller 20 can directly control data transfer from one external cache partition to another external cache partition, and the data does not need to be transferred by the controller 20, so The purpose of fast data interaction can be achieved.

Optionally, referring to FIG. 2, the SSD further includes another external buffer area 50, which can serve as a backup buffer area of the external buffer area 40. The external buffer area 50 and the external buffer area 40 can be connected in series through the interface bus to maintain interworking.

Specifically, the external buffer area 50 includes, for example, at least two external cache partitions 501, such as external cache partitions C5 to C8, respectively. The external cache partition C5 is the backup cache partition of the external cache partition C1. The external cache partition C6 is the backup cache partition of the external cache partition C2. The external cache partition C7 is the backup cache partition of the external cache partition C3. The external cache partition C8 is the backup cache partition of the external cache partition C4.

Optionally, the number of external buffers 50 for backup may be one or multiple.

In practice, a backup mapping relationship between each external cache partition in two external cache areas can be established. The backup mapping relationship can be stored on the controller 20 or on other storage units. In this case, the controller 20 After determining the target external cache partition corresponding to the target flash granule, the backup external cache partition of the target external cache partition may also be determined according to the backup mapping relationship. Further, the controller 20 may store the data to be stored in the target external cache partition corresponding to the target flash granule and the backup external cache partition in the target external cache partition. Continuing with the foregoing example as an example, assuming that the target external cache partition is the external cache partition C1, the controller 20 can determine that the backup external cache partition of the external cache partition C1 is the external cache partition C5. The controller 20 can then store the data to be stored in the external cache partition C1 and the external cache partition C5.

Next, if the target external cache partition fails before storing the data to be stored from the target external cache partition to the target flash granule; or during the migration from the target external cache partition to the target flash granule, the user mistakenly pulls out the storage strip 30 Or the target flash granule fails, the data to be stored is not successfully stored to the target flash granule, and the controller 20 can obtain the data to be stored from the backup external cache partition when receiving the response of the storage failure and the above failure reason. And store the data to be stored in the target flash granules.

It should be noted that, in the case that the user mistakenly removes the memory stick 30, if the user reinserts the memory stick 30, when the controller 20 stores the data to be stored to the target flash granule, the previously stored portion is to be stored. Data is overwritten to ensure data consistency. If the user has replaced the memory stick 30, the controller 20 directly stores the data to be stored in the backup external cache partition directly into the target flash memory of the replaced memory stick. This also ensures data integrity and consistency.

With the backup external cache partition in this embodiment, the reliability of data storage can be improved.

Optionally, in order to mistype the memory strip 30 or the flash memory 301 to cause data loss, in the embodiment of the present invention, after determining the target flash granule for storing the data to be stored, the controller 20 may further determine Backup flash granules of target flash granules. Specifically, the controller 20 may be a backup flash granule that determines a target flash granule according to a backup relationship table between the flash granules. The backup relationship table is pre-configured to the controller 20, or the controller 20 is established according to a preset rule.

The controller 20 can also determine an external cache partition corresponding to the backup flash granule according to the foregoing mapping table. The controller 20 then stores the data to be stored to the external cache partition corresponding to the backup flash granules, and then stores the data to be stored from the external cache partition corresponding to the backup flash granules to the internal cache area of the backup flash granules, and then stores the data to the backup flash memory. Particles on the flash. The data to be stored in a data write request is stored on the target flash granule and the backup flash granule. When the target flash granule fails, the data to be stored can still be found on the backup flash granule to ensure the normal operation of the host.

Preferably, the backup flash granules and the target flash granules are located on different storage strips 30. In this way, the data to be stored in a data write request is stored on the target flash granule and the backup flash granule. After the storage strip 30 where the target flash granule is located is mistakenly deleted, the to-be-stored can still be found on the backup flash granule. Data, without data loss due to the memory strip 30 where the target flash granules are located is misplaced.

Next, how to change the capacity of the memory stick 30 online, for example, to reduce or increase the flash memory particles 301 online, or to replace the flash memory particles 301, or to insert, unplug or delete the memory stick 30, or the data migration of the memory stick 30 will be described.

In one possible example, the existing Small Computer System Interface (SCSI) protocol can be modified to match the online capacity change of the memory stick 30. A possible format of the modified SCSI protocol is shown in Table 1.

Table I

Among them, in Table 1, the operation code is similar to the read command 0x28 of the existing SCSI protocol, and the write command 0x2a. This embodiment can define a special operation code to represent the operation of the memory bar. For example, the definition operation code 0xf1 indicates the operation of the memory stick.

The storage bar operation code: indicates that a specific operation is performed on the storage bar 30, for example, inserting or extracting a certain storage bar 30, and a specific operation code may be represented by one byte, for example, it may be defined as: 0x1 indicates that a certain storage bar is queried. 30, 0x2 indicates that a certain memory strip 30 is deleted, 0x3 indicates that a certain storage strip 30 is inserted, and 0x6 indicates that data of a certain storage strip 30 is migrated, and other similarities are not exemplified herein.

Controlled storage strip identifier: identifies the number of the storage strip 30 to be operated. For example, the controlled storage strip identifier is defined as 0x5, and the identifier of the storage strip 30 indicating that the data is to be migrated is 0x5.

Control Variables and Data 1: Specify the identifier of the memory stick 30 to which the data is to be moved, the amount of data to be migrated, the data address, the data length, and the flag bit for completion of migration. Optionally, this field can be empty when the operation instruction is simple.

Control variables and data 2 and reserved fields belong to fields that can be further extended. Optionally, this field can be empty when the operation instruction is simple. For example, when a certain memory stick 30 is inserted, only the identification to the controlled memory stick 30 needs to be made, and the control variables and data 1, control variables and data 2 and reserved fields can be empty. Therefore, whether some of the fields in Table 1 are empty depends on the complexity of the operation.

In the extended SCSI protocol above, the control variables can support the management of the flash granules 301, and two fields of control variables and data are designed to ensure that a combination of various command parameters is completed.

Further, when the memory stick 30 is plugged and unplugged, the controller 20 can automatically report to the array system that the memory stick 30 is inserted or removed.

Optionally, the controller 20 detects whether there is a faulty flash granule 301; if the faulty flash granule 301 is detected, determining the location of the faulty flash granule 301, for example, the storage strip where the faulty flash granule 301 is located The number or identification of 30, and the location of the failed flash granule 301 on the memory stick 30; then the controller 20 can report the location of the failed flash granule to the array system or host. It should be noted that the manner in which the controller 20 detects the faulty flash granules 301 is well known to those skilled in the art. For example, the controller 20 periodically sends detection signals to all the online flash granules 301, if at a preset time. If the reply signal of a certain flash memory 301 is not received, it indicates that the flash memory 301 is faulty.

Optionally, the flash memory particles 301 can also calculate its own failure time according to its own degree of wear, and then send the failure time or alarm signal to the controller 20. The controller 20 can place the flash memory 301 to be invalidated. The number or identification of the memory stick 30 and the location of the flash memory 301 to be expired on the memory stick 30 are reported to the array system or host.

Optionally, the controller 20 may also migrate data on the flash granules 301 to be lapsed to other non-failed flash granules 301 according to the aforementioned extended SCSI protocol.

Optionally, the embodiment of the present invention further provides a visual management interface for cooperating with the operation of the storage strip 30. For example, the faulty flash granule 301 and the flash granule 301 to be invalidated may be displayed to prompt the user to perform the replacement operation. .

Please refer to FIG. 4, which is a schematic diagram of a possible visual management interface. When the array system or the host receives the failed flash granules 301 or the flash granules 301 to be invalidated by the controller 20, it is performed on the visual management interface corresponding to the faulty flash granules 301 or the icon positions of the flash granules 301 to be invalidated. It is suggested that in FIG. 4, different filled backgrounds are used to represent flash granules of different states, but in practical applications, other prompting manners may be used for prompting, for example, red indicates failure, green indicates normal, and yellow indicates failure.

Optionally, the foregoing external cache partition, backup cache partition, and backup target flash granules may also be applied to the hard disk array and the server.

Specifically, please refer to FIG. 5, which is a structural diagram of a storage device according to an embodiment of the present invention. The storage device includes: a frame 601, at least one storage interface 6011 is disposed on the frame 601; a controller 602 is disposed in the frame 601; and at least one storage module 603 is pluggably inserted into the at least one storage interface 6011; An external cache partition 604 is in one-to-one correspondence with at least one storage module 603.

Please refer to FIG. 6 at the same time, which is a flowchart of a data storage method applied to the storage device shown in FIG. 5. The implementation of the data storage method and the functions that can be implemented by various parts of the storage device will be described below with reference to FIGS. 5 and 6. As shown in FIG. 6, the method includes:

Step 701: The controller 602 receives a data write request.

Step 702: The controller 602 acquires, from the data write request, a target storage module that stores data to be stored, and determines a target external cache partition corresponding to the target storage module.

Step 703: The controller 602 stores the to-be-stored data in the target external cache partition, and stores the to-be-stored data from the target external cache partition to the storage interface 6011 connected to the target storage module. The target storage module.

Optionally, each storage module 603 includes an internal buffer area 6031 and a storage body. Therefore, in step 703, the data to be stored is stored from the target external cache partition to the target storage module through the storage interface 6011 connected to the target storage module, and the data to be stored may be external to the target. The cache partition is stored in the internal cache area 6031 of the target storage module by the storage interface 6011 connected to the target storage module, or may be the storage to be stored from the target external cache partition through the target storage module. The interface 6011 is stored to the storage body of the target storage module. If the internal cache area 6031 of the target storage module is first stored, the controller of the target storage module may store the data to be stored from the internal cache area 6031 of the target storage module to the storage body of the target storage module according to an internal cache mechanism.

If there is only one storage unit on each storage module 603, that is, one storage module 603 is a single storage unit, then the implementation process of steps 701 to 703, and the foregoing description of the SSD, the data storage method of the controller 20 of the SSD It is similar if the flash memory 301 in the foregoing description is replaced with the storage module 603 in the present embodiment.

If at least two storage units are disposed on each storage module 603, for example, at least two flash memory particles 301 are disposed on the storage strip 30 of the foregoing SSD. Correspondingly, an external cache partition 604 packet corresponding to each storage module 603 At least two external sub-cache partitions corresponding to at least two storage units are included. Correspondingly, step 702 includes: the controller 602 acquires, from the data write request, a target storage unit that stores the data to be stored, and determines a target external sub-cache partition corresponding to the target storage unit. Step 703 includes: the controller 602 storing the to-be-stored data in the target external sub-cache partition; and connecting the to-be-stored data from the target external sub-cache partition through a storage module in which the target storage unit is located The storage interface is stored to the target storage unit. The specific implementation is similar to the foregoing SSD, as long as the flash granules are replaced by the storage unit, that is, the implementation process of step 702 and step 703 in this embodiment.

Optionally, each storage unit includes an internal sub-buffer and a storage body.

Optionally, in the case that at least two storage units are disposed on each storage module 603, the foregoing scheme of backing up the external cache partition and backing up the target flash granules may also be used, as long as the flash granules are replaced with the storage units, ie, The specific implementation process in the embodiment.

Optionally, in the case that each storage module 603 is a single storage unit, the foregoing scheme of backing up the external cache partition and the backup target storage unit may also be used. The specific implementation process is as follows: the storage device further includes at least one Backing up an external cache partition, the at least one backup external cache partition is in one-to-one correspondence with the at least one external cache partition. Correspondingly, the controller 602 determines a backup external cache partition corresponding to the target external cache partition, and stores the to-be-stored data in the backup external cache partition; the controller 602 is configured to store the data to be stored from the target When the external cache partition is stored to the target storage module, the data to be stored is stored from the backup external cache partition to the target storage module. The solution is a solution that uses a backup external cache partition to provide data storage reliability. For a detailed implementation process, reference may be made to the description of the backup external cache partition in the foregoing SSD.

The solution of the backup storage module is as follows: the controller 602 further determines a backup storage module of the target storage module, and determines an external cache partition corresponding to the backup storage module; the controller 602 also stores the data to be stored into the backup. An external cache partition corresponding to the storage module; storing the data to be stored from an external cache partition corresponding to the backup storage module to the backup storage module. Through this solution, the target storage module can be prevented from being faulty or misplaced, and data can be found in the backup storage module to avoid data loss. For a detailed implementation process, reference may be made to the description of the backup flash granules in the aforementioned SSD.

Based on the same inventive concept, an embodiment of the present invention provides a control device for implementing the data storage method shown in FIG. 6 to control the storage device as shown in FIG. 5 above. As an example, please refer to FIG. 7 , which is a functional block diagram of the control device. The control device includes a receiving unit 801 , a determining unit 802 , and a processing unit 803 .

The receiving unit 801 is configured to receive a data write request, and the determining unit 802 is configured to acquire, from the data write request, a target storage module that stores data to be stored, and determine a target external cache partition corresponding to the target storage module; The unit 803 is configured to store the to-be-stored data into the target external cache partition, and store the to-be-stored data from the target external cache partition to a storage interface connected by the target storage module. The target storage module.

Optionally, at least two storage units are disposed on each of the at least one storage module, and an external cache partition corresponding to each of the storage modules includes at least two corresponding to the at least two storage units. An external sub-cache partition; the determining unit 802 is configured to obtain, from the data write request, a target storage unit that stores data to be stored, and determine a target external sub-cache partition corresponding to the target storage unit; and the processing unit 803 is configured to: The storage data is stored in the target external sub-cache partition; and the data to be stored is stored from the target external sub-cache partition to the target storage unit through a storage interface to which the storage module in which the target storage unit is located is connected.

Optionally, the storage device further includes at least one backup external cache partition, the at least one backup external cache partition is in one-to-one correspondence with the at least one external cache partition, and the determining unit 802 is further configured to: determine the target external cache. Replacing the external cache partition corresponding to the partition, and storing the data to be stored in the backup external cache partition; the processing unit 803 is further configured to: store the to-be-stored data from the target external cache partition to the target When the storage module fails, the data to be stored is stored from the backup external cache partition to the target storage module.

Optionally, the determining unit 802 is further configured to: determine a backup storage module of the target storage module, and determine an external cache partition corresponding to the backup flash granule; the processing unit 803 is further configured to: store the to-be-stored data into the The external cache partition corresponding to the backup flash granule is stored; the data to be stored is stored from the external cache partition corresponding to the backup storage module to the backup storage module.

It should be noted that the control device is presented in the form of a functional unit. The term "unit" as used herein, without limitation, may refer to an application-specific integrated circuit (ASIC), electronic circuit, (shared, dedicated or group) processor, and memory that executes one or more software or firmware programs. Combining logic circuits, and/or other suitable components that provide the described functionality.

The various changes and specific examples in the foregoing SSD embodiments are also applicable to the storage device and the control device of the present embodiment. Through the foregoing detailed description of the SSD, those skilled in the art can clearly know the storage device and the control in this embodiment. The method of implementation of the device, so for the sake of brevity of the description, it will not be described in detail herein.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

A solid state hard disk SSD, comprising:

a disk body, the disk body is provided with a connection port for connecting with the disk array, and at least one memory bar interface;

a controller is disposed in the disk body, and the controller is electrically connected to the connection port and the storage bar interface respectively;

At least one memory strip is pluggably inserted into the at least one memory strip interface, and each of the at least one memory strip is provided with at least two flash memory particles, wherein the flash memory particles are used for storing data, The controller is configured to read and write data in the flash granules on the storage strips connected to each of the memory strip interfaces through each of the memory strip interfaces.
The SSD of claim 1 wherein said SSD further comprises at least two external cache partitions, each external cache partition corresponding to a flash memory granule.

The controller is configured to: when receiving a data write request, acquire target flash granules storing data to be stored from the data write request, determine a target external cache partition corresponding to the target flash granule, and store the to-be-stored data Entering the target external cache partition;

The data to be stored is stored from the target external cache partition to the target flash granule.
The SSD of claim 2, wherein the SSD further comprises at least two backup external cache partitions, and the at least two backup external cache partitions are in one-to-one correspondence with the at least two external cache partitions.

The controller is further configured to determine a backup external cache partition corresponding to the target external cache partition, and store the to-be-stored data in the backup external cache partition;

And storing the to-be-stored data from the backup external cache partition to the target flash granule when the storage of the to-be-stored data from the target external cache partition fails.
The SSD of claim 2, wherein the controller is further configured to determine backup flash granules of the target flash granule, determine an external cache partition corresponding to the backup flash granule, and store the data to be stored And entering an external cache partition corresponding to the backup flash granule; storing the data to be stored from an external cache partition corresponding to the backup flash granule to the backup flash granule.
The SSD according to any one of claims 1 to 4, wherein the controller is further configured to detect whether there is a faulty flash memory particle;

The controller is further configured to determine a memory strip in which the faulty flash memory is located and a location of the faulty flash memory on the memory strip when the faulty flash memory particle is detected; the controller further An identifier of a memory strip in which the flash memory particles reporting the fault are located and a location of the faulty flash memory particle on the memory strip.
A storage device, comprising:

a frame on which at least one storage interface is disposed;

a controller disposed in the frame;

At least one storage module is pluggably inserted into the at least one storage interface;

At least one external cache partition corresponding to the at least one storage module;

The controller is configured to: when the data write request is received, acquire a target storage module that stores the data to be stored from the data write request, determine a target external cache partition corresponding to the target storage module, and store the data to be stored. Entering the target external cache partition;

And storing the to-be-stored data from the target external cache partition through the storage connected to the target storage module The interface is stored to the target storage module.
The storage device according to claim 6, wherein each of the at least one storage module is provided with at least two storage units, and an external cache partition corresponding to each of the storage modules includes the At least two external sub-cache partitions corresponding to at least two storage units;

The controller is configured to obtain, from the data write request, a target storage unit that stores data to be stored, determine a target external sub-cache partition corresponding to the target storage unit, and store the to-be-stored data in the target external sub-cache. Partition

And storing the to-be-stored data from the target external sub-cache partition to a storage interface connected by a storage module where the target storage unit is located to the target storage unit.
The storage device of claim 6, wherein the storage device further comprises at least one backup external cache partition, the at least one backup external cache partition being in one-to-one correspondence with the at least one external cache partition,

The controller is further configured to determine a backup external cache partition corresponding to the target external cache partition, and store the to-be-stored data in the backup external cache partition;

And storing the to-be-stored data from the backup external cache partition to the target storage module when the storage of the to-be-stored data from the target external cache partition fails to the target storage module.
The storage device of claim 6, wherein the controller is further configured to determine a backup storage module of the target storage module, determine an external cache partition corresponding to the backup storage module, and store the data to be stored. And storing the data to be stored from the external cache partition corresponding to the backup storage module to the backup storage module.
A data storage method for a storage device according to claim 6, wherein the method comprises:

The controller receives a data write request;

The controller acquires a target storage module that stores data to be stored from the data write request, and determines a target external cache partition corresponding to the target storage module;

The controller stores the to-be-stored data in the target external cache partition; and stores the to-be-stored data from the target external cache partition to a target storage through a storage interface to which the target storage module is connected Module.
The method according to claim 10, wherein each of the at least one storage module is provided with at least two storage units, and an external cache partition corresponding to each of the storage modules includes the at least At least two external sub-cache partitions corresponding to the two storage units; the controller acquires a target storage module storing the data to be stored from the data write request, and determines a target external cache partition corresponding to the target storage module; The controller stores the to-be-stored data in the target external cache partition; and stores the to-be-stored data from the target external cache partition to the target storage module through a storage interface to which the target storage module is connected ,include:

The controller acquires, from the data write request, a target storage unit that stores data to be stored, and determines a target external sub-cache partition corresponding to the target storage unit;

The controller stores the to-be-stored data in the target external sub-cache partition; and partitions the to-be-stored data from the target external sub-cache partition through a storage interface to which the storage module in which the target storage unit is located Stored to the target storage unit.
The method of claim 10, wherein the storage device further comprises at least one backup external cache partition, the at least one backup external cache partition being in one-to-one correspondence with the at least one external cache partition, the method further include:

Determining, by the controller, a backup external cache partition corresponding to the target external cache partition, and storing the to-be-stored data in the backup external cache partition;

And when the controller fails to store the to-be-stored data from the target external cache partition to the target storage module, the controller stores the to-be-stored data from the backup external cache partition to the target storage module.
The method of claim 10, wherein the method further comprises:

Determining, by the controller, a backup storage module of the target storage module, and determining an external cache partition corresponding to the backup storage module;

The controller stores the to-be-stored data in an external cache partition corresponding to the backup storage module; and stores the to-be-stored data from an external cache partition corresponding to the backup storage module to the backup storage module.