CN101676885B - Data management method and its storage device and its controller - Google Patents

Abstract

A data management method, a storage device and a controller thereof are provided. The method is suitable for a storage device with a plurality of blocks, wherein partial blocks in the blocks are associated into a plurality of mother-child blocks. The method at least comprises the following steps: checking whether the parent-child block of the current data to be written is the same as the parent-child block of the last data to be written; (b) if the mother-child block of the current data to be written is different from the mother-child block of the last data to be written, recording the transient information of the mother-child block of the current data to be written into the table.

Description

Data management method and its storage device and its controller

technical field

The invention relates to a data management method and its storage device and its controller, and in particular to a data management method for a flash memory storage device, the storage device and its controller. the

Background technique

With the advancement and development of storage and semiconductor technologies, storage devices with large capacity, small size and high speed are already flooding the market. Among them, the invention of the flash memory allows people to easily store data in the flash memory and transmit the data stored in the flash memory to a computer connected to it. the

When the traditional flash memory controller is in use, it does not store every variable information. If each variable information is stored, the burden and working time of the controller will be increased, and the writing speed will decrease. Therefore, the controller of the traditional flash memory may only store some tables (Tables) when changing zones (Zones), wherein the above-mentioned tables are, for example, logical entity correspondence tables. Generally speaking, the frequency of the transformed region will not be too high. Therefore, the time loss and the decline in access speed caused by storing some tables when changing regions are acceptable. the

In addition, when the traditional flash memory is used, for the sake of speed, it does not store variable data every time an instruction is issued. To put it further, all its variable data are reconstructed by scanning and analyzing its internal blocks (Block) when it is just turned on. the

However, in the case of abnormal power failure, it will be difficult to reconstruct the internal variable data. Because the flash memory cannot know whether its internal data is correct, and the data of the block will become unstable when the power is abnormally cut off. Maybe the data of the block is normal when it is turned on and scanned, but when it starts to save It will become abnormal after taking it. Therefore, the above-mentioned problems will make the internal program of the controller of the flash memory difficult to judge, and indirectly affect the stability of its data. the

Contents of the invention

Embodiments of the present invention provide a data management method, its controller and its storage device. the

Embodiments of the present invention provide a data management method, which is applicable to a storage device with multiple blocks, wherein some blocks in these blocks are associated into multiple Mother and Child Blocks (M&C Blocks, referred to as M&C Blocks for short). ). This data management method includes: (a) checking whether the mother-child block to be written into data is the same as the mother-child block of the last write data; (b) if the mother-child block to be written into data is the same as the last write If the parent and child blocks of the data are different, the transient information of the parent and child blocks to be written into data is recorded in the parent and child transient relationship table. the

An embodiment of the present invention provides a data management system for a storage device with multiple blocks, wherein some of the blocks are associated into a plurality of parent and child blocks. This data management system includes: the part that is used to check whether this mother-child block that will write data at present is identical with this mother-child block that writes data last time; When the mother-child block of writing data is the same, the data to be written at present is written to the parts of the mother-child block of data to be written at present; The parent-child block that writes data at one time does not simultaneously record a transient information of the parent-child block that is currently writing data to a parent-child transient relationship table and writes the data currently to be written into the current data to be written Components of the parent-child block. the

An embodiment of the present invention provides a storage device, including a storage block circuit, a system circuit and a controller. The storage block circuit has a plurality of blocks for storing data, wherein some of the blocks are associated into a plurality of mother and child blocks. The system circuit is used for storing at least one parent-sub-block transient relationship table. The controller is coupled to the memory block circuit and the system circuit, and is used to check whether the mother-child block to be written into data is the same as the mother-child block to be written to last time, if the mother-child block to be written into data is the same as the previous If the mother and child blocks for data writing are different, a transient state information of the mother and child blocks to be written into data is recorded in the mother and child block transient relationship table. the

The method for increasing data stability and its controller provided by the embodiments of the present invention can increase the stability of data in storage devices using this method or controller, so as to avoid data instability during abnormal power failures . In addition, because the transient state information of the mother-child block to be written into data is only recorded when the mother-child block to be written in data is different from the mother-child block of the last write-in data, the method of the present invention is used The data management method and its controller and storage device provided by the embodiments do not have much influence on the writing speed. the

In order to make the above-mentioned features and advantages of the present invention more comprehensible, preferred embodiments will be described in detail below together with the accompanying drawings. the

Description of drawings

FIG. 1 is a schematic diagram of a transient state of a flash memory storage device during storage. the

FIG. 2 is a flowchart of a data management method for a flash memory storage device provided by an embodiment of the present invention. the

FIG. 3 is a system block diagram of a storage device 30 and its controller 300 provided by an embodiment of the present invention. the

【Description of main component symbols】

Block 0: parent block

Block 1: Sub-block

Page 0～Page N: page

S20～S28: Step process

30: storage device

300: controller

301: Microprocessor

302: Buffer

303: Memory block circuit

304: System circuit

Detailed ways

Before introducing the data management method provided by the embodiments of the present invention, the storage device and its controller, here is a brief description of the writing principle of the storage device using the flash memory. The storage device of the flash memory has a plurality of blocks for storing data, and each block includes a plurality of pages. The storage device of the flash memory uses a block as a unit when erasing, and uses a page as a unit when reading or writing. When the storage device of the flash memory wants to write data into a certain block that has stored data, it will first move part of the data in the block that has stored data to another block that does not record data. Among them, the above-mentioned block that originally stored data is also called a parent block, and the above-mentioned block that originally has no recorded data and is used to associate with a parent block is also called a child block. In addition, it is worth explaining What is, in the present invention, due to the characteristics of the flash memory here, the block without recording data means that the data stored in each normal unit in the block is all 1, but according to the different specifications of each flash memory , the definition of the non-recorded data is not limited to this. Then, the storage device of the flash memory writes the pre-written data into the page corresponding to the sub-block, and other data of the parent block will also be moved to the corresponding page on the sub-block, and then, The parent block will be erased (Erased), and finally, the logical entity correspondence table will update its correspondence. If the logical block number of the parent block is Logic_0, the physical block number of the parent block is Block0, and the physical block number of the child block is Block1, then, before the above logical entity correspondence table is updated, the logical block The number Logic0 corresponds to the physical block number Block0, and after the logical entity correspondence table is updated, the logical block number Logic0 corresponds to the physical block number Block1. In other words, the address of the block in the flash memory has not changed, but the content of the logical entity table has been updated, so that the actual logical address corresponds to the physical block correctly, so that the data can be correctly read later. read and write. the

However, the above-mentioned access method is only an implementation manner, and is not used to limit the present invention. For the detailed access method of the above-mentioned flash memory, please refer to US12/047144, which will not be repeated here. When the parent block has not been erased and the data on the child block and the parent block have not been merged, the transient relationship will be recorded in the parent-child block transient relationship table. Among them, merging the data on the child block and the parent block refers to moving all the multiple valid data of the parent block to the child block, and clearing the corresponding relationship between the parent and child blocks and updating the logical entity correspondence table. Among them, the parent-sub-block transient relationship table includes the logical address of the sub-block, the corresponding relationship between the updated page in the sub-block and the page in the parent block, the version of the updated data, and all physical blocks up to now. The erasing times of the parent block, the erasing times of the sub-blocks, the mapping data of each existing parent-child block, the latest write command logic address or its corresponding parent-child block or other possible Relevant data to assist in averaging the wear times of each physical block. the

Please refer to FIG. 1 first. FIG. 1 shows a transient schematic diagram of a flash memory storage device during storage. Wherein, the example in FIG. 1 has different writing methods from the above example, but these writing methods are not used to limit the present invention. Assume that the logical block address Logic0 of the flash memory recorded in the logical entity table corresponds to the physical block Block0, and this physical block Block0 has stored multiple valid valid data, for example, the pages Page0～Page N of the physical block Block0 are all Valid data exists. If the logical address of the data to be written corresponds to the pages Page2 and Page3 of the physical block Block0, the system control chip of the storage device of the flash memory will search for a block without recorded data, usually a block in the spare area , such as the spare block Block1, and associate the spare block Block1 with the physical block Block0 to form a group of mother and child blocks, and then start writing data. In other words, when there is data to be written into a physical block that already has valid data, the storage device will search for an empty block and associate it with the physical block to form a set of parent and child blocks. Therefore, the physical block Block0 can be regarded as the parent block Block0, and the backup block Block1 can be regarded as the sub-block Block1 corresponding to the parent block Block0. Then, because the data of the pages Page0 and Page1 of the parent block Block0 are valid data, the data of the pages Page0 and Page1 of the parent block Block0 will be moved to the pages Page0 and Page1 of the child block Block1. the

Then, the new data will be sequentially written into the pages Page2 and Page3 of the sub-block Block1. That is, before the group of parent-child blocks is closed, this transient relationship can be recorded as a parent-child block transient relationship table. Because the data of pages Page4~Page N may be changed in subsequent commands, if this transient relationship can be stored first, and the parent and child blocks are closed only when the parent and child blocks need to be closed, unnecessary moving and The action of erasing a block. In addition, through the logical entity table and the parent-child block transient relationship table, the mapping between the logical block address and the physical block address will make multiple physical block addresses correspond to a logical block address, in other words, it is the parent block The content of the block Block0 and the sub-block Block1 is integrated to be the content of the corresponding logical block. the

In order to effectively manage the data in the flash memory, the best way is to record the internal variables every time an instruction comes. Then when the computer is turned on next time, it can be known which page (Page) of which block is being written before the power is turned off, and at this time, it only needs to be processed for this block. Therefore, every time a write command is received, information such as the logical address of the child block, the corresponding relationship between the updated page in the child block and the page in the parent block, and the version of the updated data are recorded in the parent-child block transient relationship The table method is the most robust (Robust) data management method, but this method has a great impact on its access speed. the

Therefore, the method of the present invention is to write the logical address of the sub-block, the corresponding relationship between the updated page in the sub-block and the page in the parent block, the version of the updated data, etc. Information, the erasing times of all physical blocks from this boot up, the erasing times of the parent block, the erasing times of the sub-blocks, the mapping data of each existing parent-child block, and the latest write command logic The address or its corresponding parent-child block or other relevant data that can assist in averaging the wear times of each physical block is recorded in the parent-child block transient relationship table. If the next instruction is to write to the child block (Child Block) written last time, the logical address of the child block, the corresponding relationship between the updated page in the child block and the page in the parent block will not be , the version of the updated data, the number of erasing times of all physical blocks from this boot up to the present, the number of times of erasing of the parent block, the number of times of erasing of the sub-blocks, the mapping data of each parent-child block currently existing, at least the latest The logical address of the write command or its corresponding parent-child block or other relevant data that can assist the average wear times of the physical block is recorded in the parent-child block transient relationship table. Because this situation indicates that the data this time is continuous data that continues the previous data, but it may also be random but just corresponds to the same parent block data. Therefore, the transient information of the parent and child blocks at this time (including child The logical address of the block, the corresponding relationship between the updated page in the sub-block and the page in the parent block, the version of the updated data, the erasing times of all physical blocks from this boot up to the present, and the erasing times of the parent block Erasing times of sub-blocks, mapping data of existing parent and sub-blocks, at least the most recent write command logic address or its corresponding parent and sub-blocks, or other relevant data that can assist in averaging the wear times of physical blocks) It does not need to be stored in the parent-child block transient relationship table. If the parent-child block to which data is to be written in the next instruction is not another parent-child block in which data was written last time, the transient information needs to be stored in the parent-child block transient relationship table. Therefore, it is possible to determine whether the current transient information needs to be recorded in the parent-child block transient relationship table by using whether the currently written parent-child block is the same as the last written parent-child block, so as to effectively manage data without seriously affecting its write speed. the

When starting up next time, or when the first write command comes down after starting up, in order to effectively manage data, the flash memory will forcibly close (close) the mother and child blocks that were being written before power off, that is, Move valid data of other pages of the parent block to pages corresponding to the child block. Therefore, regardless of normal power failure, the data management method and its storage device and its controller provided by the embodiments of the present invention can prevent valid data from being written into a block storing invalid data, thereby effectively managing data. the

In an embodiment of the present invention, the storage device of the flash memory stores multiple transient relationship tables of the parent and child blocks, and the transient relationship tables of the parent and child blocks can be stored in, for example, buffer circuits in the controller, temporary memory, A specific block in the flash memory or its system circuit. However, based on the convenience of data preservation or data recording, the latest parent-child block transient relationship data in the parent-child block transient relationship table will be updated in real time and stored in the temporary storage first. After a specific time, such as 3 minutes , or receive a specific command, such as flush, or perform a specific action, such as replacing the logical and physical block mapping table, and then copy the parent-child block transient relationship table with the latest data from the temporary memory to the flash memory Or update the parent-child block transient relationship table stored in the flash memory. Wherein, the number of parent-child block transient relationship tables that can be recorded is not used to limit the present invention. The transient information of these mother and child blocks can enable the storage device of the flash memory to know which page (Page) of which block is being written before power-off when the flash memory storage device is turned on. At the same time, these transient information can enable the data to be written later to quickly write data into the corresponding mother and child blocks according to the previous transient information. In another embodiment, these mother-child block transient relationship tables record information about the average number of times of wear and tear of multiple mother-child blocks, such as the number of erasing times of all physical blocks from this power-on to the present, the erasure of child blocks. The number of erasing times, the erasing times of the parent block, the mapping data of each existing parent and child blocks, the logical address of at least the latest write command, the mapping data of each currently existing parent and child block, and the logic of the latest write command address or its corresponding parent-child block or its corresponding parent-child block data. the

Please refer to FIG. 2 . FIG. 2 is a flowchart of a data management method for a flash memory storage device provided by an embodiment of the present invention. Firstly, after the power is turned on again, in step S20, it is judged whether there is a parent-child block, if yes, execute step S21, if no, execute step S26. Because most of the blocks of the flash memory storage device just leave the factory or after the card is opened have no recorded data, therefore, step S26 can be directly executed. the

In step S21, it is judged whether the received write data is the first write data received after the power is turned on, wherein at least one write logical address in each write command will be recorded or Update to the parent-child block transient relationship table. If yes, execute step S22, and if no, execute step S23. In step S22, close the specified mother-child block, that is, merge the data of the mother block in the last written mother-child block before the power is turned on into the child block, and update the logical entity table, and clear or update The corresponding parent-child block transient relationship table. Because the power outage before the power is turned on may be an abnormal power outage, so the data of the mother and child blocks written last before the power outage may be incorrect. In order to avoid writing valid data into a block with unstable data and effectively manage data, step S22 closes the last written parent and child blocks before power off. the

In step S23 , it is judged according to the write command recorded in the parent-child block transient relationship table whether the block to be written into is one of the multiple parent-child blocks into which data has been previously written. If yes, execute step S24, and if no, execute step S25. the

In step S25, it is checked whether there is a block with or without data recording, which can be matched with the parent block of the current logic writing address to become a corresponding parent-child block. If yes, execute step S26, otherwise execute step S27. In step S27, one of the multiple parent-child blocks is closed to generate a child block without recorded data. In addition, the parent-child block transient relationship table of the closed parent-child block is cleared or updated. In this way, the child block without recorded data can correspond to the parent block of the current logical writing address to become the currently written parent and child blocks, so step S26 can then be executed. the

