EP0503417B1 - Method and means for verification of write data - Google Patents
Method and means for verification of write data Download PDFInfo
- Publication number
- EP0503417B1 EP0503417B1 EP92103531A EP92103531A EP0503417B1 EP 0503417 B1 EP0503417 B1 EP 0503417B1 EP 92103531 A EP92103531 A EP 92103531A EP 92103531 A EP92103531 A EP 92103531A EP 0503417 B1 EP0503417 B1 EP 0503417B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- write data
- port
- host
- write
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/2215—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test error correction or detection circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1008—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1076—Parity data used in redundant arrays of independent storages, e.g. in RAID systems
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/18—Error detection or correction; Testing, e.g. of drop-outs
- G11B20/1833—Error detection or correction; Testing, e.g. of drop-outs by adding special lists or symbols to the coded information
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/18—Error detection or correction; Testing, e.g. of drop-outs
- G11B20/1816—Testing
- G11B2020/183—Testing wherein at least one additional attempt is made to read or write the data when a first attempt is unsuccessful
Definitions
- This invention relates to the verification of write data in a storage means, for example in a fault tolerant disk drive array.
- Presently known systems for recording binary data typically include a host computer for processing data, one or more disk drives and a controller interfacing between the computer and the disk drives.
- a plurality of drives are configured in an array for recording and storing data.
- a disk array generally consists of a number of disk drives and one or more redundant drives.
- Fault tolerant disk arrays are used that allow failure of one or more disk drives in an array without loss of data. Such types of disk arrays are used when data availability is critical.
- fault tolerance is achieved by calculating simple parity for the system data and storing it on the redundant drive(s).
- the reconstruction of data for a bad block requires the existence of parity data for that block, knowledge in the controller of the location of the bad block, and no more than one bad data block per parity block.
- Typical controller architecture has two exposures to write data loss events, namely (1) an undetected failure of the controller data path function; and (2) an undetected failure in one of the drive data paths.
- Typical disk controllers protect against write data loss events by reading and checking the data just written. This form of "write verification" in disk controllers requires an additional revolution of the disks in order to perform the read operation, which constitutes a significant performance penalty and therefore is not generally attempted.
- guaranteed detection of a write failure in a drive data path is difficult to implement and rarely achieved in disk array systems.
- CRC cyclic redundancy check
- a verification system including a disk array that detects loss of write data or failure during the write mode without duplication of circuitry in the write and read data circuits.
- a system for verifying write data to be recorded in a storage means comprising:
- a method for verifying write data to be recorded in a storage means comprising the steps of:
- verification of write data is achieved by detection of an error in the controller data path (CDP) during a write operation in a fault tolerant storage means such as a disk array system.
- the CDP is separated into a write data path (WDP) and a read data path (RDP), which operate independently of each other.
- the RDP is enabled during a write operation to read output data from the WDP and to implement detection of data errors in the controller. If no error is detected in the write data exiting the WDP, we are assured of being able to subsequently read it because of the fault tolerance in disk drive data paths.
- cyclic redundancy check (HOST CRC) characters are generated and added to the host write data.
- the HOST CRC characters are used in two ways. First, they are regenerated and checked in the RDP during write operations as an overall check of the WDP processing of the host data block. Second, the HOST CRC characters are stored on the drives to be used on subsequent read operations as an overall check of the RDP as it rebuilds the host data block.
- the combined host data block and HOST CRC is divided into multiple data blocks by the WDP, one block per drive.
- the controller then generates additional cyclic redundancy check (PORT CRC) characters which are appended to each block and stored on the drives. The PORT CRC characters are regenerated during read operations and compared to the stored characters.
- the PORT CRC check can be used as a pointer to the failed data path.
- the read data can then be reconstructed from the other good disk drives in a well known manner.
- This feature provides fault tolerance on read operations.
- the blocks having write data with HOST and PORT CRC characters are fed to the ports of a plurality of disk drives, which includes a parity drive for processing redundancy data.
- error detection circuitry in the RDP checks the host data, redundant data, and the HOST CRC and PORT CRC characters to detect errors in the write data from the WDP.
- RDP error detection circuitry In a specific implementation of RDP error detection circuitry, there is no need for duplication of PORT CRC generating circuitry in the RDP thus simplifying the write verification system and reducing cost of manufacture and maintenance expense. Instead, the individual data blocks are checked by summing the contribution of each port. The resulting sum is checked and if a failure is indicated, the write operation is retried.
- a write verification system comprises a host computer 10 that processes binary data, and a controller 16 including a write data path (WDP) network 18 and a read data path (RDP) network 34.
- WDP write data path
- RDP read data path
- the WDP network 18 and RDP network 34 although connected, function independently to process write data and read data respectively.
- the RDP network 34 is enabled during the write mode to read output data from the WDP network 18.
- Host computer 10 provides blocks of host data to be passed to the controller 16 and to an array of disk drives D0-D3, DP for recording of the data.
- the computer 10 includes a generator 12 that generates a number of bytes of host cyclic redundancy check (HOST CRC) characters which are appended to each block of write data received at input terminal 14.
- HOST CRC generator 12 does not need to reside in the host computer, but could just as easily reside in the controller 16 and equivalent results would be achieved.
- the HOST CRC generator 12 is shown in more detail in Figure 4.
- the exclusive OR tree 70 and register 72 are operated in a well known manner such that the input data is divided by a generator polynomial and the remainder is computed.
- the multiplexer 74 is switched so as to append the remainder (which is now known as HOST CRC) onto the host data out of 78. This cycle is repeated for each block of host data.
- the write data block with the appended HOST CRC characters is directed to the WDP network 18.
- the block of input data from the host computer 10 and the HOST CRC characters are divided by a data sequencer 20 into a plurality of subblocks of port data, preferably of equal size.
- four data subblocks are passed respectively to PORT CRC generators 24a,b,c,d.
- the write input data from the host computer 10 is channeled to a parity accumulator 22 that calculates the redundancy data for the parity port, which is subsequently passed to PORT CRC generator 24p.
- PORT CRC characters are appended to the data and parity subblocks by PORT CRC generators 24a,b,c,d,p.
- the PORT CRC generators are implemented with the same type of circuit as the HOST CRC generator circuit shown in Figure 4.
- the byte is also passed through to the corresponding WDP holding register 26a,b,c,d,p.
- two PORT CRC bytes are immediately transferred following the last port data byte to the respective WDP holding register 26.
- the data and parity subblocks are transferred from the WDP holding registers to the respective disk drives D0-D3,Dp.
- the purpose of each holding register 26a,b,c,d,p is to provide temporary storage of data before the data can be sent to the respective disk drive.
- each of four consecutive host data bytes are summed by modulo 2 summation in the parity accumulator 22, and the resulting sum is fed to PORT CRC generator 24p.
- the first group of eight bytes of host write data may be designated as 01,02,03,04,05,06,07,08.
- the first byte 01 of 8 bits is transferred to PORT CRC generator 24a, WDP holding register 26a and, simultaneously to an exclusive OR (XOR) logic circuit 50 of the accumulator 22, as illustrated in Fig. 2.
- the byte value 01 is summed with the initial value 00 to produce a resultant 01.
- the value of the byte in the parity accumulator 22 is transferred to PORT CRC generator 24p and register 26p.
- These five bytes, 01-04 and the parity byte represent the first rank of data.
- a port rank. corresponds to the set of bytes over which the parity byte is calculated, and the parity byte itself.
- the accumulator 22 is reinitialized to 00 and the above sequence is repeated for every four bytes of input data.
- the parity byte 0C is then transferred to PORT CRC generator 24p, holding register 26p, and the accumulator is reinitialized to 00.
- the second rank therefore consists of the five bytes 05, 06, 07, 08, and the parity byte 0C.
- the WDP Data Sequencer 20 divides the host data block including HOST CRC into fourths and the parity port data is calculated from the host data.
- a system clock (not shown) is used to time the sequential transfer of the data bytes or subblocks.
- the PORT CRC characters that are generated in PORT CRC generators 24a,b,c,d,p are passed respectively to WDP holding registers 26a-d,p.
- the data and parity subblocks with appended HOST CRC and PORT CRC characters are then fed through terminals 28a-d,p to PORT0-PORT3 and PORTP to respective data disk drives D0-D3 and parity disk drive Dp for storage.
- the data subblocks and redundant or parity subblock are fed back through terminals 30a-30d,p to the network 34 constituting the read data path (RDP).
- the port data and parity data are provided to holding registers 32a-d,p. Each holding register provides temporary storage of data.
- the stored data contents of the RDP holding registers 32a-d,p are passed to a 5 byte XOR summer 36 to produce a sum check across each rank, bytes 0-3,p for the entire data block.
- the output of the summer 36 is directed to a zero check circuit 38 which checks the result of the summing operation to be equal to 0 for each rank, bytes 0-3,p. If the sum is non-zero an error flag is set in a status register of the controller 16.
- the microprocessor 48 has access to the error flag. If the error flag is set after the write operation, the transfer is considered incorrect and the microprocessor initiates a retry. It should be noted that five 8-bit input data lines are connected between the outputs of the holding registers 32a-d,p and the inputs to xor summer 36, although Fig. 1 shows single lead lines for convenience and simplicity.
- Fig. 3 an example of detection circuitry comprising the xor summer 36 and zero check circuit 38 is illustrated.
- Five data lines, each carrying 8-bit data bytes, are applied to xor circuits 54, 56 and 58.
- Xor circuit 58 receives an 8-bit output from xor 56 as well as the 8- bit data byte from the holding register 32.
- the outputs of xor circuits 54 and 58 are supplied to xor circuit 60, which provides an 8-bit byte to the zero check circuit 38, having a zero detect circuit 62 and flip-flop 64.
- the output from the flip-flop 64 is an error flag which is set if the zero check circuit detects a non-zero result.
- the microprocessor 48 has access to the error flag. If the error flag 44 is set after the write operation, the transfer is considered incorrect and the microprocessor initiates a retry.
- the port subblocks provided to the RDP holding registers 32a-d are also provided to an RDP data sequencer 40 that sequentially channels the data subblocks to a HOST CRC check circuit 42 under control of the system clock.
- the data is reassembled in the RDP data sequencer 40 in the same sequence as it was provided by the host computer to the WDP. The sequence must be the same in order to regenerate the correct HOST CRC in the check circuit 42.
- the regenerated CRC value is compared to the HOST CRC characters. If the regenerated value is not the same as the HOST CRC, an error flag 46 is set in a status register of the controller 16.
- the microprocessor 48 has access to the error flag. If the error flag is set after the write operation, the transfer is considered incorrect and the microprocessor initiates a retry.
- HOST CRC check circuit 42 performs the same function as the HOST CRC generator 12 as illustrated in Figure 4 with the exception that the HOST CRC characters appended to the host data block are included in the checker's calculation. Also the result of the calculation is checked to be equal to zero at the end of the host data block.
- a failure in the write data path causes the overall checks to fail in the read data path and the write operation is then immediately retried. If the RDP does not detect an error in the write data then the data and appended check characters are deemed to be fault tolerant. Fault tolerance allows any single drive path or drive to fail without loss of host data.
- a simple and efficient sum check of the PORT CRC characters is provided by using the linear properties of CRC polynomial operations.
- the sum of the individual data PORT CRC's and the parity PORT CRC will always be zero.
- the parity PORT CRC is generated from the parity port data and not from the sum of the individual data PORT CRC characters.
- PORT CRC DO(x), D1(x), D2(x), D3(x)- one for each port data subblock.
- the remainder of the division operations are the PORT CRC's appended to the data polynomials.
- Fig. 5 illustrates an example of a 14 byte HOST DATA block with two bytes of HOST CRC appended, as follows:
- the HOST DATA block is divided into four DATA subblocks.
- the parity subblock is generated from the HOST DATA.
- the parity subblock PORT CRC is calculated independently of the other PORT CRC characters.
- the first rank of data consists of the HOST DATA block bytes 01, 02, 03, 04 and parity subblock byte 04.
- PORTO data subblock consists of the host data block bytes 01, 05, 09, 0D, and PORT CRC bytes 22 and 6A as generated by the PORT CRC generator 24a.
- Each byte of the parity subblock is the xor sum across the corresponding data subblocks excluding the PORT CRC ranks 5 and 6.
- the parity PORT CRC as generated by 24p is calculated from the parity port data bytes 04, 0C, 04, 11.
- an improved write verification system wherein a sum check of the port CRCs takes advantage of the linear properties of CRC polynomials by individually summing the data port CRCs and the parity port CRC as a means to check the correct generation of port CRCs while simplifying the hardware design.
- the disclosed embodiment affords the checking of data blocks simultaneously with the recording and storage of data in a fault tolerant disk drive array.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Detection And Correction Of Errors (AREA)
Abstract
Description
- This invention relates to the verification of write data in a storage means, for example in a fault tolerant disk drive array.
- Presently known systems for recording binary data typically include a host computer for processing data, one or more disk drives and a controller interfacing between the computer and the disk drives. With some systems that process relatively large amounts of data, a plurality of drives are configured in an array for recording and storing data. A disk array generally consists of a number of disk drives and one or more redundant drives. Fault tolerant disk arrays are used that allow failure of one or more disk drives in an array without loss of data. Such types of disk arrays are used when data availability is critical. In one method, fault tolerance is achieved by calculating simple parity for the system data and storing it on the redundant drive(s). The reconstruction of data for a bad block requires the existence of parity data for that block, knowledge in the controller of the location of the bad block, and no more than one bad data block per parity block.
- It is well known that the most common failure events which occur with the use of fault tolerant disk arrays are recoverable. Since fault tolerant disk arrays are employed for critical data applications, less common failure events affecting data integrity assume a much higher importance as compared to nonfault tolerant disk systems. Thus controller failures, even though much less likely than drive failures, may lead to data loss that is unacceptable. Although controller failure during a read operation leads to the lack of availability of system data, there is no permanent loss of the data. The faulty controller can be replaced and the data recovered. On the other band, a controller failure during a write operation, if undetected, can cause a corruption of the system data on the drives. Such corruption of data would not be detected until the bad block is subsequently read. If there is a significant time lag between the write and read operations, additional bad blocks could be written in the interim. In a worst case situation, a controller failure during a write operation may never be detected in the controller. For example, if the controller scrambles data when writing to the disks and parity data is generated for the scrambled data, an undetectable and uncorrectable write failure would occur.
- Typical controller architecture has two exposures to write data loss events, namely (1) an undetected failure of the controller data path function; and (2) an undetected failure in one of the drive data paths. Even though the drive data paths are fault tolerant in a disk array, a bad block must be detectable in order for it to be correctable. Typical disk controllers protect against write data loss events by reading and checking the data just written. This form of "write verification" in disk controllers requires an additional revolution of the disks in order to perform the read operation, which constitutes a significant performance penalty and therefore is not generally attempted. Furthermore, guaranteed detection of a write failure in a drive data path is difficult to implement and rarely achieved in disk array systems.
- One well known error detection approach uses cyclic redundancy check (CRC) characters for detection of data path errors. Presently known disk systems require CRC generation circuitry and separate additional independent circuitry for detecting data errors. This duplication of circuitry is relatively expensive. It is highly desirable to provide integrity checking in the controller during the write mode using simplified circuitry.
- Accordingly, it is desirable to achieve verification of write data for fault tolerant disk arrays without the performance penalty incurred in typical disk controllers due to reading the previously written data.
- It is also desirable to provide a verification system that detects loss of write data or failure in the controller data path during a write operation.
- Furthermore, it is desirable to provide a verification system including a disk array that detects loss of write data or failure during the write mode without duplication of circuitry in the write and read data circuits.
- According to a first aspect of the present invention there is provided a system for verifying write data to be recorded in a storage means, comprising:
- a host interface for providing input blocks of write data;
- a means for generating host cyclic redundancy check characters appended to said write data blocks; and
- a controller coupled to said interface, said controller including a write data path network and a read data path network coupled to the output of said write data path network;
- said write data path network including means for dividing said data blocks into subblocks to be passed through respective ports, and port generator means for appending port cyclic redundancy check characters to said data subblocks;
- said read data path network including first checking means for checking said host cyclic redundant check characters and second checking means for checking said port cyclic redundancy check characters, said read data path network being enabled during a write operation in order to read the write data from the output of the write data path network, so as to detect errors in the write data and initiate a retry operation upon detection of such errors.
- According to a second aspect of the present invention, there is provided a method for verifying write data to be recorded in a storage means, comprising the steps of:
- providing input blocks of write data;
- generating host cyclic redundancy check characters appended to said write data blocks;
- in a write data path network, dividing said data blocks into subblocks to be passed through respective ports, appending port cyclic redundancy check characters to said data subblocks, and outputting the write data including said host cyclic redundancy check characters and said port cyclic redundancy check characters through said ports to said storage means;
- in a read data path network which is enabled during a write operation, reading the write data output from the write data path network, and checking said host cyclic redundancy check characters and said port cyclic redundancy check characters, so as to detect errors in the write data; and
- initiating a retry operation upon detection of an error in the write data.
- Thus, verification of write data is achieved by detection of an error in the controller data path (CDP) during a write operation in a fault tolerant storage means such as a disk array system. The CDP is separated into a write data path (WDP) and a read data path (RDP), which operate independently of each other. The RDP is enabled during a write operation to read output data from the WDP and to implement detection of data errors in the controller. If no error is detected in the write data exiting the WDP, we are assured of being able to subsequently read it because of the fault tolerance in disk drive data paths.
- In operation, cyclic redundancy check (HOST CRC) characters are generated and added to the host write data. The HOST CRC characters are used in two ways. First, they are regenerated and checked in the RDP during write operations as an overall check of the WDP processing of the host data block. Second, the HOST CRC characters are stored on the drives to be used on subsequent read operations as an overall check of the RDP as it rebuilds the host data block. The combined host data block and HOST CRC is divided into multiple data blocks by the WDP, one block per drive. The controller then generates additional cyclic redundancy check (PORT CRC) characters which are appended to each block and stored on the drives. The PORT CRC characters are regenerated during read operations and compared to the stored characters. If a disk drive data path has failed during a write or read operation, the PORT CRC check can be used as a pointer to the failed data path. The read data can then be reconstructed from the other good disk drives in a well known manner. This feature provides fault tolerance on read operations. The blocks having write data with HOST and PORT CRC characters are fed to the ports of a plurality of disk drives, which includes a parity drive for processing redundancy data. Simultaneously, error detection circuitry in the RDP checks the host data, redundant data, and the HOST CRC and PORT CRC characters to detect errors in the write data from the WDP.
- In a specific implementation of RDP error detection circuitry, there is no need for duplication of PORT CRC generating circuitry in the RDP thus simplifying the write verification system and reducing cost of manufacture and maintenance expense. Instead, the individual data blocks are checked by summing the contribution of each port. The resulting sum is checked and if a failure is indicated, the write operation is retried.
- Reference will now be made, by way of example, to the accompanying drawings, in which:
- Figure 1 is a schematic circuit block diagram of a write data verification system, illustrating independent write data and read data paths, embodying the present invention;
- Figure 2 is a schematic circuit diagram of a parity accumulator, such as used in the write data path of the system of Fig. 1;
- Figure 3 is a schematic circuit diagram of error detection circuitry useful for verifying write data, including an exclusive OR summer and zero check circuit, such as employed in the read data path of the system of Fig. 1;
- Figure 4 is a schematic circuit diagram of the CRC generator such as used in the WDP and RDP of the system of Fig. 1; and
- Figure 5 is an example of a host data block transfer as the system in Fig. 1 sends it to a disk array.
- With reference to Fig. 1, a write verification system comprises a
host computer 10 that processes binary data, and acontroller 16 including a write data path (WDP)network 18 and a read data path (RDP)network 34. TheWDP network 18 andRDP network 34, although connected, function independently to process write data and read data respectively. TheRDP network 34 is enabled during the write mode to read output data from theWDP network 18. -
Host computer 10 provides blocks of host data to be passed to thecontroller 16 and to an array of disk drives D0-D3, DP for recording of the data. Thecomputer 10 includes agenerator 12 that generates a number of bytes of host cyclic redundancy check (HOST CRC) characters which are appended to each block of write data received atinput terminal 14. TheHOST CRC generator 12 does not need to reside in the host computer, but could just as easily reside in thecontroller 16 and equivalent results would be achieved. - The
HOST CRC generator 12 is shown in more detail in Figure 4. As host data is received oninput 76 and passed tooutput 78, the exclusive ORtree 70 and register 72 are operated in a well known manner such that the input data is divided by a generator polynomial and the remainder is computed. After a block of HOST data has passed through thegenerator 12, themultiplexer 74 is switched so as to append the remainder (which is now known as HOST CRC) onto the host data out of 78. This cycle is repeated for each block of host data. - As illustrated in Fig. 1, the write data block with the appended HOST CRC characters is directed to the
WDP network 18. The block of input data from thehost computer 10 and the HOST CRC characters are divided by adata sequencer 20 into a plurality of subblocks of port data, preferably of equal size. In this implementation, four data subblocks are passed respectively to PORT CRC generators 24a,b,c,d. - Concurrently the write input data from the
host computer 10 is channeled to aparity accumulator 22 that calculates the redundancy data for the parity port, which is subsequently passed to PORT CRC generator 24p. - In accordance with this embodiment,PORT CRC characters are appended to the data and parity subblocks by PORT CRC generators 24a,b,c,d,p. The PORT CRC generators are implemented with the same type of circuit as the HOST CRC generator circuit shown in Figure 4. As each data byte is presented to one of the PORT CRC generators 24a,b,c,d,p for PORT CRC calculation, the byte is also passed through to the corresponding WDP holding register 26a,b,c,d,p. When each port data block has been completed, two PORT CRC bytes are immediately transferred following the last port data byte to the respective WDP holding register 26. The data and parity subblocks are transferred from the WDP holding registers to the respective disk drives D0-D3,Dp. The purpose of each holding register 26a,b,c,d,p is to provide temporary storage of data before the data can be sent to the respective disk drive.
- During operation of the system, each of four consecutive host data bytes are summed by modulo 2 summation in the
parity accumulator 22, and the resulting sum is fed to PORT CRC generator 24p. As an example, the first group of eight bytes of host write data may be designated as 01,02,03,04,05,06,07,08. Thefirst byte 01 of 8 bits is transferred to PORT CRC generator 24a, WDP holding register 26a and, simultaneously to an exclusive OR (XOR)logic circuit 50 of theaccumulator 22, as illustrated in Fig. 2. Thebyte value 01 is summed with theinitial value 00 to produce a resultant 01. Thesecond byte 02 is transferred to PORT CRC generator 24b and register 26b, and simultaneously summed with thecurrent value 01 in accumulator 22 (01 xor 02 = 03).Byte 03 is transferred to PORT CRC generator 24c, register 26c, and simultaneously summed (03 xor 03 = 00).Byte 04 is transferred to PORT CRC generator 24d, register 26d and simultaneously summed (00 xor 04 = 04). At this point the value of the byte in theparity accumulator 22 is transferred to PORT CRC generator 24p and register 26p. These five bytes, 01-04 and the parity byte, represent the first rank of data. A port rank. corresponds to the set of bytes over which the parity byte is calculated, and the parity byte itself. - The
accumulator 22 is reinitialized to 00 and the above sequence is repeated for every four bytes of input data. The transfer of data is continued by transfer ofbyte 05 to PORT CRC generator 24a, holding registers 26a, and simultaneous summing with the initialized 00 value (00 xor 05 = 05). Thenbyte 06 is transferred to PORT CRC generator 24b, holding register 26b, and is simultaneously summed (05 xor 06 = 03).Byte 07 is transferred to PORT CRC generator 24c, holding register 26c, and is simultaneously summed (03 xor 07 = 04). Byte 08 is transferred to PORT CRC generator 24d, holding register 26d, and is simultaneously summed (04 xor 08 = 0C). The parity byte 0C is then transferred to PORT CRC generator 24p, holding register 26p, and the accumulator is reinitialized to 00. The second rank therefore consists of the fivebytes - This sequence is repeated until the entire host data block including HOST CRC characters has been transferred. The
WDP Data Sequencer 20 divides the host data block including HOST CRC into fourths and the parity port data is calculated from the host data. A system clock (not shown) is used to time the sequential transfer of the data bytes or subblocks. - After each host data block including HOST CRC characters has been processed in the above manner, the PORT CRC characters that are generated in PORT CRC generators 24a,b,c,d,p are passed respectively to WDP holding registers 26a-d,p. The data and parity subblocks with appended HOST CRC and PORT CRC characters are then fed through terminals 28a-d,p to PORT0-PORT3 and PORTP to respective data disk drives D0-D3 and parity disk drive Dp for storage.
- The data subblocks and redundant or parity subblock are fed back through terminals 30a-30d,p to the
network 34 constituting the read data path (RDP). The port data and parity data are provided to holding registers 32a-d,p. Each holding register provides temporary storage of data. The stored data contents of the RDP holding registers 32a-d,p are passed to a 5byte XOR summer 36 to produce a sum check across each rank, bytes 0-3,p for the entire data block. The output of thesummer 36 is directed to a zerocheck circuit 38 which checks the result of the summing operation to be equal to 0 for each rank, bytes 0-3,p. If the sum is non-zero an error flag is set in a status register of thecontroller 16. Themicroprocessor 48 has access to the error flag. If the error flag is set after the write operation, the transfer is considered incorrect and the microprocessor initiates a retry. It should be noted that five 8-bit input data lines are connected between the outputs of the holding registers 32a-d,p and the inputs toxor summer 36, although Fig. 1 shows single lead lines for convenience and simplicity. - In Fig. 3, an example of detection circuitry comprising the
xor summer 36 and zerocheck circuit 38 is illustrated. Five data lines, each carrying 8-bit data bytes, are applied toxor circuits Xor circuit 58 receives an 8-bit output fromxor 56 as well as the 8- bit data byte from the holding register 32. The outputs ofxor circuits xor circuit 60, which provides an 8-bit byte to the zerocheck circuit 38, having a zero detectcircuit 62 and flip-flop 64. The output from the flip-flop 64 is an error flag which is set if the zero check circuit detects a non-zero result. Themicroprocessor 48 has access to the error flag. If theerror flag 44 is set after the write operation, the transfer is considered incorrect and the microprocessor initiates a retry. - As shown in Fig. 1, the port subblocks provided to the RDP holding registers 32a-d are also provided to an
RDP data sequencer 40 that sequentially channels the data subblocks to a HOSTCRC check circuit 42 under control of the system clock. The data is reassembled in theRDP data sequencer 40 in the same sequence as it was provided by the host computer to the WDP. The sequence must be the same in order to regenerate the correct HOST CRC in thecheck circuit 42. The regenerated CRC value is compared to the HOST CRC characters. If the regenerated value is not the same as the HOST CRC, anerror flag 46 is set in a status register of thecontroller 16. Themicroprocessor 48 has access to the error flag. If the error flag is set after the write operation, the transfer is considered incorrect and the microprocessor initiates a retry. - It should be noted that the HOST
CRC check circuit 42 performs the same function as theHOST CRC generator 12 as illustrated in Figure 4 with the exception that the HOST CRC characters appended to the host data block are included in the checker's calculation. Also the result of the calculation is checked to be equal to zero at the end of the host data block. - A failure in the write data path causes the overall checks to fail in the read data path and the write operation is then immediately retried. If the RDP does not detect an error in the write data then the data and appended check characters are deemed to be fault tolerant. Fault tolerance allows any single drive path or drive to fail without loss of host data.
- Since the host data block is checked by a HOST CRC, any error in the controller data path which occurs during the host data transfer will be detected. However since the PORT CRC characters are appended to the port data blocks after the HOST CRC, if an error occurs in the generation of the PORT CRC characters or when they are appended, the HOST CRC would not detect such errors during the write operation. An additional check is required to allow the detection of an error produced during port data block PORT CRC generation. One approach would be to duplicate the PORT CRC hardware in the RDP for each port, which would be relatively expensive and complex. For this example five check circuits similar to the circuit depicted in Fig. 4 would need to be duplicated in the RDP.
- In an embodiment of this invention, a simple and efficient sum check of the PORT CRC characters is provided by using the linear properties of CRC polynomial operations. The sum of the individual data PORT CRC's and the parity PORT CRC will always be zero. In this implementation, the parity PORT CRC is generated from the parity port data and not from the sum of the individual data PORT CRC characters.
-
- r(x) =
- Remainder polynomial;
- D(x) =
- Data polynomial;
- g(x) =
- CRC generator polynomial
- MOD =
-
CRC MODULO 2 division -
-
-
-
-
- This expression shows that the sum of the individual data PORT CRC's and the parity PORT CRC will be 0.
- Fig. 5 illustrates an example of a 14 byte HOST DATA block with two bytes of HOST CRC appended, as follows:
- HOST DATA:
- (01, 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E)
- HOST CRC:
- (EF, FD)
- The HOST DATA block is divided into four DATA subblocks. The parity subblock is generated from the HOST DATA. The parity subblock PORT CRC is calculated independently of the other PORT CRC characters.
- The first rank of data consists of the HOST
DATA block bytes parity subblock byte 04. PORTO data subblock consists of the host data blockbytes PORT CRC bytes port data bytes ranks 5 and 6 (PORT CRC ranks) should be zero:
22 xor 14xor 84 xor FA xor 48 = 00, and
6A xor 5C xor 0Dxor AD xor 96 = 00. - Thus, an improved write verification system is provided wherein a sum check of the port CRCs takes advantage of the linear properties of CRC polynomials by individually summing the data port CRCs and the parity port CRC as a means to check the correct generation of port CRCs while simplifying the hardware design. The disclosed embodiment affords the checking of data blocks simultaneously with the recording and storage of data in a fault tolerant disk drive array.
- The embodiment of the invention described herein is intended to be illustrative and it should be understood that the description is only one way of implementing the invention and is not meant to exclude others. For example, a byte for byte comparison could be performed between the WDP and RDP data as an alternative method for checking the write operation. In addition, while the invention is described with reference to a controller connected to disk drives, it is applicable to any controller connected in a fault tolerant way to any type of data processing and storage device.
Claims (14)
- A system for verifying write data to be recorded in a storage means, comprising:a host interface (10) for providing input blocks (14) of write data;a means (12) for generating host cyclic redundancy check characters appended to said write data blocks; anda controller (16) coupled to said interface, said controller including a write data path network (18) and a read data path network (34) coupled to the output of said write data path network (18);said write data path network (18) including means (20) for dividing said data blocks into subblocks to be passed through respective ports (PORT0...PORT3), and port generator means (24A...24D) for appending port cyclic redundancy check characters to said data subblocks;said read data path network (34) including first checking means (42) for checking said host cyclic redundant check characters and second checking means (36, 38) for checking said port cyclic redundancy check characters, said read data path network (34) being enabled during a write operation in order to read the write data from the output of the write data path network, so as to detect errors in the write data and initiate a retry operation upon detection of such errors.
- A system as claimed in claim 1, wherein said write data path network (18) includes redundancy means (22) coupled to said host interface (10) for receiving said input data and for calculating redundancy subblocks to be passed through a respective port (PORTP), and additional port generator means (24P) for appending port cyclic redundancy check characters to said redundancy subblocks.
- A system as claimed in claim 1, wherein said write data path network (18) comprises write data holding registers (26A...26D) respectively coupled to said port generator means (24A...24D) for temporarily storing respective subblock data including redundancy subblock data.
- A system as claimed in claim 3, including terminal means comprising a number of terminals (28A...28D) coupled to respective ones of said holding registers (26A...26D), and wherein said storage means is a fault tolerant disk drive array having a plurality of disk drives (D0...D3) coupled to respective ones of said terminals (28A...28D).
- A system as claimed in claim 4, wherein said plurality of disk drives includes at least one redundant disk drive (DP) for storing redundancy data, said redundant disk drive being coupled to a redundant port terminal (28P).
- A system as claimed in claim 4 or 5, including a feedback path between said write data path network (18) and said read data path network (34).
- A system as claimed in claim 6, wherein said feedback path includes said terminal means (28A...28D, 28P), and said read data path network (34) includes a number of read data holding registers (32A...32D, 32P) coupled to said terminal means for temporarily storing said subblock data received from said terminal means; and a data sequencer (40) for sequentially channelling said data subblocks including said redundant subblock stored in said holding registers (32A...32D, 32P).
- A system as claimed in claim 7, wherein said first checking means comprises a host cyclic redundancy checking circuit (42) that is coupled to said data sequencer (40) for checking said host data cyclic redundancy check characters.
- A system as claimed in any preceding claim, wherein said second checking means includes an exclusive OR summer (36) coupled to said holding registers (32A...32D, 32P) for summing said port cyclic redundancy check characters and a zero check circuit (38) tied to said summer (36) for checking said sum of said port cyclic redundancy check characters.
- A system as claimed in claim 9, wherein said summer (36) includes means for summing groups of consecutive host data bytes by modulo 2 summation.
- A system as claimed in claim 2, wherein said redundancy means (22) generates redundancy data from simple parity across the data subblocks, accumulated while dividing said write data blocks (14) into subblocks.
- A system as claimed in claim 1, wherein said second checking means includes duplicate CRC generating and comparing means.
- A method for verifying write data to be recorded in a storage means, comprising the steps of:providing input blocks (14) of write data;generating host cyclic redundancy check characters appended to said write data blocks;in a write data path network (18), dividing said data blocks into subblocks to be passed through respective ports (PORT0...PORT3), appending port cyclic redundancy check characters to said data subblocks, and outputting the write data including said host cyclic redundancy check characters and said port cyclic redundancy check characters through said ports to said storage means;in a read data path network (34) which is enabled during a write operation, reading the write data output from the write data path network (18), and checking said host cyclic redundancy check characters and said port cyclic redundancy check characters, so as to detect errors in the write data; andinitiating a retry operation upon detection of an error in the write data.
- A method as claimed in claim 13, wherein said step of checking said port cyclic redundancy check characters is performed by summing groups of consecutive host data bytes by modulo 2 summation.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/668,107 US5289478A (en) | 1991-03-11 | 1991-03-11 | Method and means for verification of write data |
US668107 | 1991-03-11 |
Publications (3)
Publication Number | Publication Date |
---|---|
EP0503417A2 EP0503417A2 (en) | 1992-09-16 |
EP0503417A3 EP0503417A3 (en) | 1994-07-06 |
EP0503417B1 true EP0503417B1 (en) | 1997-07-16 |
Family
ID=24681040
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP92103531A Expired - Lifetime EP0503417B1 (en) | 1991-03-11 | 1992-03-02 | Method and means for verification of write data |
Country Status (4)
Country | Link |
---|---|
US (1) | US5289478A (en) |
EP (1) | EP0503417B1 (en) |
JP (1) | JP2779284B2 (en) |
DE (1) | DE69220822T2 (en) |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3451099B2 (en) * | 1991-12-06 | 2003-09-29 | 株式会社日立製作所 | External storage subsystem |
JP2672916B2 (en) * | 1991-12-13 | 1997-11-05 | 富士通株式会社 | Data check method for array disk device |
US5379415A (en) * | 1992-09-29 | 1995-01-03 | Zitel Corporation | Fault tolerant memory system |
US5396620A (en) * | 1993-12-21 | 1995-03-07 | Storage Technology Corporation | Method for writing specific values last into data storage groups containing redundancy |
US5487077A (en) * | 1994-05-23 | 1996-01-23 | International Business Machines Corporation | Location dependent variable error correction processing for multi-track recording media using variable length coding means |
US5748871A (en) * | 1995-08-11 | 1998-05-05 | Symbios Logic Inc. | Dual bus architecture for a storage device |
US5719885A (en) * | 1995-12-28 | 1998-02-17 | Emc Corporation | Storage reliability method and apparatus |
US6018778A (en) * | 1996-05-03 | 2000-01-25 | Netcell Corporation | Disk array controller for reading/writing striped data using a single address counter for synchronously transferring data between data ports and buffer memory |
US6108812A (en) * | 1996-06-20 | 2000-08-22 | Lsi Logic Corporation | Target device XOR engine |
KR100251950B1 (en) * | 1997-06-26 | 2000-04-15 | 윤종용 | Data storage apparatus |
US6175933B1 (en) | 1997-10-17 | 2001-01-16 | International Business Machines Corporation | Recovery of file transfers in a data processing system |
US6266202B1 (en) | 1998-06-05 | 2001-07-24 | Seagate Technology Llc | Closed loop write verification in a disc drive |
US6496320B1 (en) | 2000-02-09 | 2002-12-17 | Seagate Technology Llc | Adaptive attenuation of multi-axis vibrational disturbance |
US7020835B2 (en) | 2000-10-19 | 2006-03-28 | Oracle International Corporation | Enhancements to data integrity verification mechanism |
US6928607B2 (en) | 2000-10-19 | 2005-08-09 | Oracle International Corporation | Data integrity verification mechanism |
US7017107B2 (en) * | 2001-04-30 | 2006-03-21 | Sun Microsystems, Inc. | Storage array employing scrubbing operations at the disk-controller level |
US7016967B2 (en) * | 2001-11-08 | 2006-03-21 | Northrop Grumman Corporation | Methodology for fast file transfer protocol |
US6792506B2 (en) * | 2002-03-29 | 2004-09-14 | Emc Corporation | Memory architecture for a high throughput storage processor |
US7260658B2 (en) * | 2002-05-31 | 2007-08-21 | Oracle International Corporation | Verifying input/output command data by separately sending data to be written and information about contents of the data |
TWI259356B (en) * | 2004-03-26 | 2006-08-01 | Infortrend Technology Inc | Apparatus for checking data coherence, controller and storage system having the same and method therefore is disclosed |
US7627614B2 (en) | 2005-03-03 | 2009-12-01 | Oracle International Corporation | Lost write detection and repair |
US7734980B2 (en) * | 2005-06-24 | 2010-06-08 | Intel Corporation | Mitigating silent data corruption in a buffered memory module architecture |
EP2035948B1 (en) * | 2006-06-27 | 2016-04-13 | Waterfall Security Solutions Ltd. | Unidirectional secure links from and to a security engine |
IL180020A (en) * | 2006-12-12 | 2013-03-24 | Waterfall Security Solutions Ltd | Encryption -and decryption-enabled interfaces |
IL180748A (en) * | 2007-01-16 | 2013-03-24 | Waterfall Security Solutions Ltd | Secure archive |
US9635037B2 (en) | 2012-09-06 | 2017-04-25 | Waterfall Security Solutions Ltd. | Remote control of secure installations |
US10152500B2 (en) | 2013-03-14 | 2018-12-11 | Oracle International Corporation | Read mostly instances |
US9419975B2 (en) | 2013-04-22 | 2016-08-16 | Waterfall Security Solutions Ltd. | Bi-directional communication over a one-way link |
US9767178B2 (en) | 2013-10-30 | 2017-09-19 | Oracle International Corporation | Multi-instance redo apply |
IL235175A (en) | 2014-10-19 | 2017-08-31 | Frenkel Lior | Secure remote desktop |
US9892153B2 (en) | 2014-12-19 | 2018-02-13 | Oracle International Corporation | Detecting lost writes |
US10747752B2 (en) | 2015-10-23 | 2020-08-18 | Oracle International Corporation | Space management for transactional consistency of in-memory objects on a standby database |
US11657037B2 (en) | 2015-10-23 | 2023-05-23 | Oracle International Corporation | Query execution against an in-memory standby database |
IL250010B (en) | 2016-02-14 | 2020-04-30 | Waterfall Security Solutions Ltd | Secure connection with protected facilities |
US10698771B2 (en) | 2016-09-15 | 2020-06-30 | Oracle International Corporation | Zero-data-loss with asynchronous redo shipping to a standby database |
US10891291B2 (en) | 2016-10-31 | 2021-01-12 | Oracle International Corporation | Facilitating operations on pluggable databases using separate logical timestamp services |
US11475006B2 (en) | 2016-12-02 | 2022-10-18 | Oracle International Corporation | Query and change propagation scheduling for heterogeneous database systems |
US10691722B2 (en) | 2017-05-31 | 2020-06-23 | Oracle International Corporation | Consistent query execution for big data analytics in a hybrid database |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3831143A (en) * | 1971-11-26 | 1974-08-20 | Computer Science Corp | Concatenated burst-trapping codes |
US3786439A (en) * | 1972-12-26 | 1974-01-15 | Ibm | Error detection systems |
US4281355A (en) * | 1978-02-01 | 1981-07-28 | Matsushita Electric Industrial Co., Ltd. | Digital audio signal recorder |
US4211997A (en) * | 1978-11-03 | 1980-07-08 | Ampex Corporation | Method and apparatus employing an improved format for recording and reproducing digital audio |
US4276646A (en) * | 1979-11-05 | 1981-06-30 | Texas Instruments Incorporated | Method and apparatus for detecting errors in a data set |
JPS56119550A (en) * | 1980-02-25 | 1981-09-19 | Sony Corp | Transmission method of pcm signal |
US4380029A (en) * | 1981-03-13 | 1983-04-12 | Bti Computer Systems | Data recording format and method and apparatus for producing same |
US4612640A (en) * | 1984-02-21 | 1986-09-16 | Seeq Technology, Inc. | Error checking and correction circuitry for use with an electrically-programmable and electrically-erasable memory array |
JPS6151253A (en) * | 1984-08-20 | 1986-03-13 | Nec Corp | Memory error correctng circuit |
JPS61154227A (en) * | 1984-12-26 | 1986-07-12 | Mitsubishi Electric Corp | Two-stage coding method |
US4775978A (en) * | 1987-01-12 | 1988-10-04 | Magnetic Peripherals Inc. | Data error correction system |
USRE34100E (en) * | 1987-01-12 | 1992-10-13 | Seagate Technology, Inc. | Data error correction system |
CA1296103C (en) * | 1987-06-02 | 1992-02-18 | Theodore Jay Goodlander | High-speed, high capacity, fault-tolerant, error-correcting storage system |
US4876616A (en) * | 1987-07-22 | 1989-10-24 | Sony Corporation | Apparatus for reproducing a digital signal |
US4926426A (en) * | 1988-08-30 | 1990-05-15 | Unisys Corporation | Error correction check during write cycles |
WO1991001524A1 (en) * | 1989-07-19 | 1991-02-07 | Cray Research, Inc. | An error recovery method and apparatus for high performance disk drives |
-
1991
- 1991-03-11 US US07/668,107 patent/US5289478A/en not_active Expired - Fee Related
-
1992
- 1992-03-02 EP EP92103531A patent/EP0503417B1/en not_active Expired - Lifetime
- 1992-03-02 DE DE69220822T patent/DE69220822T2/en not_active Expired - Fee Related
- 1992-03-10 JP JP4051818A patent/JP2779284B2/en not_active Expired - Lifetime
Also Published As
Publication number | Publication date |
---|---|
EP0503417A2 (en) | 1992-09-16 |
JP2779284B2 (en) | 1998-07-23 |
DE69220822T2 (en) | 1997-11-20 |
JPH04313116A (en) | 1992-11-05 |
DE69220822D1 (en) | 1997-08-21 |
EP0503417A3 (en) | 1994-07-06 |
US5289478A (en) | 1994-02-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0503417B1 (en) | Method and means for verification of write data | |
US6041430A (en) | Error detection and correction code for data and check code fields | |
US5805799A (en) | Data integrity and cross-check code with logical block address | |
US7203890B1 (en) | Address error detection by merging a polynomial-based CRC code of address bits with two nibbles of data or data ECC bits | |
EP1792254B1 (en) | Memory array error correction | |
US6453440B1 (en) | System and method for detecting double-bit errors and for correcting errors due to component failures | |
US8099651B2 (en) | Subsystem and method for encoding 64-bit data nibble error correct and cyclic-redundancy code (CRC) address error detect for use in a 76-bit memory module | |
US5909541A (en) | Error detection and correction for data stored across multiple byte-wide memory devices | |
US5491701A (en) | Burst error corrector | |
US4402045A (en) | Multi-processor computer system | |
EP1183605B1 (en) | System and method for protecting data and correcting bit errors due to component failures | |
USRE34100E (en) | Data error correction system | |
US5177744A (en) | Method and apparatus for error recovery in arrays | |
US5226043A (en) | Apparatus and method for data error detection and correction and address error detection in a memory system | |
US5745508A (en) | Error-detection code | |
EP0117287A2 (en) | Method for correcting errors in digital data and system employing such method | |
US8527834B2 (en) | Information processing device and information processing method | |
US6457154B1 (en) | Detecting address faults in an ECC-protected memory | |
JP2001005736A (en) | Memory error correcting device | |
JPH054699B2 (en) | ||
JPH06324951A (en) | Computer system with error inspection / correction function | |
JPS63197124A (en) | Error test system | |
KR19990028535A (en) | Method and device for protecting data in disk drive buffer | |
US4455655A (en) | Real time fault tolerant error correction mechanism | |
US5751745A (en) | Memory implemented error detection and correction code with address parity bits |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): DE FR GB |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): DE FR GB |
|
17P | Request for examination filed |
Effective date: 19940927 |
|
17Q | First examination report despatched |
Effective date: 19960718 |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): DE FR GB |
|
REF | Corresponds to: |
Ref document number: 69220822 Country of ref document: DE Date of ref document: 19970821 |
|
ET | Fr: translation filed | ||
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed | ||
REG | Reference to a national code |
Ref country code: GB Ref legal event code: IF02 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20020306 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20020312 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20020320 Year of fee payment: 11 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20030302 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20031001 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20031127 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST |