Defective management data handling method and recording medium

Abstract: A distributed management information such as a distributed management information 0 for management of a predetermined unit of data is stored in an redundant area of respective blocks of a flash memory, whereas a collected management information for all-at-once management of said data is stored in a predetermined block of the flash memory. When using the flash memory, firstly, it is determined whether the collected management information has an error. If any error is detected, a collected management information is created from the distributed management information in the redundant area of respective blocks. If the aforementioned data is modified, the collected management information is re-created according to the distributed management information of the redundant area of respective blocks, so that this collected management information is stored in the aforementioned predetermined block.

Description: BACKGROUND OF THE INVENTION Field of the Invention The present invention relates to a data management apparatus using, a data management method, and a recording medium which use a flash memory. Description of the Prior Art Conventionally, when an electronic apparatus such as a computer is used as a main storage apparatus, a memory apparatus is used to suffice a capacity of this main storage apparatus. As this storage apparatus, there can be exemplified a magnetic tape, magnetic disc, magneto-optical disc, paper tape, memory card, and the like. Among these apparatuses, the memory card is widely used for its comparatively high speed of transfer rate. Moreover, this memory card is built in a still image pickup apparatus (so-called still camera) and in a camera of a video tape recorder, so as to be used as a storage apparatus for recording a pickup information. The memory card includes memory means such as a semiconductor integrated circuit embedded in a case made from, for example, a synthetic resin. As the semiconductor integrated circuit, a flash memory (electrically erasable type programmable ROM (read only memory)) or the like is used. In the memory apparatus such as the aforementioned memory card, a data management is carried out by way of a so-called distributed management method or a collected management method. The distributed management method is realized as follows. Memory means for storing data in a storage apparatus is divided into data erase units such as blocks, and for each of the blocks there is provided a block management information such as a block flag, a logical address, and a linkage information, which are distributed and created for the respective blocks. Hereinafter, such management information items will be referred to as a distributed management information. In the distributed management method, when an electronic apparatus is activated for carrying out a data read-out and/or write-in from/to the aforementioned storage apparatus, firstly, the electronic apparatus collects the distributed management information items distributed in the respective blocks of the storage means and stores them into storage means of the electronic apparatus, so as to create a collected management table which enables to carry out an all-at-once management of the storage means of the storage apparatus, thus carrying out the data of the storage apparatus. In a case when this distributed management method is used, upon modification of a data in the respective blocks in the storage means of the storage apparatus by a signal transmitted from the electronic apparatus, the distributed management information is also modified. Consequently, each time when the electronic apparatus is activated as has been described above, the latest distributed management information items are collected from the respective blocks of the storage means in the storage apparatus, so as to create a management table in the storage means of the electronic apparatus. That is, according to this distributed management method, for example, even if any of the blocks in the storage means in the storage apparatus is destroyed, upon next activation of the electronic apparatus, the distributed management information items excluding that of the destroyed block are collected, so as to create a collected management table in the storage means of the electronic apparatus. Consequently, in the distributed management method, even if any of the blocks in the storage means of the storage apparatus is destroyed, it is possible to carry out a data write-in and/or data read-out to/from the blocks not destroyed. That is, the distributed management method is comparatively unsusceptible to destruction because there will be no such case that write-in and/or read-out cannot be carried out to/from the entire storage means. However, if the aforementioned distributed management method is applied to a storage apparatus having a large capacity and a plenty of blocks, when activating an electronic apparatus for carrying out a data write-in and/or read-out to/from the storage apparatus, it takes quite a time to create a collected management table in the electronic apparatus. Thus, activation of the electronic apparatus requires a plenty of time, preventing the high-speed processing. The other method, i.e., the collected management method is realized as follows. The management information items such as a block flag, logical address, and linkage information of respective blocks in storage means of the storage apparatus is stored in a single place in the storage means, and a management information is created for all-at-once management of the data of the respective blocks. Hereinafter, such a management information will be referred to as a collected management information. When the electronic is activated for carrying out a data read-out and/or write-in from/to the aforementioned storage apparatus, the electronic apparatus reads out the aforementioned collected management information so as to create a collected management table in the storage means of the electronic apparatus, thus carrying out management of the data of the storage apparatus. In a case when this collected management method is employed, upon activation of an electronic apparatus for a data write-in and/or data read-out to/from the storage apparatus, what is necessary for the electronic apparatus is to read out the collected management information, thus enabling to carry out the activation of the electronic apparatus in a short period of time, which in turn enables to realize a high-speed processing. However, when carrying out management of a data of a storage apparatus by the aforementioned collected management method, if the collected management information in the storage means of the storage apparatus is destroyed, it becomes impossible to carry out a data write/in and/or read-out to/from the entire storage means. That is, this method is not tolerant against the data destruction. Moreover, according to the collected management method, each time a data of respective blocks is modified in the storage means of the storage apparatus, the entire collected management information need be modified for data consistency between the collected management information and each of the blocks. In order to rewrite a plenty of blocks, a plenty of time is required for modifying the collected management information, thus preventing a high-speed processing. From US-A-5 479 609 is known a solid state peripheral storage device having a redundant mapping memory algorithm for mapping defective sectors, wherein a mapping memory which receives an address from a computer system provides a mapping to Physical Sector Number (PSN) data which address memory units. SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide a data management apparatus, a data management method and a recording medium which are tolerant against destruction and enable a high-speed processing of a data. This object is achieved by a data management apparatus, a data management method and a recording medium according to the enclosed independent claims. Advantageous features of the present invention are defined in the corresponding subclaims. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram showing a configuration of a memory card system according to the present invention. Fig. 2 is a block diagram showing a specific configuration of a memory card of the aforementioned memory card system. Fig. 3 explains a block configuration of a flash memory of the aforementioned memory card. Fig. 4 explains contents of a distributed management information of one page of a block of the aforementioned flash memory. Fig. 5 explains contents of a distributed management information used as an additional information. Fig. 6 explains a configuration of a collected management file. Fig. 7 explains contents of an OS header of the aforementioned collected management file. Fig. 8 explains contents of a file header in the aforementioned header. Fig. 9 explains contents of a system entry list in the aforementioned header. Fig. 10 explains contents of system information in the aforementioned header. Fig. 11 explains contents of a bit map table of the of the data according to the distributed management information, in a collected management information storage area. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram showing a configuration of a memory card system according to the present invention. Fig. 2 is a block diagram showing a specific configuration of a memory card of the aforementioned memory card system. Fig. 3 explains a block configuration of a flash memory of the aforementioned memory card. Fig. 4 explains contents of a distributed management information of one page of a block of the aforementioned flash memory. Fig. 5 explains contents of a distributed management information used as an additional information. Fig. 6 explains a configuration of a collected management file. Fig. 7 explains contents of an OS header of the aforementioned collected management file. Fig. 8 explains contents of a file header in the aforementioned header. Fig. 9 explains contents of a system entry list in the aforementioned header. Fig. 10 explains contents of system information in the aforementioned header. Fig. 11 explains contents of a bit map table of the aforementioned collected management file. Fig. 12 explains contents of an address conversion table of the aforementioned collected management file. Fig. 13 explains contents of a linkage information table of the aforementioned collected management file. Fig. 14 is a flowchart showing a processing executed when a host computer is started. Fig. 15 is a flowchart showing a processing executed when the host computer is started. Fig. 16 is a flowchart showing a processing of a data write or a data erase. Fig. 17 shows an external perspective view of a memory card according to the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT hereinafter, description will be directed to embodiments of the present invention with reference to the attached drawings. The present invention is applied, as shown in Fig. 1 for example, to a memory card system 1 including a host computer 10 and a memory card 20. It should be noted that here explanation will be given on a case of writing a video data transmitted from a host computer, to a memory card, but the same applies to a case of other data including an audio data. As shown in Fig. 1, the aforementioned host computer 10 includes: a hard disc drive (hereinafter, referred to as HDD) for storing a video data of a still image and an audio data; a RAM (random access memory) 12 for temporarily storing and reading out a video data and the like from the HDD 11; a display interface (hereinafter, referred to as display I/F) 13; a display 14 for displaying an image according to the video data supplied via the display I/F 13; a serial interface (hereinafter, referred to as a serial I/F) for carrying out a data transmission and reception via three lines with the memory card 20; a bus 16; a CPU (central processing unit) 17 for the entire system control; and a ROM (read only memory) 18 which contains a program data for controlling the CPU 17. The RAM 12, for example, via the bus 16, temporarily stores an audio data and a video data stored in the HDD 11 and, when required, supplies the video data via the bus 16 to the serial I/F 15. The display 14 is supplied with the video data read out from the HDD 11 via the bus 16 and the display I/F 13 as well as video data from the memory card 20, so as to display a still image according to these video data. The serial I/F 15 transmits a video data to the memory card 20 and receives a video data from the memory card via the three lines. More specifically, via a first line, the serial I/ F 15 transmits a video data and a control data for writing to the memory card 20 and receives a video data which has been read out from the memory card 20. Via a second line, the serial I/F 15 outputs a status signal indicating a switched state according to a switching between a video data and a control data in the first line. Furthermore, via a third line, the serial I/F 15 transmits a serial clock SCLK for transmitting the aforementioned control data and video data. The CPU 17 controls read-out of a video data from the RAM 12 and the HDD 11 and write-in of a video data into the RAM 12 and the like as well as controls transmission and reception of a video data to/from the memory card 20. For example, the CPU 17 issues a data write-in to the memory card with specification of an address. As shown in Fig. 2, the memory card 20 in the present embodiment includes: a control IC 21 for receiving a video data and a control data from the aforementioned host computer 10; and a flash memory (electrically erasable type programmable ROM (read only memory)) 22 as storage means for storing the video data received. The control IC 21, for specifically, includes: a serial/parallel - parallel/serial interface sequencer (hereinafter, referred to as a sequencer) 31; a page buffer 32 for temporarily storing a video data from the sequencer 31; a flash interface sequencer (hereinafter, referred to as a flash I/F sequencer) 33 for supplying the flash memory 22 with a video data form the page buffer 32; an ECC encoder/decoder 34 for carrying out an error correction; a command generator 35 for generating a predetermined control command; a configuration ROM (read only memory) 36 containing a version information and the like; and an oscillator 37 for supplying a clock to respective circuits. The sequencer 31 is connected via the aforementioned first to third lines to the serial I/F 15 of the host computer 10. Consequently, the sequencer 31 is supplied with a status signal and a serial clock SCLK as well as a serial DIO consisting of a video data and control data from the host computer 10. The sequencer 31 converts the serial DIO supplied from the host computer 10, into a parallel data in synchronization with the aforementioned serial clock SCLK. Among the parallel data, the sequencer 31, for examples, supplies a control data to the command generator 35, and a video data to the pager buffer 32. The pager buffer 32 is a buffer memory for storing each page of the video data supplied from the sequencer 31. The video data stored in the page buffer 33 is added with an error correction code by the ECC encoder/decoder 34. The pager buffer 32 supplies one page of video data having the error correction code, via the flash I/F sequencer 32 to the flash memories 22a to 22d. Thus, the video data from the host computer 10 is written in the flash memories 22a to 22d. Moreover, a video data read out from the flash memories 22a to 22d is supplied via the flash I/F sequencer 33 to the pager buffer 32. The pager buffer 32 stores the video data from the flash I/F sequencer 33. Here, the ECC encoder/decoder 34 carries out an error correction processing according to the error correction code added to the data stored in the page buffer 32. The page buffer 32 reads out page after another of the data which error has been corrected and supplies the data to the sequencer 31. The sequencer 31 converts the parallel video data supplied from the page buffer 32, into a serial data DIO which is transmitted to the aforementioned host computer 10. The command generator 35, according to a control data form the sequencer 31, generates a control command. Moreover, the command generator 35 generates a Busy command (hereinafter, referred to as a busy signal) indicating that a video data is being written into the flash memory 22 or a video data is being read out from the flash memory 22, and transmits the command via the sequencer 31 to the host computer 10. When the video data write-in or the data read-out is complete, the command generator 35 generates a Ready command (hereinafter, referred to as a ready signal) and transmits the command via the sequencer 31 to the host computer 10. The host computer receives the busy signal and the ready signal so as to recognize the operation state of the memory card 20. The configuration ROM 36 contains a version information and an initial value information of the memory card 20. Consequently, when a connection is made between the host computer 10 and the memory card 20, the command generator 35, firstly, reads out the aforementioned version information and the like from the configuration ROM 36 via the sequencer 31, and according to this information, generates a predetermined command, so as to carry out a predetermined initialization of the memory card 20. Here, the aforementioned flash memory 22 is a NAND type. as shown in Fig. 3, this flash memory 22 is consists of a plurality of blocks including a boot area of 2 blocks, a data area made from a plurality of blocks, and an area having a collected management information (collected management file) over a plurality of blocks. The boot area includes a boot block and a boot block backup, each in a single block. The boot block is a block containing a first data to be read out, for example, an address of a block containing a data for identifying the block and a collected management information. Moreover, the boot block backup is a copy of the boot block so as to be used, for example, when the boot block is destroyed. The data area is used to store various data such as a video data and an audio data. The area containing a collected management information stores a collected management information consisting of data for management of information required for access. Here, each of the blocks consists of a predetermined number of pages, each page (=528 bytes) consisting of a main data area for storing a main data of 512 bytes and a redundant area of 16 bytes. The redundant area stores a distributed management information indicating the storage stage of the page and the like. Fig. 4 shows a distributed management information of each page including: block enabled/disabled information (1 byte); block flag (1 byte); block end flag (4 bytes); reference flag (4 bits); management flag (1 bytes); logical address (2 bytes); linkage address (2 bytes); format reserve (3 bytes); distributed information ECC (2 bytes); and data ECC (3 bytes). The "block enabled/disabled information" is an information indicating whether the block is in a usable state. For example, if the block is destroyed and cannot be used, the "block enabled/disabled information" is overwritten, so as to indicate that the block cannot be used. The "block flag" indicates that no data has been written in the block, i.e., the block is not in use; or the block is used as a file head; or the block is used by other than a file head; or when the block has become unnecessary because of erase or rewrite, the block is set to a used state so as to be erased later. The "block end flag" indicates whether the block is an end block when a plurality of blocks constitute one file. It should be noted that when the "block end flag" indicates that the block is an end block, the "linkage address" becomes invalid even if specified. The "reference flag" is a flag specifying reference of an additional information which will be detailed later. This additional information exists on the last page of the block. The "management flag" is an information of 1 byte. Three bits (bits 2 to 0) of the one byte is stored in a collected management information table, whereas the remaining 5 bits are not stored in the collected management table but are used for an error correction processing and the like. The "logical address" indicates a logical address of the block. The "linkage address" indicates a logical address of a block to be linked with this block. It should be noted that when the block is already known to be an end block, the "block end flag" is turned on, so that "0xffff" is set is in the "linkage address". When this block is not known whether to be an end block, a logical address is assigned and set in the "linkage address". When this block is to become an end block, overwrite is executed and the "block end flag" is turned on. The "format reserve" is an information of 3 bytes for use as a reserved area. The "distributed information ECC" is used for correcting an error of the "management flag", "logical address", "linkage address", and the "format reserve". The "data ECC" is used for correcting a an error of a data other than the distributed management information. It should be noted that a distributed management information on the last page of each block is used as an additional information. As shown in Fig. 5, the additional information includes an overwrite area and an additional management information area. The overwrite area is identical to the aforementioned distributed management information. The additional management information area includes: identification number (1 bytes); valid data size (2 bytes); and format reserve (5 bytes). The "identification number" is used for rewriting a file, so as to identify an original file and a destination when updating by using an identical logical block. When a new logical address is used, "0" is written, and the value is incremented when update is executed. The "valid data size" indicates a size of a valid data within the block. For example, if the block has no empty area, "0xffff" is written and the "reference flag" is turned on, describing the block valid data size - 1. Moreover, a collected management information is constituted according to distributed management information of respective blocks. As shown in Fig. 6, the distributed management information consists of: a header containing a start position information for searching an empty area in respective blocks of the flash memory 22; a bit map table, an address conversion table, and a linkage information table. The header includes an OS header, file header, system entry list, and system information. Fig. 7 shows the OS header having: file ID (2 bytes); file version (2 bytes); file size (4 bytes); number of blocks in use (2 bytes); number of links (1 bytes); date (8 bytes); manufacturer/model code (4 bytes); initial loading directory number (2 bytes); number of keywords loaded (1 byte); keyword character code (1 byte); keyword character string (32 bytes); file name (11 bytes); 0 reset reserve (4 bytes); and individual data (32 bytes). The "file size" indicates the entire size of the collected management file in the number of bytes. The "number of blocks in use" indicates the number of blocks using the collected management file in the flash memory 22. The "number of links" indicates the number of links when the collected management file is in a reference relation with (linked to) other files. The "date" indicates a data when the collected management file is created or updated. The "manufacturer/model code" indicates the manufacturer and the model of an apparatus which has written the collected management file into the memory card 20. The "initial loading directory number" is described as "0xffff" without any definition. The "number of keywords loaded" and the "keyword character code" are set to "0". The "keyword character string" is all set to "0". The "file name" is used when carrying out management of the collected management file, and not used within the memory card 20. The "0 reset reserve" is always set to 0 when executing a rewrite. The "individual data" is all "0". Fig. 8 shows the file header including: specification identification data (8 bytes); file specification identification data (8 bytes); file ID (2 bytes); file version (2 bytes); date of application created (8 bytes); date of application updated (8 bytes); creation manufacturer/model code (4 bytes); updating manufacturer/model code (4 bytes); 0 reset reserve (16 bytes); number of data entries (1 byte); number of tables (1 bytes); character code (1 byte); title character string (128 bytes); and a reserved area (48 bytes). The "specification identification data" indicates that the flash memory 22 stores a collected management file according to a predetermined specification. The "file specification identification data" indicates that the collected management file has been created according to the aforementioned predetermined specification. the "file ID" indicates a file type, and the same is contained in the OS header. The "file version" indicates a version number. The "date of application created" indicated a date when the collected management file is created, whereas the "date of application updated" indicates the date of updating. The creation manufacturer/model code" indicates the manufacturer and the model name which has created the collected management file, whereas the "updating manufacturer/model code" indicates a manufacturer and model name which has updated the collected management file. The "number of data entries" indicates a number of entries which will be detailed later, and the number is 3 in a collected management file. The "number of tables" indicates a number of data items in a table data area, and the number is "0" here. The "character code" indicates an input character with a predetermined code number, and it is "Oxff" here. The "title character string" indicates title characters, which are all "Oxff". Fig. 9 shows the system entry list consisting of 4 sets of 12-byte data (entries), each set including: start address (4 bytes); data size (4 bytes); data type ID (1 byte); and reserved (3 bytes). In other words, the system entry list executes management of up to four entries. It should be noted that a collected management file, excluding a header, has a bit map table, an address conversion table, and a linkage information table, and accordingly, contains an information required for management of these three tables. For example, for a bit map table, the "start address" indicates an address of the start position of the bit map table, and the "data size" indicates a number of blocks required for the bit map table. The "data type ID" describes "0x03" indicating a bit map table. It should be noted that an identical configuration is used for the address conversion table and the linkage information table. Fig. 10 shows a configuration of the system information including: empty block search position (2 bytes) and an reserved area (94 bytes). The "empty block search position" serves to store a search position of an empty block. On the other hand, as shown in Fig. 11, the bit map table is used for management of in-use state of the flash memory 22 on block basis and contains a head information other attribute information for management of blocks. More specifically, as shown in Fig. 11, the bit map table contains in the physical address order of blocks, an 8-bit information consisting of: enabled/disabled (1 bit); block flag (2 bits); block end flag (1 bit); reference flag (1 bit); system flag (1 bit); read only (1 bit); and marking (1 bit). The "enabled/disabled", "block flag", "block end flag", and "reference flag" are respectively identical to "block enabled/disabled information", "block flag", "block end flag" of the distributed management information. That is, "enabled/disabled" indicates whether the block can be used. The "block flag" indicates whether the block is not in use; used as a head block; used other than as a head block; in used and waiting for erase. The "block end flag" indicates whether the block is continuous to another block in one file or an end The "reference flag" indicates whether an additional management information contains an item to be referenced. It should be noted that the "system flag" indicates whether the block is for an ordinary application or a block for the system. The "read only" indicates whether the block is enabled for read-out/write-in or the block is dedicated for read-out. The "marking" indicates whether the block is an ordinary block or block for marking, and in a case of marking, a reference of the distributed management information is specified. Fig. 12 shows a configuration of the address conversion table, containing in the logical address order of blocks, physical address of respective blocks. That is, in the address conversion table, block physical addresses are described so as to correspond to the logical addresses written in the distributed management information of the respective blocks. This enables to carry out all-at-once management of conversion between the physical address and the logical address. It should be noted that "0xffff" is described for the physical address of a block not in use. Fig. 13 shows a configuration of the linkage information table which contains, in the block logical address order, a linkage address of the distributed management information corresponding to respective blocks as the "linkage logical address". It should be noted that the "linkage logical address" is described as "0xffff" if the block is a final block, and as "0x0000" if the logical address is not in use. Moreover, the logical address 0 is dedicated for a route directory and linkage to this is inhibited. In the memory card system 1 having the aforementioned configuration, when the CPU 17 of the host computer 10 is started, as shown in Fig. 14, the CPU 17 reads out information of the boot block from the flash memory 22 of the memory card 20 and determines whether a collected management information is contained (step ST1 and step ST2). It should be noted that in this process, the memory card 20 is also substantially activated, but here, explanation will be given along the processing in the host computer 10. If the CPU 17 decides that a collected management information is contained, the collected management file is read from the flash memory 22 into the RAM 12 (step ST3). Furthermore, the CPU 17 decides whether the collected management information which has been read in is valid (step ST4). If the collected management information is decided to be valid, the CPU 17 creates a collected management table in the RAM 12 so as to be used for memory management (step ST5). This collected management table is used for management of data in the flash memory 22. Thus, if no error is contained in a collected management information of the memory card 20, the CPU 17 of the host computer 10, when activated, can read out the collected management information so as to carry out management of the data in the flash memory 22. This enables to carry out a high-speed processing in a short time after activation. On the other hand, if the CPU 17, in step ST2, decides that no collected management information.is contained, or if in step ST4, decides that the collected management information is not valid, the CPU 17 collects distributed management information stored in the distributed management information areas of respective blocks, so as to constitute a collected management information by creating a collected management table within the storage means (step ST6). More specifically, step ST6 executes a subroutine processing shown in Fig. 15. The CPU 17 of the host computer 10 initializes the memory table for storing a collected management information (step ST11) and loads an initial defective address of the boot block as unusable in the bit map table, as well as an unusable block preceding the boot block as unusable (step ST12) Blocks after the boot block are successively checked and it is decided whether check of all the blocks is complete (step ST13). When it is decided that check of all the blocks is not complete, the CPU 17 reads out a distributed management information of one block from the flash memory 22 and stores it in the RAM 12 (step ST14). After this, it is decided whether an error is contained in the distributed management information which has been read out (step ST15). If any error is found, it is loaded in the bit map table that an error is caused in the block (step ST16). Moreover, it is decided that no error is contained in the distributed management information which has been read out, the CPU 17 loads the management flat of the distributed management information, in the bit map table, describes a physical address of the block in the corresponding logical address of the address conversion table, and further describes a linkage information in the corresponding logical address of the linkage information table (step ST17). Thus, a content of the distributed management information of the block is described in the bit map table, in the address conversion table, and in the linkage information table. Moreover, the CPU 17 also checks whether any dual logical address or linkage address having no destination is contained (step ST17). After the CPU 17 has described a content of a distributed management information of the block in the bit map table, in the address conversion table, and in the linkage information table in the aforementioned steps ST13 to ST15 and ST17, control is returned to step ST13 for describing contents of distributed management information of other blocks in the bit map table and the like. when read-out of distributed management information of all the blocks is complete, i.e., check of all the blocks is complete (step ST13), the CPU 17 adds a 512-byte header to the data consisting of the bit map table, the address conversion table, and the linkage information table, so as to create a collected management file in the RAM 12, thus completing the creation of the collected management information. Thus, when no collected management information is present or when a collected management information is not valid, the distributed management information is used to create a collected management file. In this process, the CPU 17 may re-store the collected management table in the RAM 12 as a collected management information in the collected management information storage area of the flash memory 22 during a period when no predetermined computation processing is to be carried out such as upon power OFF. Thus, the CPU 17 can execute management of data according to the collected management information stored in the RAM 12 with the flash memory 22, which enables to carry out management of a data read-out or write-in easily and at a high speed. Furthermore, when no collected management information is present or a collected management information is not valid, it is possible to read out a distributed management information from the flash memory 22, so as to create a collected management information to be used for management. Consequently, even when a distributed management information is destroyed, it is possible to execute a data management, which increases the reliability. More specifically, by creating a bit map table, the CPU 17 can recognize an unusable block according to the bit map table of the collected management information, without searching the distributed management information of all the blocks. This enables to execute a data write-in at a higher speed. Moreover, it is possible to know that each of the blocks is a head block or an intermediate block or a block containing no data. This also enables to execute a file write-in or read-out at a high speed. Moreover, by creating an address conversion table for example, the CPU 17 can execute conversion from a logical address to a physical address at a high speed, thus reducing the access time to the flash memory 22. Furthermore, by creating a linkage information logical address, the CPU 17 can easily recognize the blocks constituting a file and read out at a high speed a file consisting of a plurality of blocks. Next, description will be directed to a processing of the CPU 17 for writing a video data write into the memory card 20 with reference to Fig. 16. When writing a new data in the flash memory 22 or when erasing a data in the flash memory 22, the CPU 17 decides whether the collected management information stored in the RAM 12 is valid (step ST21). More specifically, it is decided whether a part of the collected management information need be modified according to the distributed management information corresponding to the new data. When the collected management information is decided to be valid, the CPU 17 executes a processing to invalidate the collected management information in the RAM 12 (step ST22) and writes a new video data in the flash memory 22 or a data modification processing such as erase of the video data already stored (step ST23). Note that if the collected management information is decided not to be valid in step ST21, a modification processing such as a video data write-in is executed (step ST23). The CPU 17 updates a part of the collected management information in the RAM 12 (step ST24) according to the distributed management information corresponding to the new video data which has been written in or the distributed management information of a block in which a video data or the like has been erased. At computation processing end such as immediately before power OFF, the CPU 17 writes the collected management information stored in the RAM 12 in the collected management information storage area of the flash memory 22 (step ST15). That is, when a data write-in or erase has caused modification in the collected management information, the CPU 17, according to the distributed management information of the written data or the like, updates the collected management. information, so that the collected management information is always matched with the distributed management information, thus assuring the reliability of the video data management. Moreover, by writing the obtained collected management information in the flash memory 22 at an appropriate moment, it is possible to execute other computation processing with a higher priority, thus enhancing the entire computation processing speed. It should be noted that the memory card in the present embodiment, for example, may have an external configuration as shown in Fig. 17 in a flat thin card shape made from a synthetic resin. In the aforementioned memory card 20, for example, an external terminal (not depicted) is formed at one side 2a in the longitudinal direction, so that the memory card 20 can be mounted on an electronic apparatus (not depicted) in the direction indicated by the arrow M in the figure. Moreover, in the aforementioned memory card 20, it is possible to form a lock cut-off portion at one side parallel to the mounting direction, for example, so that when the memory card 20 is mounted on an electronic apparatus (not depicted), a lock convex (not depicted) of the electronic apparatus is engaged with the lock cut-off portion so as to prevent removal of the memory card 20 from the electronic apparatus. That is, the memory card 20 in the present embodiment has both of a collected management information stored in a collected management information storage area and a distributed management information stored in a distributed management storage area of the flash memory 22 as storage means. By carrying out management of these information items according to the data management method of the present invention, when an error is detected in the collected management information, the host computer 10 searches respective distributed management information stored in the distributed management information storage area, so as to create a collected management information for use; and if the collected management information is destroyed, it is possible to easily create one. Thus, there is no such danger that the entire data read-out and/or write-in cannot be executed. That is, the system is tough for destruction. Furthermore, if a modification such as erase and rewrite is caused to the distributed management information stored in the distributed management information storage area in the flash memory 22 of the memory card 20, the host computer 10 updates the collected management information according to the modified distributed management information to be stored in distributed management information storage and stores the updated information in the collected management information storage area in the flash memory 22 of the memory card 20. Thus, there will be no difference between the distributed management information and the collected management information in the memory card 20. Furthermore, when the host computer 10 is activated next time, the host computer searches the aforementioned re-created and re-stored in the memory card as a collected management information, which enables to activate the host computer 10 in a reduced time, which in turn enables a high-speed processing. In a case when the re-storing processing of a collected management information by the host computer 10 in the memory card 20 is interrupted, it is assumed that no collected management information exists. In this case, upon activation of the host computer 10 next time, a processing is carried out, assuming that no collected management information is present. Moreover, in a case when a distributed management information is destroyed in the memory card 20, it becomes impossible to execute a data read-out and/or read-out from/to a corresponding block, but a damage of the memory card 20 as a whole can be minimized. It should be noted that the explanation above has been given on a case of a memory card for a serial interface, but the data management apparatus according to the present invention can also be used for a parallel interface.