In step S24, judge whether the mother-child block to be written into data is the mother-child block of last write data according to the write instruction recorded in the mother-child block transient relationship table, if yes, then execute step S28, If not, directly execute step S26. In step S26, store the transient state information of the parent-child block whose data is currently to be written into the parent-child block transient relationship table. In step S28, the data to be written is written into the sub-blocks in the parent-sub-block, and then returns to step S21. the

From the above method flow chart, it can be known that the data management method provided by the embodiment of the present invention will close the parent-child block that was written last before the power off when the power is turned on, so as to avoid writing valid data into blocks that may have invalid data, enabling efficient data management. In order to make those skilled in the art understand the present invention better, an example is used below to illustrate the operation of the above method. the

Assuming that the mother-child block to be written into is M&C1, it will judge whether there is a mother-child block and whether it is the first write command according to the mother-child block transient relationship table stored in the flash memory after booting. If all are, then the mother-child block of the last write-in data before the power is turned on is turned off, and then it is checked whether the mother-child block to write data is one of a plurality of mother-child blocks previously written in data. If the mother-child block to write data is not one of the multiple mother-child blocks that have previously written data, then directly store the transient information of the mother-child block to write data, and write the data to this The parent and child block of the input data. If it is not the first write command, it is directly checked whether the mother-child block to write data is one of the multiple mother-child blocks that have written data before. the

If the mother-child block M&C1 to write data at present is one of a plurality of mother-child blocks previously written in data, that is, there is a mother-child transient relationship table that records the transient information of the mother-child block to write data into, and The mother-child block M&C1 to which data is to be written this time is the same as the mother-child block M&C1 to which data was written last time, and the data will continue to be written into the mother-child block M&C1. If the mother-child block M&C1 to which data is currently written is one of the multiple mother-child blocks to which data was previously written, but is different from the mother-child block M&C2 in which data was written last time, the mother-child area to which data is currently to be written will be stored The transient state information of the block M&C1, so that the previously recorded transient state information in the parent-child block transient relationship table of the parent-child block M&C1 will be updated with the current transient state information. Since the mother-child block M&C1 to which data is currently written is different from the mother-child block M&C2 to which data was written last time, the data will be written into the currently written mother-child block M&C1. In addition, when the next write command comes in, according to the updated parent-child block transient relationship table, it can be known that the parent-child block of previously written data is M&C1. the

If the mother-child block M&C1 to write data in is not one of the multiple mother-child blocks previously written in data, it will check whether there is a child block with recorded data that can be associated with the parent block of the current logical write address to become If the currently written mother-child block is yes, then the transient information of the mother-child block M&C1 to be written into data will be stored, and then the data will be written into the mother-child block to be written into. If there is no empty child block, any parent-child block will be closed, and the parent-child block transient relationship table of the closed parent-child block will be cleared, so as to clear the empty child block and the current writing The parent block of the logical writing address of the data input is associated with the currently written parent-child block, and then the transient information of the parent-child block M&C1 to be written into data is stored, and then the data is written into this to-be-written data mother-child block. the

Next, please refer to FIG. 3 , which is a system block diagram of a storage device 30 and its controller 300 provided by an embodiment of the present invention. The storage device 30 includes a controller 300 , a storage block circuit 303 and a system circuit 304 . Wherein, the controller 300 includes a microprocessor 301 and a buffer 302 . The buffer 302 is coupled to the microprocessor 301 , and the processor 301 is coupled to the memory block circuit 303 and the system circuit 304 . In this embodiment, the controller 300 is separated from the system circuit 304 , however, the controller 300 can also be designed in the system circuit 304 , in other words, the above embodiments are not intended to limit the present invention. the

