Garbage collection exception handling method, device, computer equipment and storage medium

Abstract

The embodiment of the present application discloses a method, device, computer equipment and storage medium for handling exceptions of garbage collection. The method is applied to a solid-state hard disk, in which a first mapping table and a second mapping table corresponding to a physical block are pre-stored, and the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into preset sizes according to a preset division rule. The method includes: under preset conditions, all first mapping tables and all sub-table bitmaps corresponding to the physical block are loaded; when the first uncorrectable error of the first mapping table is read, the physical block address corresponding to the first mapping table is loaded; when the second uncorrectable error of the physical block address is read, whether the physical block address is on the second mapping table is determined according to the sub-table bitmap; if it is on the second mapping table, the physical block address is processed according to the preset strategy. The method for handling exceptions of garbage collection provided in the embodiment of the present application can accelerate the search for the physical block address of the uncorrectable error.

Description

Technical Field

[0001] The present application relates to the technical field of solid-state hard disks, and in particular to an exception handling method, apparatus, computer equipment, and storage medium for garbage collection. Background Art

[0002] At present, L2P (Logical to Physical) and P2L (Physical to Logical) are mainly used for garbage collection (GC). If a P2L table reads an uncorrectable error (UNC), and a physical block address (PBA) covered by this P2L also reads an uncorrectable error, it is necessary to search the entire L2P table to find the physical block address of the uncorrectable error. As the capacity of solid-state disks (Solid State Disk or Solid State Drive, referred to as SSD) increases, the L2P table also increases. It takes a long time to search the entire L2P table, which affects the speed of garbage collection to release physical blocks (PB) and the processing speed of the host. Therefore, how to speed up the search for physical block addresses of uncorrectable errors is a technical problem that needs to be solved urgently. Summary of the invention

[0003] One of the purposes of the present application is to provide a garbage collection exception handling method, apparatus, computer equipment and storage medium to solve the problem of how to speed up the search for physical block addresses of uncorrectable errors.

[0004] In a first aspect, an embodiment of the present application provides a garbage collection exception handling method, which is applied to a solid-state hard disk, wherein a first mapping table and a second mapping table corresponding to a physical block are pre-stored in the solid-state hard disk, wherein the first mapping table is a mapping table from a physical address to a logical address, and the second mapping table is a mapping table from a logical address to a physical address, wherein the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into preset sizes according to a preset division rule, wherein the sub-table bitmap is used to record the position of the data on the physical block in the second mapping sub-table, and the method includes:

[0005] Under a preset condition, loading all first mapping tables and all sub-table bitmaps corresponding to the physical block;

[0006] When a first uncorrectable error in the first mapping table is read, loading a physical block address corresponding to the first mapping table;

[0007] When a second uncorrectable error of the physical block address is read, determining whether the physical block address is on the second mapping table according to the sub-table bitmap;

[0008] If it is on the second mapping table, the physical block address is processed according to a preset strategy.

[0009] In an optional implementation, the processing the physical block address according to a preset strategy includes:

[0010] Moving the data in the physical block address to the target physical block;

[0011] According to the first mapping table, the logical allocation address corresponding to the physical block address is written into the spare area, and an invalid flag is set for the logical allocation address in the spare area.

[0012] In an optional implementation manner, after writing the logical allocation address corresponding to the physical block address into the spare area and setting an invalid flag for the logical allocation address in the spare area, the method further includes:

[0013] When reading the physical block address, if the invalid flag is read, an error message is displayed.

[0014] In an optional implementation manner, before loading all first mapping tables and all sub-table bitmaps corresponding to the physical block under a preset condition, the method further includes:

[0015] When the physical block is full, the sub-table bitmap is written into the physical block of the single-level storage unit flash memory.

[0016] In an optional implementation manner, before loading all first mapping tables and all sub-table bitmaps corresponding to the physical block under a preset condition, the method further includes:

[0017] Create a physical block and clear the cache area of ​​the first mapping table;

[0018] Writing the physical allocation address into the physical block, and writing the corresponding logical allocation address into the buffer area of ​​the first mapping table;

[0019] If it is detected that the cache area of ​​the first mapping table is full or the physical block is full, the first mapping table is written into the physical block of the single-level storage unit flash memory.