Claims: A data management apparatus comprising: storage means (20) for storing arbitrary data in a data storage area (22a..22d) constituted by predetermined storage units, and storing in a distributed management information storage area a distributed management information for management of said arbitrary data on a predetermined storage unit basis; and storing in a collected management information storage area (22a..22d) a collected management information for all-at-once management of said data according to said distributed management information; and management means (10, 17) which determines upon activation whether said collected management information is valid, and if said collected management information is determined to be valid (ST4), management of said data is carried out according to said collected management information, and if said collected management information is determined to be invalid, management of said arbitrary data is carried out according to said distributed management information. A data management apparatus as claimed in Claim 1, wherein if said collected management information is not valid, said management means (10, 17) creates a collected management information from said distributed management information stored in said distributed management information storage area (22a..22d), and writes the created collected management information in said storage means (20). A data management apparatus as claimed in Claim 1 or 2, wherein when a new data is written in said data storage area (22a..22d) of said storage means (20), causing modification to a part of said collected management information, said storage means (20) updates said collected management information according to a distributed management information of the data written and writes said updated collected management information in said storage means (20). A data management apparatus as claimed in Claim 3, wherein when a predetermined data processing is executed, said management means (10, 17) writes said updated collected management information in said storage means (20) after said predetermined data processing is complete. A data management apparatus as claimed in any one of Claims 1 to 4, wherein said storage means (20) stores a distributed management information having a management flag for management of a storage state of said predetermined unit of data and a collected management information constituted by management flags of said predetermined storage units; and said management means (10, 17), according to said collected management information, carries out management of a data storage in said data storage area (22a..22d). A data management apparatus as claimed in any one of Claims 1 to 5, wherein said storage means (20) stores a distributed management information having a logical address of said predetermined storage unit and a collected management information constituted by a set of physical addresses of said predetermined storage units and corresponding logical addresses; and said management means (10, 17), according to said collected management information, executes conversion between a physical address and a logical address of said predetermined storage unit and reads out arbitrary data stored in said storage means (20) or writes arbitrary data into said storage means (20). A data management apparatus as claimed in any one of Claims 1 to 6, wherein said storage means (20) stores a distributed management information having a linkage information indicating that said predetermined storage unit is to be linked to another storage unit and a collected management information constituted by a set of linkage information items of said predetermined storage units; and said management means (10, 17), according to said collected management information, reads out from said storage means (20) arbitrary data stored in a data storage area (22a..22d) to which said predetermined storage unit is linked. A data management method comprising : a step (ST23) of storing arbitrary data in a data storage area (22a..22d) constituted by predetermined storage units; a step of storing in a distributed management information storage area (22a..22d) a distributed management information for management of said arbitrary data on a predetermined storage unit basis; a step (ST24, ST25) of storing in a collected management information storage area (22a..22d) a collected management information for all-at-once management of said arbitrary data according to said distributed management information; a step (ST4) of determining upon activation whether said collected management information is valid; and a step management of said arbitrary data according to said collected management information if said collected management information is determined (ST4) to be valid, or according to said distributed management information if said collected management information is determined (ST4) to be invalid. A data management method as claimed in Claim 8, wherein if said collected management information is not valid, a collected management information is created (ST6) from said distributed management information stored in said distributed management information storage area (22a..22d), and said created collected management information is stored. A data management method as claimed in Claim 8 or 9, wherein when new arbitrary data is written in said data storage area (22a..22d) of said storage means (20), causing modification (ST23) to a part of said collected management information, said collected management information is updated (ST24) according to a distributed management information of the data written and said updated collected management information is stored. A data management method as claimed in any one of Claims 8 to 10, wherein when a predetermined data processing is executed, said updated collected management information is stored in said storage means (20) after said predetermined data processing is complete. A data management method as claimed in any one of Claims 8 to 11, comprising: a step of storing a distributed management information having a management flag for management of a storage state of said predetermined unit of data and a collected management information constituted by management flags of said predetermined storage units; and a step of management of a data storage in said data storage area (22a..22d) according to said collected management information. A data management method as claimed in any one of Claims 8 to 12, comprising: a step of storing a distributed management information having a logical address of said predetermined storage unit and a collected management information constituted by a set of physical addresses of said predetermined storage units and corresponding logical addresses; and a step of conversion between a physical address and a logical address of said predetermined storage unit according to said collected management information, so as to read out arbitrary data stored in said storage means (20) or to store new arbitrary data. A data management method as claimed in any one of Claims 8 to 13, comprising: a step of storing a distributed management information having a linkage information indicating that said predetermined storage unit is to be linked to another storage unit and a collected management information constituted by a set of linkage information items of said predetermined storage units; and a step, according to said collected management information, of reading out from said storage means (20) arbitrary data stored in a data storage area (22a..22d) to which said predetermined storage unit is linked. A recording medium comprising: a data recording area (22a..22d) constituted by predetermined storage units in which arbitrary data are stored; a distributed management information storage area (22a..22d) in which a distributed management information for management of said arbitrary data on a predetermined storage unit basis is stored; a collected management information storage area (22a..22d) in which collected management information for all-at-once management of said arbitrary data according to said distributed management information are stored; thus said arbitrary data are recorded and/or reproduced in/from said data recording area (22a..22d) according to said collected management information if said collected management information is determined (ST4) to be valid, or according to said distributed management information if said collected management information is determined (ST4) to be invalid. A recording medium as claimed in Claim 15, said medium (20) storing a distributed management information having a management flag for management of a storage state of said predetermined storage unit of data; and a collected management information constituted by a set of management flags of said predetermined storage units. A recording medium as claimed in Claim 15 or 16, said medium (20) storing a distributed management information having a logical address of said predetermined storage unit; and a collected management information constituted by a set of physical addresses of said predetermined storage units and corresponding logical addresses. A recording medium as claimed in Claim 15, said medium (20) storing a distributed management information having a linkage information indicating linkage of said predetermined storage unit to another predetermined storage unit; and a collected management information constituted by a set of linkage information items of said predetermined storage units.

Inventors: HIRABAYASHI MITSUHIRO, NAKANISHI KENICHI, OKAUE TAKUMI, SASSA AKIRA, HIRABAYASHI, MITSUHIRO, NAKANISHI, KENICHI, OKAUE, TAKUMI, SASSA, AKIRA
Applicants: SONY CORP, SONY CORPORATION
Application year: 1998
Main classification: G06F11
IPC codes: G06F11, G11B20, G06F12, G11C29