The memory bank circuit 303 includes a plurality of memory banks of the flash memory, and as mentioned above, these memory banks include a plurality of pages. In addition, the system circuit 304 is used to store the aforementioned parent-child transient relationship table. The system circuit 304 can be random access memory (Random Access Memory, RAM) or non-volatile memory or other types of storage units, and the parent-child transient state The relationship table records the logical address of the sub-block, the corresponding relationship between the updated pages in the sub-block and the pages in the parent block, the version of the updated data, the erasure times of all physical blocks from this power on to the present, and the parent block. The erasure times of the block, the erasure times of the sub-blocks, the mapping data of each existing parent and sub-block, at least the logical address of the latest write command or its corresponding parent and sub-blocks or other physical blocks that can be used to assist in wear Relevant data averaged over times. The buffer 302 stores program codes, and the microprocessor 301 is used to read the program codes from the buffer 302 . The above-mentioned program codes are originally stored in the memory block circuit 303, and the controller 300 controls the memory block circuit 303 to send the stored program codes to the buffer 302 for storage after the power is turned on. The microprocessor 301 then executes the program code of the buffer 302 to control the memory block circuit 303 and the system circuit 304 to implement the method shown in FIG. 2 . the

It is worth noting that, in addition to storing the parent-child block transient relationship in the system circuit 304, based on the convenience of data preservation or data recording, the controller 300 will pass a specific time, such as 3 minutes, or receive a specific command , such as flush, or perform a specific action, such as when replacing the logical and physical block mapping table, copy the parent-child block transient relationship table of the latest data from the system circuit 304 to the storage block circuit 303. In addition, the above-mentioned storage device 30 can be a storage device of a pendrive (PenDrive) or a storage device of a solid state disk (Solid State Disk, SSD), and the storage block circuit 303 can be a non-volatile memory, such as an NAND Type flash memory (Nand Flash). the

To sum up, the data management method and the controller provided by the embodiments of the present invention can enable the storage device using the method or the controller to manage data effectively. In addition, because the transient state information of the mother-child block to be written into data is only recorded when the mother-child block to be written in data is different from the mother-child block of the last write-in data, the method of the present invention is used The data management method and its controller and storage device provided by the embodiments do not have much influence on the writing speed. the

Although the present invention has been disclosed as above with the embodiments, it is not intended to limit the present invention. Those skilled in the art can make some changes and modifications without departing from the spirit and scope of the present invention. Therefore, the protection of the present invention The scope is to be determined as defined by the appended claims.

Claims (9)

1. a data managing method is applicable to the memory storage with a plurality of blocks, and wherein, the part block associations in these blocks becomes a plurality of mother and child blocks, and this data managing method comprises:

(a) to write one second mother and child blocks of data identical with the last time to check one first mother and child blocks will write data at present, when wherein if this first mother and child blocks is identical with this second mother and child blocks, execution in step (b) then, if and this first mother and child blocks is different with this second mother and child blocks, then execution in step (c);

(b) data that will will write at present write to this first mother and child blocks; And

(c) record transient information to a mothers and sons transient state relation table of this first mother and child blocks, and the data that will will write at present write to this first mother and child blocks,

Wherein this mother and sons' transient state relation table records a transient information of this second mother and child blocks.

2. data managing method as claimed in claim 1, wherein, this transient information that will write this first mother and child blocks of data at present comprises the logical address of a sub-block, the renewal page in one sub-block and the corresponding relation of the page in female block, one version of new data more, one start this time is to the erasing times of present all physical blocks, the erasing times of one female block, the erasing times of one sub-block, the mapping (enum) data of present each mother and child blocks that exists, the last write instruction logical address or its corresponding mother and child blocks or at least one other can be for the average related data of physical blocks wearing and tearing number of times of assisting this memory storage.

3. data managing method as claimed in claim 1 wherein also comprises before in step (a):