[0020] In an optional implementation, the preset condition includes that the number of errors of the physical pages of the solid state drive exceeds a preset error threshold and / or the invalid data of the solid state drive exceeds an invalid data threshold.

[0021] In a second aspect, an embodiment of the present application provides an exception handling device for garbage collection, which is applied to a solid-state hard disk, wherein a first mapping table and a second mapping table corresponding to a physical block are pre-stored in the solid-state hard disk, wherein the first mapping table is a mapping table from a physical address to a logical address, and the second mapping table is a mapping table from a logical address to a physical address, wherein the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into a preset size according to a preset division rule, wherein the sub-table bitmap is used to record the position of the data on the physical block in the second mapping sub-table, and the device includes:

[0022] A sub-table bitmap loading module, used for loading all first mapping tables and all sub-table bitmaps corresponding to the physical block under preset conditions;

[0023] A physical block address loading module, configured to load a physical block address corresponding to the first mapping table when a first uncorrectable error in the first mapping table is read;

[0024] a judgment module, configured to judge whether the physical block address is on the second mapping table according to the sub-table bitmap when a second uncorrectable error of the physical block address is read;

[0025] The processing module is used for processing the physical block address according to a preset strategy if it is on the second mapping table.

[0026] In a third aspect, a computer device is provided, the computer device comprising a memory and a processor, the memory storing a computer program, and the computer program, when executed by the processor, implements the garbage collection exception handling method described in the first aspect.

[0027] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the garbage collection exception handling method as described in the first aspect is implemented.

[0028] The embodiments of the present application provide an exception handling method, device, computer equipment and storage medium for garbage collection. The method is applied to a solid-state hard disk, including: under preset conditions, loading all first mapping tables and all sub-table bitmaps corresponding to the physical block; when the first uncorrectable error of the first mapping table is read, loading the physical block address corresponding to the first mapping table; when the second uncorrectable error of the physical block address is read, judging whether the physical block address is on the second mapping table according to the sub-table bitmap; if it is on the second mapping table, processing the physical block address according to a preset strategy. When the second uncorrectable error of the physical block address is read, the position of the physical block address in the second mapping table is searched according to the sub-table bitmap, which can speed up the search for the physical block address of the uncorrectable error compared to the prior art of searching the entire second mapping table for the position of the physical block address in the second mapping table. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present application and should not be regarded as limiting the scope of protection of the present application. In each of the drawings, similar components are numbered similarly.

[0030] Figure 1 A schematic block diagram showing the steps of a garbage collection exception handling method provided by an embodiment of the present application is shown;

[0031] Figure 2 A schematic block diagram of the structure of a garbage collection exception handling device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0032] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0033] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0034] Hereinafter, the terms "including", "having" and their cognates, which may be used in various embodiments of the present application, are intended only to indicate specific features, numbers, steps, operations, elements, components, or combinations of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing items or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations of the foregoing items.

[0035] Furthermore, the terms “first”, “second”, “third”, etc. are merely used for distinguishing descriptions and are not to be understood as indicating or implying relative importance.

[0036] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present application belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present application.

[0037] Example 1

[0038] Please refer to Figure 1 , Figure 1 A schematic block diagram showing the steps of a garbage collection exception handling method provided in an embodiment of the present application is shown.

[0039] like Figure 1 As shown, a garbage collection exception handling method provided in an embodiment of the present application can be applied to a solid-state hard disk, in which a first mapping table and a second mapping table corresponding to a physical block are pre-stored, the first mapping table is a mapping table from a physical address to a logical address, the second mapping table is a mapping table from a logical address to a physical address, the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into preset sizes according to a preset division rule, the sub-table bitmap is used to record the position of the data on the physical block in the second mapping sub-table, including S110 to S140.

[0040] S110: Under a preset condition, all first mapping tables and all sub-table bitmaps corresponding to the physical block are loaded.

[0041] In this embodiment, a physical block (PB) is a physical area for storing data on a recording medium. The first mapping table (Physical to Logical, P2L table) is a mapping table of physical addresses to logical addresses, and mainly stores mapping information of physical addresses to logical addresses. The second mapping table (Logical to Physical, L2P table) is a mapping table of logical addresses to physical addresses, and mainly stores mapping information of logical addresses to physical addresses.