Whether (d) inspect this first mother and child blocks that will write data at present is one of these mother and child blocks that before write data, if it is non-during for one of these mother and child blocks of before having write data wherein will to write this first mother and child blocks of data at present, execution in step (e) then, if and this first mother and child blocks that will write data at present is during for one of these mother and child blocks of before having write data, then execution in step (a);

(e) check that the block whether no record data are arranged in these blocks can become a mother and child blocks with the block associations that will write data, if when wherein not having the block of any one no record data, execution in step (f) then, if and when having or not the block of record data, execution in step (c) then; And

(f) close these mother and child blocks any mother and child blocks and the execution in step (c) wherein that before writes.

4. data managing method as claimed in claim 3 wherein also comprises before in step (d):

(g) judge that received one writes instruction, whether be that the first stroke after this memory storage opening power writes instruction, if wherein this writes the first stroke that instructs to after this memory storage opening power and writes instruction, execution in step (h) then, if and this to write instruction non-for the first stroke after this memory storage opening power writes instruction, execution in step (d) then; And

(h) close this second mother and child blocks that the last time writes.

5. a data management system is applicable to the memory storage with a plurality of blocks, and wherein, the part block associations in these memory block becomes a plurality of mother and child blocks, and this data management system comprises:

Be used for to check that whether one first mother and child blocks that will write data at present writes the identical parts of one second mother and child blocks of data with the last time;

The data that are used for will will writing at present when this first mother and child blocks is identical with this second mother and child blocks write to the parts of this first mother and child blocks; And

Be used for working as this first mother and child blocks and this second mother and child blocks and do not record transient information to a mothers and sons transient state relation table of this first mother and child blocks simultaneously and incite somebody to action the parts that the data that will write at present write to this first mother and child blocks,

Wherein this mother and sons' transient state relation table records a transient information of this second mother and child blocks.

6. data management system as claimed in claim 5, wherein, this transient information that will write this first mother and child blocks of data at present comprises the logical address of a sub-block, the renewal page in one sub-block and the corresponding relation of the page in female block, one version of new data more, one start this time is to the erasing times of present all physical blocks, the erasing times of one female block, the erasing times of one sub-block, the mapping (enum) data of present each mother and child blocks that exists, the last write instruction logical address or its corresponding mother and child blocks or at least one other can be for the average related data of physical blocks wearing and tearing number of times of assisting this memory storage.

7. data management system as claimed in claim 5 also comprises:

Be used for inspecting this first mother and child blocks that will write data at present and whether be the parts of one of these mother and child blocks of before having write data;

Be used for whether writing the identical parts of this second mother and child blocks of data with the last time when this first mother and child blocks that will write data at present checks this first mother and child blocks that will write data at present during for one of these mother and child blocks of before having write data;

Be used for checking whether these blocks have the block of no record data can become the parts of a mother and child blocks with the block associations that will write data when this first mother and child blocks that will write data at present is non-during for one of these mother and child blocks of before having write data;

Record will write transient information to the mothers and sons transient state relation table of this first mother and child blocks of data and the parts that the data that will will write at present write to this first mother and child blocks that will write data at present at present when being used for the block as the no record data; And

For close these mother and child blocks any mother and child blocks wherein that before writes when not having the block of any one no record data, this transient information that records this first mother and child blocks that will write data at present also writes to the data that will write at present the parts of this first mother and child blocks that will write data at present to this mother and sons' transient state relation table.

8. data management system as claimed in claim 7 also comprises:

Whether being used for judging received one, to write instruction be the parts that the first stroke after this memory storage opening power writes instruction;

Be used for that non-whether inspect this first mother and child blocks that will write data at present when instructing be the parts that before write one of these mother and child blocks of data for the first stroke after this memory storage opening power writes when this writes instruction; And

Be used for writing the parts of closing this second mother and child blocks that the last time writes when instruction is instructed for the first stroke after this memory storage opening power writes when this.

9. data management system as claimed in claim 5, this memory storage is the memory storage of a flash memory.

Images