[0042] Furthermore, the second mapping table includes dividing the second mapping table into at least two second mapping sub-tables of a preset size and a sub-table bitmap according to a preset division rule. The preset division rule and the preset size can be set according to actual needs and are not limited here. Each bit (Bit) in the sub-table bitmap represents a second mapping sub-table. Exemplarily, the second mapping table is divided into at least two second mapping sub-tables of a preset size of 64KB according to the preset division rule. The sub-table bitmap is used to record the position of the physical data in the second mapping sub-table, providing a basis for subsequent accelerated search for physical block addresses of uncorrectable errors.

[0043] Furthermore, the preset condition includes that the number of errors of the physical pages of the solid state drive exceeds a preset error threshold and / or the invalid data of the solid state drive exceeds an invalid data threshold.

[0044] Specifically, the physical block includes multiple physical pages. When the solid-state drive detects that the number of errors in its own physical page is greater than a preset error threshold, that is, exceeds the error correction capability range of the error correction code (ECC), and / or its own invalid data is greater than the invalid data threshold, garbage collection will be performed. Invalid data can be data generated by the storage device itself, or data set by the user. Invalid data is only for filling the data given in the physical block of the specified type, and is not valid data for the user. The user does not need to pay attention to invalid data, and there is no restriction on the content of the invalid data, which can be selected based on experience. The invalid data can be of a specified size, such as the invalid data can be a page, which can fill a free page of a physical block of the specified type.

[0045] In an optional implementation manner, before loading all first mapping tables and all sub-table bitmaps corresponding to the physical block under a preset condition, the method further includes:

[0046] When the physical block is full, the sub-table bitmap is written into the physical block of the single-level storage unit flash memory.

[0047] Specifically, when the physical block is writing data, the sub-table bitmap of the corresponding second mapping sub-table is updated. When the physical block is full, the sub-table bitmap is written into a single-level cell (SLC) flash memory physical block.

[0048] In an optional implementation manner, before loading all first mapping tables and all sub-table bitmaps corresponding to the physical block under a preset condition, the method further includes:

[0049] Create a physical block and clear the cache area of ​​the first mapping table;

[0050] Writing the physical allocation address into the physical block, and writing the corresponding logical allocation address into the buffer area of ​​the first mapping table;

[0051] If it is detected that the cache area of ​​the first mapping table is full or the physical block is full, the first mapping table is written into the physical block of the single-level storage unit flash memory.

[0052] Specifically, when the number of available physical blocks in the solid-state drive is insufficient, a physical block is created, and a 32B buffer is allocated in a RAM (Read Only Memory) or a DRAM (Dynamic Random Aess Memory) as a first mapping table, that is, a buffer area of ​​the first mapping table. When data is written to the physical block for the first time, a physical allocation address (Physical Allocation Address, PAA) is written to the physical block, and a logical allocation address corresponding to the physical allocation address is written to the buffer area of ​​the first mapping table. If the solid-state drive detects that the buffer area of ​​the first mapping table is full or the physical block is full, the first mapping table is written to a single-level storage unit flash memory physical block. Wherein, the physical allocation address is the flash memory address stored in the physical address.

[0053] S120: When a first uncorrectable error in the first mapping table is read, a physical block address corresponding to the first mapping table is loaded.

[0054] In this embodiment, a physical block address (Physical Block Address, PBA) is the address of a physical block or the physical block pointed to by a certain address.

[0055] S130: When a second uncorrectable error of the physical block address is read, determining whether the physical block address is on the second mapping table according to the sub-table bitmap.

[0056] In this embodiment, judging whether the physical block address is on the second mapping table according to the sub-table bitmap means directly searching whether the physical block address is in the sub-table bitmap; if it is in the sub-table bitmap, it is determined that the physical block address is on the second mapping sub-table, that is, the physical block address is on the second mapping table; if it is not in the sub-table bitmap, it is determined that the physical block address is not on the second mapping sub-table, that is, the physical block address is not on the second mapping table.

[0057] S140: If it is on the second mapping table, process the physical block address according to a preset strategy.

[0058] In this embodiment, if the physical block address is on the second mapping table, it means that the physical block address is valid and the physical block address is processed according to a preset strategy; if the physical block address is not on the second mapping table, it means that the physical block address is invalid and is not processed.

[0059] During the garbage collection exception handling process, when the second mapping table is updated, the garbage collection module and the cross-reading and writing modules wait for each other, and conflicts may occur between different modules. In an optional implementation, the processing of the physical block address according to a preset strategy includes:

[0060] Moving the data in the physical block address to the target physical block;

[0061] According to the first mapping table, the logical allocation address corresponding to the physical block address is written into the spare area, and an invalid flag is set for the logical allocation address in the spare area.

[0062] Specifically, after determining that the physical block address is valid, the data in the physical block address is moved to the target physical block. According to the first mapping table, the logical allocation address corresponding to the physical block address is searched, the logical allocation address is written into a spare area (spare area), and an invalid flag is set for the logical allocation address of the spare area. The logical allocation address is a flash address stored in the logical address, and the spare area is used to store metadata, such as information such as a logical block address (Logical Block Address, LBA), metadata is data describing data, and the logical block address is the address of a certain logical block or a logical block pointed to by a certain address.

[0063] It can be understood that when the physical block address is on the second mapping table, the data of the logical allocation address corresponding to the physical block address in the second mapping table is not directly modified to an uncorrectable error, but the logical allocation address is written to a spare area (spare area), and an invalid flag is set for the logical allocation address in the spare area, thereby avoiding conflicts between different modules.

[0064] It is worth noting that in the spare area, only the logical allocation address corresponding to the erroneous physical address that cannot be corrected will be set with an invalid flag, and other metadata such as the logical block address will not be set with an invalid flag.

[0065] In an optional implementation manner, after writing the logical allocation address corresponding to the physical block address into the spare area and setting an invalid flag for the logical allocation address in the spare area, the method further includes:

[0066] When reading the physical block address, if the invalid flag is read, an error message is displayed.

[0067] Specifically, when the solid state drive reads the physical block address, if the invalid flag is read, an error message of "media error" is displayed. It is understandable that the error message can be set according to actual conditions and is not limited here.

[0068] An exception handling method for garbage collection provided by an embodiment of the present application is applied to a solid-state hard disk, including: under preset conditions, loading all first mapping tables and all sub-table bitmaps corresponding to the physical block; when a first uncorrectable error of the first mapping table is read, loading the physical block address corresponding to the first mapping table; when a second uncorrectable error of the physical block address is read, judging whether the physical block address is on the second mapping table according to the sub-table bitmap; if it is on the second mapping table, processing the physical block address according to a preset strategy. When a second uncorrectable error of the physical block address is read, searching the position of the physical block address in the second mapping table according to the sub-table bitmap, compared with the prior art of searching the position of the physical block address in the second mapping table by searching the entire second mapping table, it can speed up the search for the physical block address of the uncorrectable error.

[0069] Example 2

[0070] Please refer to Figure 2 , Figure 2A structural schematic block diagram of a garbage collection exception handling device provided by an embodiment of the present application is shown. The garbage collection exception handling device 500 is applied to a solid state hard disk, in which a first mapping table and a second mapping table corresponding to a physical block are pre-stored, the first mapping table is a mapping table from a physical address to a logical address, the second mapping table is a mapping table from a logical address to a physical address, the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into preset sizes according to a preset division rule, the sub-table bitmap is used to record the position of the data on the physical block in the second mapping sub-table, and the garbage collection exception handling device 500 includes a sub-table bitmap loading module 510, a physical block address loading module 520, a judgment module 530 and a processing module 540.

[0071] The sub-table bitmap loading module 510 is used to load all first mapping tables and all sub-table bitmaps corresponding to the physical block under a preset condition;

[0072] The physical block address loading module 520 is used to load the physical block address corresponding to the first mapping table when a first uncorrectable error in the first mapping table is read;

[0073] The judging module 530 is configured to judge whether the physical block address is on the second mapping table according to the sub-table bitmap when a second uncorrectable error of the physical block address is read;

[0074] The processing module 540 is configured to process the physical block address according to a preset strategy if the physical block address is on the second mapping table.

[0075] Optionally, the processing module 540 includes:

[0076] A moving submodule, used for moving the data in the physical block address to a target physical block;

[0077] A submodule is set, which is used to write the logical allocation address corresponding to the physical block address into the spare area according to the first mapping table, and set an invalid flag for the logical allocation address of the spare area.

[0078] The above-mentioned device is used to execute the method provided in Example 1, and its implementation principle and technical effect are similar, which will not be repeated here.

[0079] An embodiment of the present application further discloses a computer device, which includes a memory and a processor. The memory stores a computer program. When the computer program is executed by the processor, it implements the garbage collection exception handling method as described in Example 1.

[0080] The embodiment of the present application further discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the garbage collection exception handling method as described in Embodiment 1 is implemented.

[0081] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0082] In addition, the functional modules or units in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0083] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art, and the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk.

[0084] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A method for handling exceptions in garbage collection, characterized in that: Applied to a solid state drive, the solid state drive pre-stores a first mapping table and a second mapping table corresponding to a physical block, the first mapping table is a mapping table from a physical address to a logical address, the second mapping table is a mapping table from a logical address to a physical address, the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into preset sizes according to a preset division rule, the sub-table bitmap is used to record the position of the data on the physical block in the second mapping sub-table, the method includes: Under a preset condition, loading all first mapping tables and all sub-table bitmaps corresponding to the physical block; When a first uncorrectable error in the first mapping table is read, loading a physical block address corresponding to the first mapping table; When a second uncorrectable error of the physical block address is read, determining whether the physical block address is on the second mapping table according to the sub-table bitmap; If it is on the second mapping table, the physical block address is processed according to a preset strategy; the processing of the physical block address according to the preset strategy includes: Moving the data in the physical block address to the target physical block; According to the first mapping table, writing the logical allocation address corresponding to the physical block address into the spare area, and setting an invalid flag for the logical allocation address in the spare area; After writing the logical allocation address corresponding to the physical block address into the spare area and setting an invalid flag for the logical allocation address in the spare area, the method further includes: When reading the physical block address, if the invalid flag is read, an error message is displayed.

2. The method according to claim 1, characterized in that Before loading all the first mapping tables and all the sub-table bitmaps corresponding to the physical block under the preset condition, the method further includes: When the physical block is full, the sub-table bitmap is written into the physical block of the single-level storage unit flash memory.

3. The method according to claim 1, characterized in that Before loading all the first mapping tables and all the sub-table bitmaps corresponding to the physical block under the preset condition, the method further includes: Create a physical block and clear the cache area of ​​the first mapping table; Writing the physical allocation address into the physical block, and writing the corresponding logical allocation address into the buffer area of ​​the first mapping table; If it is detected that the cache area of ​​the first mapping table is full or the physical block is full, the first mapping table is written into the physical block of the single-level storage unit flash memory.

4. The method according to claim 1, characterized in that: The preset conditions include that the number of errors of the physical pages of the solid state drive exceeds a preset error threshold and / or the invalid data of the solid state drive exceeds an invalid data threshold.

5. A garbage collection exception handling device, characterized in that: Applied to a solid state drive, the solid state drive pre-stores a first mapping table and a second mapping table corresponding to a physical block, the first mapping table is a mapping table from a physical address to a logical address, the second mapping table is a mapping table from a logical address to a physical address, the second mapping table includes a sub-table bitmap and at least two second mapping sub-tables divided into preset sizes according to a preset division rule, the sub-table bitmap is used to record the position of the data on the physical block in the second mapping sub-table, the device includes: A sub-table bitmap loading module, used for loading all first mapping tables and all sub-table bitmaps corresponding to the physical block under preset conditions; A physical block address loading module, configured to load a physical block address corresponding to the first mapping table when a first uncorrectable error in the first mapping table is read; a judgment module, configured to judge whether the physical block address is on the second mapping table according to the sub-table bitmap when a second uncorrectable error of the physical block address is read; a processing module, configured to process the physical block address according to a preset strategy if the physical block address is on the second mapping table; A moving submodule, used for moving the data in the physical block address to a target physical block; A submodule is set up to write the logical allocation address corresponding to the physical block address into the spare area according to the first mapping table, and set an invalid flag for the logical allocation address of the spare area; when reading the physical block address, if the invalid flag is read, an error message is displayed.

6. A solid state hard disk, characterized in that: The solid state drive includes a memory and a processor, the memory stores a computer program, and when the computer program is executed by the processor, the garbage collection exception handling method according to any one of claims 1 to 4 is implemented.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the garbage collection exception handling method according to any one of claims 1 to 4 is implemented.

Images