US20040123202A1 - Mechanisms for detecting silent errors in streaming media devices - Google Patents
Mechanisms for detecting silent errors in streaming media devices Download PDFInfo
- Publication number
- US20040123202A1 US20040123202A1 US10/328,792 US32879202A US2004123202A1 US 20040123202 A1 US20040123202 A1 US 20040123202A1 US 32879202 A US32879202 A US 32879202A US 2004123202 A1 US2004123202 A1 US 2004123202A1
- Authority
- US
- United States
- Prior art keywords
- data block
- integrity metadata
- metadata
- processing system
- streaming media
- 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.)
- Granted
Links
Images
Classifications
-
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2211/00—Indexing scheme relating to details of data-processing equipment not covered by groups G06F3/00 - G06F13/00
- G06F2211/10—Indexing scheme relating to G06F11/10
- G06F2211/1002—Indexing scheme relating to G06F11/1076
- G06F2211/1007—Addressing errors, i.e. silent errors in RAID, e.g. sector slipping and addressing errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2211/00—Indexing scheme relating to details of data-processing equipment not covered by groups G06F3/00 - G06F13/00
- G06F2211/10—Indexing scheme relating to G06F11/10
- G06F2211/1002—Indexing scheme relating to G06F11/1076
- G06F2211/104—Metadata, i.e. metadata associated with RAID systems with parity
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
- This invention relates generally to data storage systems and more particular to a mechanism for detecting silent errors in streaming media devices.
- Data storage systems can occasionally corrupt data. These corruptions occur for several reasons. For example, firmware bugs, unprotected cache memories, bus errors can cause bits in data blocks to be modified. Such errors are “silent” because the data storage system does not realize that the error has occurred. Silent data corruption may create significant problems. For example, when an application requests data and gets the wrong data, the application may crash, or alternatively, the application may pass along the corrupted data to other applications.
- Silent data corruption is especially troublesome when it occurs in streaming media devices such as tapes. The streaming media devices, traditionally used for backup, are typically written once and not read again until an emergency occurs. If a streaming media device suffers a silent data corruption, systems that will subsequently use backup copies retrieved from the affected tape to recover data may from then on be unknowingly operating on corrupted data. Such situations may have disastrous consequences (e.g., irreparable undetected long-term data corruption).
- The present invention relates to various aspects for detecting errors in data storage devices.
- In one aspect of the invention, when a command to write a block of data to a streaming media device is received, integrity metadata associated with the data block is attached to the data block and written to the streaming media device together with the data block. Subsequently, when a read command pertaining to this data block is received, new integrity metadata is determined and compared to the attached metadata. If the new integrity metadata does not match the attached metadata, an error message is generated.
- According to another aspect of the present invention, a set of integrity metadata is determined for a data block being written to a storage medium. Each integrity metadata within the set of integrity metadata corresponds to a particular portion of the data block. The set of integrity metadata is attached to the data block and written to the storage medium. Upon receiving a read command, the attached set of integrity metadata is used to check whether any portion of the data block is corrupted.
- The present invention is illustrated by way of example, and not limitation, by the figures of the accompanying drawings in which like references indicate similar elements and in which:
- FIG. 1 illustrate an exemplary data storage system in accordance with one embodiment of the present invention;
- FIG. 2 is a flow diagram of one embodiment of a method for detecting errors in streaming media devices;
- FIG. 3A is a flow diagram of one embodiment of a method for detecting errors in data storage devices;
- FIG. 3B illustrates an exemplary data block including a set of integrity metadata; and
- FIG. 4 is a flow diagram of one embodiment of a method for restoring a file using multiple backup copies.
- As will be discussed in more detail below, an embodiment of the present invention provides a method for detecting errors in streaming media devices. In accordance with one embodiment, when a command to write a block of data to a streaming media device is received, integrity metadata associated with this data block is attached to the data block and written to the streaming media device together with the data block. Subsequently, when a read command pertaining to this data block is received, new integrity metadata is determined and compared to the attached metadata. If the new integrity metadata does not match the attached metadata, an error message is generated.
- In another embodiment, a method is provided for detecting errors in data storage devices. The method includes determining a set of integrity metadata for a data block being written to a storage medium. Each integrity metadata within the set of integrity metadata corresponds to a particular portion of the data block. The set of integrity metadata is attached to the data block and written to the storage medium. Upon receiving a read command, the attached set of integrity metadata is used to determine whether any portion of the data block is corrupted.
- In the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention.
- FIG. 1 illustrates an exemplary data storage system in accordance with one embodiment of the present invention.
- Referring to FIG. 1, a
data storage system 100 containsstorage media 120 and adata processing system 105.Storage media 120 comprises one ormore storage devices 122. In particular, storage devices may be streaming media devices such as tapes or virtual tapes (i.e., storage devices that manage data in such a manner that the data located partially or entirely in hard disk storage appears to be stored entirely on tape cartridges). -
Data processing system 105 may be a backup host machine, a server or any other device external to thestorage media 120 within the block-based portion of the I/O datapath. The datapath referred to herein represents any software, hardware, or other entities that manipulate data in block form (i.e., from the time the data enters block form on write operations to the point where the data leaves block form on read operations). The datapath extends from the computer that reads or writes the data (converting it into block form) to the storage device where the data resides during storage. For example, the datapath may include software modules such as volume managers that stripe or replicate the data, the storage devices that store the data blocks, the portion of the file system that manages data in blocks, the network that transfers the blocks, etc. - Users of
data storage system 100 may be connected todata processing system 105 directly or via a network such as a local area network or a storage array network.Storage media 120 communicates withdata processing system 105 via aninterconnect 106 that may be a standard bus for communicating information and signals (e.g., SCSI, fibre channel, etc.).Tape drives 122 are capable of responding to read and write commands fromcomputer 105. -
Computer 105 includesmemory 134 andprocessor 130, as well as other devices. In one embodiment,memory 134stores software module 128 and other program code that can be executed byprocessor 130.Memory 134 may be RAM or some other machine-readable medium. The machine-readable medium may include a mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine such as a computer or digital processing device. For example, a machine-readable medium may include a read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, etc. The code or instructions may be represented by carrier-wave signals, infrared signals, digital signals, and by other like signals. - In another embodiment,
module 128 may be implemented intape drive 122, or anywhere else outside of thecomputer 105 on the I/O datapath (e.g., a virtual tape device). - In yet another embodiment,
module 128 may consist of two modules residing remotely from each other (e.g., the first module may be implemented inmemory 134 ofcomputer 105 and the second module may be implemented in tape drive 122). - Tape storage devices within
storage media 120 store data in blocks. The length of a data block may vary for different tapes (e.g., 512 bytes, 4 kilobytes, etc.). For each tape, the length of a data block is recorded in the tape header. Each data block includes embedded integrity metadata that enables detection of errors in thestorage media 120. Integrity metadata may include a logical block address to verify the location of the data block and/or a checksum to verify the contents of the data block. A checksum is a numerical value derived through a mathematical computation on the data in a data block. The size of the integrity metadata may also be recorded in the tape header. - In one embodiment,
module 128 is responsible for determining integrity metadata for a data block and attaching the integrity metadata to the data block upon receiving a write command. The data and the attached integrity metadata are then stored together on the tape. Subsequently, when a read command is generated,module 128 is responsible for comparing the attached integrity metadata with new integrity metadata to detect any errors occurred since the data block was written to the tape. The errors could occur due to firmware bugs, unprotected cache memories, bus errors, etc. and are unknown to thestorage system 100. - FIG. 2 is a flow diagram of one embodiment of a
method 200 for detecting errors in streaming media devices. The method may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, etc.), software (such as run on a general purpose computer system or a dedicated machine), or a combination of both. -
Method 200 begins with processing logic receiving a command pertaining to a streaming media device such as a magnetic-tape storage device (processing block 202) and determining whether this command is a write or read command (decision box 204). The streaming media device stores data using extended data blocks. That is, each block of the streaming media device includes a data portion to store the actual data and an integrity metadata portion to store integrity metadata associated with the data stored in the data portion. In one embodiment, the size of the data portion and the size of the integrity metadata are recorded in the header of the streaming media device. - If the command received at
processing block 204 is a write command, processing logic determines integrity metadata for a block of data to be written to the streaming media device (processing block 206). In one embodiment, the integrity metadata is a logical block address to be used for writing the block of data to the streaming media device. In another embodiment, the integrity metadata is a checksum calculated for the data block. - Next, processing logic attaches the integrity metadata to the block of data (processing block208). Afterwards, the data block with the attached integrity metadata is written to the streaming media device (processing block 210). The attached integrity metadata is used to detect errors in the streaming media device when receiving a command to read this block of data.
- Referring now to a read command logic, if the command received at
processing block 204 is a read command, processing logic extracts integrity metadata embedded into a data block on which a read is requested (processing block 212), determines new integrity metadata for the current content of the data block (processing block 214), and compares the extracted integrity metadata with the new integrity metadata (processing block 216). If the extracted integrity metadata match the new integrity metadata (decision box 218), processing logic returns the requested data (processing block 220). Alternatively, if a mismatch between the new integrity metadata and the extracted integrity metadata is found, then this mismatch indicates that this data block may have been corrupted between the time the data block was written to the storage medium and the present time. Accordingly, processing logic returns an error message with or without the data (processing block 222). - As discussed above, in one embodiment, integrity metadata is a checksum calculated for a specific data block. The strength of a checksum determines how likely it is that a data block experiencing a typical type of error will result in a data block with an identical checksum. Checksums are calculated using algorithms that may very from simple algorithms (e.g., an XOR checksum algorithm) to more complex algorithms (e.g., a Fletcher-32 checksum algorithm). If the size of a data block is large, which is typical for a magnetic-tape storage device (e.g., a tape may have 4-KB data blocks), a simple checksum algorithm that works well for a smaller data block (e.g., a 512-byte data block) may not provide a sufficiently strong checksum. The use of a complex checksum algorithm, however, may be costly due to expensive computations involved. One embodiment of a present invention provides a solution that allows the use of simple integrity metadata algorithms while providing a reliable means for detecting errors in data storage devices with large data blocks. This solution can also be used for tapes having data blocks varying in size.
- FIG. 3A is a flow diagram of one embodiment of a
method 300 for detecting errors in data storage devices. The method may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, etc.), software (such as run on a general purpose computer system or a dedicated machine), or a combination of both. -
Method 300 begins with processing logic receiving a command pertaining to a data block (processing block 301) and determining whether this command is a command to write the data block to a storage medium (decision box 302). The storage medium may be, for example, a magnetic tape, one or more disks, etc. If the determination made atdecision box 302 is positive, processing logic determines a set of integrity metadata (e.g., a set of logical block addresses or a set of checksums) for this data block (processing block 303). Each integrity metadata within the set is calculated for a specific portion of the data block. That is, the data block is divided into portions, and each portion corresponds to a particular integrity metadata value. For example, a 4-KB data block may be divided into 8 units, 0.5 KB each. In one embodiment, sizes of data block portions and corresponding integrity metadata items are recorded within the storage medium (e.g., in the header of a tape). - Next, processing logic attaches the set of integrity metadata to the data block (processing block304) and writes the data block with the attached set of integrity metadata to the storage medium (processing block 306).
- If the command pertaining to the data block is a read command, processing logic computes new integrity metadata values for the portions of the data block (processing block310) and compares the attached integrity metadata values with the new integrity metadata values (processing block 312). If the two sets match (decision box 313), processing logic returns the requested data (processing box 316). Otherwise, processing logic returns an error message with or without the corrupted data (processing block 314). In one embodiment, processing logic returns an error message as soon as it detects a first mismatch between the two integrity metadata values of the same data block portion. Alternatively, processing logic checks all integrity metadata values and returns an error message identifying the data block portions that are corrupted.
- FIG. 3B illustrates an exemplary data block350 of a storage medium such as a magnetic tape, a virtual tape, one or more disk drives, etc. The data block 350 includes
data 354 andintegrity metadata 352 attached to thedata 354. Thedata 354 is divided inton data portions 356. Eachdata portion 356 corresponds to a metadata value 358 (i.e.,data portion 1 corresponds to metadatavalue 1,data portion 2 corresponds to metadatavalue 2, etc.). The metadata values 358 were calculated when thedata 354 was written to the storage medium. If a command to read thedata 354 is received, new metadata values will be calculated fordata portions 356 for comparing with the existing metadata values 358. If each new metadata value matches the corresponding existingmetadata value 358, thedata 354 is returned. If there is a mismatch in any pair of corresponding metadata values, an error code is returned as discussed above. - One embodiment of a mechanism for restoring a file using multiple backup copies made by a backup application will now be described.
- FIG. 4 is a flow diagram of one embodiment of a
method 400 for restoring a file using multiple backup copies. The method may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, etc.), software (such as run on a general purpose computer system or a dedicated machine), or a combination of both. Processing logic may be implemented in a backup application and/or a tape drive. -
Method 400 begins with processing logic receiving a command to restore a file using multiple backup copies previously made by a backup application (processing block 402). In response, processing logic determines whether any portion of a first copy is corrupted using a corresponding attached set of integrity metadata (e.g., a set of checksums) (decision box 404). If the first copy of the file is not corrupted, processing logic restores the file from this copy (processing logic 406). Otherwise, if the first copy is corrupted, processing logic refuses to read the corrupted copy and automatically switches to a next copy of the file (processing block 408). The switching continues until processing logic finds an uncorrupted copy of the file (decision box 410) which is then used to restore the file (processing block 406). - It should be noted that the technique of
method 400 may be used to recover entire files as discussed above, as well as portions of files without loss of generality. - In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
Claims (30)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/328,792 US7103811B2 (en) | 2002-12-23 | 2002-12-23 | Mechanisms for detecting silent errors in streaming media devices |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/328,792 US7103811B2 (en) | 2002-12-23 | 2002-12-23 | Mechanisms for detecting silent errors in streaming media devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20040123202A1 true US20040123202A1 (en) | 2004-06-24 |
US7103811B2 US7103811B2 (en) | 2006-09-05 |
Family
ID=32594584
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/328,792 Expired - Lifetime US7103811B2 (en) | 2002-12-23 | 2002-12-23 | Mechanisms for detecting silent errors in streaming media devices |
Country Status (1)
Country | Link |
---|---|
US (1) | US7103811B2 (en) |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040024963A1 (en) * | 2002-08-05 | 2004-02-05 | Nisha Talagala | Method and system for striping data to accommodate integrity metadata |
US20050251707A1 (en) * | 2004-04-29 | 2005-11-10 | International Business Machines Corporation | Mothod and apparatus for implementing assertions in hardware |
US20060112096A1 (en) * | 2004-11-19 | 2006-05-25 | Vikas Ahluwalia | Method of verifying metadata of a migrated file |
US20060112296A1 (en) * | 2004-11-05 | 2006-05-25 | Sheahan Thomas J | Data recovery system for appliances |
US20060218144A1 (en) * | 2005-03-28 | 2006-09-28 | Microsoft Corporation | Systems and methods for performing streaming checks on data format for UDTs |
US20070013234A1 (en) * | 2005-05-06 | 2007-01-18 | Amtran Technology Co., Ltd | Power switch circuit |
US20070106868A1 (en) * | 2005-11-04 | 2007-05-10 | Sun Microsystems, Inc. | Method and system for latency-directed block allocation |
US20070260623A1 (en) * | 2006-05-05 | 2007-11-08 | Jaquette Glen A | Apparatus, system, and method for read back verification of stored data |
US7533225B1 (en) * | 2004-08-17 | 2009-05-12 | Sun Microsystems, Inc. | Method and apparatus for enabling adaptive endianness |
US20120117040A1 (en) * | 2010-11-10 | 2012-05-10 | Oracle International Corporaton | Method and System for Verifying Data Stored on a Medium |
US20130185261A1 (en) * | 2006-08-18 | 2013-07-18 | Falconstor, Inc. | System and Method for Identifying and Mitigating Redundancies in Stored Data |
US8566125B1 (en) | 2004-09-20 | 2013-10-22 | Genworth Holdings, Inc. | Systems and methods for performing workflow |
US8681570B2 (en) * | 2012-02-24 | 2014-03-25 | GlobalFoundries, Inc. | Methods and systems for memory devices with asymmetric switching characteristics |
CN105161138A (en) * | 2015-09-30 | 2015-12-16 | 四川效率源信息安全技术股份有限公司 | Repair method for situation of incapability of accessing to data block caused by error of Seagate hard disk firmware manager |
WO2017053100A1 (en) * | 2015-09-25 | 2017-03-30 | Microsoft Technology Licensing, Llc | Efficient detection of corrupt data |
CN109918226A (en) * | 2019-02-26 | 2019-06-21 | 平安科技(深圳)有限公司 | A kind of silence error-detecting method, device and storage medium |
US10387280B2 (en) * | 2017-06-09 | 2019-08-20 | International Business Machines Corporation | Reporting defects in a flash memory back-up system |
CN111858139A (en) * | 2020-07-10 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Method and device for detecting silent data errors |
US10956245B1 (en) * | 2017-07-28 | 2021-03-23 | EMC IP Holding Company LLC | Storage system with host-directed error scanning of solid-state storage devices |
US20220116298A1 (en) * | 2009-12-29 | 2022-04-14 | Iheartmedia Management Services, Inc. | Data stream test restart |
US20230091301A1 (en) * | 2005-09-30 | 2023-03-23 | Pure Storage, Inc. | Utilizing Integrity Information to Determine Corruption in a Vast Storage System |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050066230A1 (en) * | 2003-09-23 | 2005-03-24 | Bean Robert George | Data reliabilty bit storage qualifier and logical unit metadata |
GB2413654B (en) * | 2004-04-29 | 2008-02-13 | Symbian Software Ltd | A method of backing up and restoring data in a computing device |
US8751859B2 (en) * | 2007-05-10 | 2014-06-10 | International Business Machines Corporation | Monitoring lost data in a storage system |
US7752489B2 (en) * | 2007-05-10 | 2010-07-06 | International Business Machines Corporation | Data integrity validation in storage systems |
US8117496B2 (en) * | 2009-06-18 | 2012-02-14 | International Business Machines Corporation | Detecting and recovering from silent data errors in application cloning systems |
US9275678B2 (en) * | 2010-03-25 | 2016-03-01 | International Business Machines Corporation | Primary storage media with associated secondary storage media for efficient data management |
US9430155B2 (en) * | 2010-03-25 | 2016-08-30 | International Business Machines Corporation | File index, metadata storage, and file system management for magnetic tape |
US9063666B2 (en) | 2010-03-25 | 2015-06-23 | International Business Machines Corporation | File index, metadata storage, and file system management for magnetic tape |
US9401180B2 (en) | 2012-10-12 | 2016-07-26 | International Business Machines Corporation | High resolution tape directory (HRTD) stored at end of data in an index partition |
US11874821B2 (en) | 2021-12-22 | 2024-01-16 | Ebay Inc. | Block aggregation for shared streams |
Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5197148A (en) * | 1987-11-30 | 1993-03-23 | International Business Machines Corporation | Method for maintaining data availability after component failure included denying access to others while completing by one of the microprocessor systems an atomic transaction changing a portion of the multiple copies of data |
US5201044A (en) * | 1990-04-16 | 1993-04-06 | International Business Machines Corporation | Data processing method for file status recovery includes providing a log file of atomic transactions that may span both volatile and non volatile memory |
US5206939A (en) * | 1990-09-24 | 1993-04-27 | Emc Corporation | System and method for disk mapping and data retrieval |
US5720026A (en) * | 1995-10-06 | 1998-02-17 | Mitsubishi Denki Kabushiki Kaisha | Incremental backup system |
US5796934A (en) * | 1996-05-31 | 1998-08-18 | Oracle Corporation | Fault tolerant client server system |
US5889934A (en) * | 1997-02-24 | 1999-03-30 | Data General Corporation | Data validation system for a group of data storage disks |
US5995308A (en) * | 1997-03-31 | 1999-11-30 | Stmicroelectronics N.V. | Disk resident defective data sector information management system on a headerless magnetic disk device |
US6009542A (en) * | 1998-03-31 | 1999-12-28 | Quantum Corporation | Method for preventing transfer of data to corrupt addresses |
US6343343B1 (en) * | 1998-07-31 | 2002-01-29 | International Business Machines Corporation | Disk arrays using non-standard sector sizes |
US6347359B1 (en) * | 1998-02-27 | 2002-02-12 | Aiwa Raid Technology, Inc. | Method for reconfiguration of RAID data storage systems |
US6397309B2 (en) * | 1996-12-23 | 2002-05-28 | Emc Corporation | System and method for reconstructing data associated with protected storage volume stored in multiple modules of back-up mass data storage facility |
US6408416B1 (en) * | 1998-07-09 | 2002-06-18 | Hewlett-Packard Company | Data writing to data storage medium |
US6418519B1 (en) * | 1998-08-18 | 2002-07-09 | International Business Machines Corporation | Multi-volume, write-behind data storage in a distributed processing system |
US6467060B1 (en) * | 1998-06-26 | 2002-10-15 | Seagate Technology Llc | Mass storage error correction and detection system, method and article of manufacture |
US6484185B1 (en) * | 1999-04-05 | 2002-11-19 | Microsoft Corporation | Atomic operations on data structures |
US20030070042A1 (en) * | 2001-09-28 | 2003-04-10 | James Byrd | Storage array having multiple erasure correction and sub-stripe writing |
US6553511B1 (en) * | 2000-05-17 | 2003-04-22 | Lsi Logic Corporation | Mass storage data integrity-assuring technique utilizing sequence and revision number metadata |
US6584544B1 (en) * | 2000-07-12 | 2003-06-24 | Emc Corporation | Method and apparatus for preparing a disk for use in a disk array |
US6587962B1 (en) * | 1999-10-20 | 2003-07-01 | Hewlett-Packard Development Company, L.P. | Write request protection upon failure in a multi-computer system |
US20030140299A1 (en) * | 2002-01-22 | 2003-07-24 | Sun Microsystems, Inc. | Error detection in storage data |
US20030145270A1 (en) * | 2002-01-31 | 2003-07-31 | Holt Keith W. | Method for using CRC as metadata to protect against drive anomaly errors in a storage array |
US6606629B1 (en) * | 2000-05-17 | 2003-08-12 | Lsi Logic Corporation | Data structures containing sequence and revision number metadata used in mass storage data integrity-assuring technique |
US20030163777A1 (en) * | 2002-02-28 | 2003-08-28 | Holt Keith W. | Optimized read performance method using metadata to protect against drive anomaly errors in a storage array |
US6629273B1 (en) * | 2000-01-24 | 2003-09-30 | Hewlett-Packard Development Company, L.P. | Detection of silent data corruption in a storage system |
US20030188216A1 (en) * | 2001-10-01 | 2003-10-02 | International Business Machines Corporation | Controlling the state of duplexing of coupling facility structures |
US20030221155A1 (en) * | 2002-05-24 | 2003-11-27 | Weibel David C. | Error detection using data block mapping |
US6684289B1 (en) * | 2000-11-22 | 2004-01-27 | Sandisk Corporation | Techniques for operating non-volatile memory systems with data sectors having different sizes than the sizes of the pages and/or blocks of the memory |
US6687791B2 (en) * | 2002-01-07 | 2004-02-03 | Sun Microsystems, Inc. | Shared cache for data integrity operations |
US6728922B1 (en) * | 2000-08-18 | 2004-04-27 | Network Appliance, Inc. | Dynamic data space |
US20040123032A1 (en) * | 2002-12-24 | 2004-06-24 | Talagala Nisha D. | Method for storing integrity metadata in redundant data layouts |
US20040153746A1 (en) * | 2002-04-24 | 2004-08-05 | Talagala Nisha D. | Mechanisms for embedding and using integrity metadata |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6874001B2 (en) | 2001-10-05 | 2005-03-29 | International Business Machines Corporation | Method of maintaining data consistency in a loose transaction model |
US6880060B2 (en) | 2002-04-24 | 2005-04-12 | Sun Microsystems, Inc. | Method for storing metadata in a physical sector |
-
2002
- 2002-12-23 US US10/328,792 patent/US7103811B2/en not_active Expired - Lifetime
Patent Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5197148A (en) * | 1987-11-30 | 1993-03-23 | International Business Machines Corporation | Method for maintaining data availability after component failure included denying access to others while completing by one of the microprocessor systems an atomic transaction changing a portion of the multiple copies of data |
US5201044A (en) * | 1990-04-16 | 1993-04-06 | International Business Machines Corporation | Data processing method for file status recovery includes providing a log file of atomic transactions that may span both volatile and non volatile memory |
US5206939A (en) * | 1990-09-24 | 1993-04-27 | Emc Corporation | System and method for disk mapping and data retrieval |
US5720026A (en) * | 1995-10-06 | 1998-02-17 | Mitsubishi Denki Kabushiki Kaisha | Incremental backup system |
US5796934A (en) * | 1996-05-31 | 1998-08-18 | Oracle Corporation | Fault tolerant client server system |
US6397309B2 (en) * | 1996-12-23 | 2002-05-28 | Emc Corporation | System and method for reconstructing data associated with protected storage volume stored in multiple modules of back-up mass data storage facility |
US5889934A (en) * | 1997-02-24 | 1999-03-30 | Data General Corporation | Data validation system for a group of data storage disks |
US5995308A (en) * | 1997-03-31 | 1999-11-30 | Stmicroelectronics N.V. | Disk resident defective data sector information management system on a headerless magnetic disk device |
US6347359B1 (en) * | 1998-02-27 | 2002-02-12 | Aiwa Raid Technology, Inc. | Method for reconfiguration of RAID data storage systems |
US6009542A (en) * | 1998-03-31 | 1999-12-28 | Quantum Corporation | Method for preventing transfer of data to corrupt addresses |
US6467060B1 (en) * | 1998-06-26 | 2002-10-15 | Seagate Technology Llc | Mass storage error correction and detection system, method and article of manufacture |
US6408416B1 (en) * | 1998-07-09 | 2002-06-18 | Hewlett-Packard Company | Data writing to data storage medium |
US6343343B1 (en) * | 1998-07-31 | 2002-01-29 | International Business Machines Corporation | Disk arrays using non-standard sector sizes |
US6418519B1 (en) * | 1998-08-18 | 2002-07-09 | International Business Machines Corporation | Multi-volume, write-behind data storage in a distributed processing system |
US6484185B1 (en) * | 1999-04-05 | 2002-11-19 | Microsoft Corporation | Atomic operations on data structures |
US6587962B1 (en) * | 1999-10-20 | 2003-07-01 | Hewlett-Packard Development Company, L.P. | Write request protection upon failure in a multi-computer system |
US6629273B1 (en) * | 2000-01-24 | 2003-09-30 | Hewlett-Packard Development Company, L.P. | Detection of silent data corruption in a storage system |
US6553511B1 (en) * | 2000-05-17 | 2003-04-22 | Lsi Logic Corporation | Mass storage data integrity-assuring technique utilizing sequence and revision number metadata |
US6606629B1 (en) * | 2000-05-17 | 2003-08-12 | Lsi Logic Corporation | Data structures containing sequence and revision number metadata used in mass storage data integrity-assuring technique |
US6584544B1 (en) * | 2000-07-12 | 2003-06-24 | Emc Corporation | Method and apparatus for preparing a disk for use in a disk array |
US6728922B1 (en) * | 2000-08-18 | 2004-04-27 | Network Appliance, Inc. | Dynamic data space |
US6684289B1 (en) * | 2000-11-22 | 2004-01-27 | Sandisk Corporation | Techniques for operating non-volatile memory systems with data sectors having different sizes than the sizes of the pages and/or blocks of the memory |
US20030070042A1 (en) * | 2001-09-28 | 2003-04-10 | James Byrd | Storage array having multiple erasure correction and sub-stripe writing |
US20030188216A1 (en) * | 2001-10-01 | 2003-10-02 | International Business Machines Corporation | Controlling the state of duplexing of coupling facility structures |
US6687791B2 (en) * | 2002-01-07 | 2004-02-03 | Sun Microsystems, Inc. | Shared cache for data integrity operations |
US20030140299A1 (en) * | 2002-01-22 | 2003-07-24 | Sun Microsystems, Inc. | Error detection in storage data |
US20030145270A1 (en) * | 2002-01-31 | 2003-07-31 | Holt Keith W. | Method for using CRC as metadata to protect against drive anomaly errors in a storage array |
US20030163777A1 (en) * | 2002-02-28 | 2003-08-28 | Holt Keith W. | Optimized read performance method using metadata to protect against drive anomaly errors in a storage array |
US20040153746A1 (en) * | 2002-04-24 | 2004-08-05 | Talagala Nisha D. | Mechanisms for embedding and using integrity metadata |
US20030221155A1 (en) * | 2002-05-24 | 2003-11-27 | Weibel David C. | Error detection using data block mapping |
US20040123032A1 (en) * | 2002-12-24 | 2004-06-24 | Talagala Nisha D. | Method for storing integrity metadata in redundant data layouts |
Cited By (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7051155B2 (en) | 2002-08-05 | 2006-05-23 | Sun Microsystems, Inc. | Method and system for striping data to accommodate integrity metadata |
US20040024963A1 (en) * | 2002-08-05 | 2004-02-05 | Nisha Talagala | Method and system for striping data to accommodate integrity metadata |
US7328374B2 (en) * | 2004-04-29 | 2008-02-05 | International Business Machines Corporation | Method and apparatus for implementing assertions in hardware |
US20050251707A1 (en) * | 2004-04-29 | 2005-11-10 | International Business Machines Corporation | Mothod and apparatus for implementing assertions in hardware |
US7533225B1 (en) * | 2004-08-17 | 2009-05-12 | Sun Microsystems, Inc. | Method and apparatus for enabling adaptive endianness |
US8566125B1 (en) | 2004-09-20 | 2013-10-22 | Genworth Holdings, Inc. | Systems and methods for performing workflow |
US20060112296A1 (en) * | 2004-11-05 | 2006-05-25 | Sheahan Thomas J | Data recovery system for appliances |
US7529745B2 (en) | 2004-11-19 | 2009-05-05 | International Business Machines Corporation | Method of verifying metadata of a migrated file |
US20060112096A1 (en) * | 2004-11-19 | 2006-05-25 | Vikas Ahluwalia | Method of verifying metadata of a migrated file |
EP1710718A2 (en) * | 2005-03-28 | 2006-10-11 | Microsoft Corporation | Systems and methods for performing streaming checks on data format for UDTs |
US20060218144A1 (en) * | 2005-03-28 | 2006-09-28 | Microsoft Corporation | Systems and methods for performing streaming checks on data format for UDTs |
US7571153B2 (en) * | 2005-03-28 | 2009-08-04 | Microsoft Corporation | Systems and methods for performing streaming checks on data format for UDTs |
EP1710718A3 (en) * | 2005-03-28 | 2009-12-23 | Microsoft Corporation | Systems and methods for performing streaming checks on data format for UDTs |
US20070013234A1 (en) * | 2005-05-06 | 2007-01-18 | Amtran Technology Co., Ltd | Power switch circuit |
US11755413B2 (en) * | 2005-09-30 | 2023-09-12 | Pure Storage, Inc. | Utilizing integrity information to determine corruption in a vast storage system |
US20230091301A1 (en) * | 2005-09-30 | 2023-03-23 | Pure Storage, Inc. | Utilizing Integrity Information to Determine Corruption in a Vast Storage System |
US20070106868A1 (en) * | 2005-11-04 | 2007-05-10 | Sun Microsystems, Inc. | Method and system for latency-directed block allocation |
US20070260623A1 (en) * | 2006-05-05 | 2007-11-08 | Jaquette Glen A | Apparatus, system, and method for read back verification of stored data |
US8375064B2 (en) | 2006-05-05 | 2013-02-12 | International Business Machines Corporation | Apparatus, system, and method for read back verification of stored data |
US20130185261A1 (en) * | 2006-08-18 | 2013-07-18 | Falconstor, Inc. | System and Method for Identifying and Mitigating Redundancies in Stored Data |
US10769106B2 (en) | 2006-08-18 | 2020-09-08 | Falconstor, Inc. | System and method for identifying and mitigating redundancies in stored data |
US9710476B2 (en) * | 2006-08-18 | 2017-07-18 | Falconstor, Inc. | System and method for identifying and mitigating redundancies in stored data |
US20220116298A1 (en) * | 2009-12-29 | 2022-04-14 | Iheartmedia Management Services, Inc. | Data stream test restart |
US11777825B2 (en) * | 2009-12-29 | 2023-10-03 | Iheartmedia Management Services, Inc. | Media stream monitoring |
US20230155908A1 (en) * | 2009-12-29 | 2023-05-18 | Iheartmedia Management Services, Inc. | Media stream monitoring |
US11563661B2 (en) * | 2009-12-29 | 2023-01-24 | Iheartmedia Management Services, Inc. | Data stream test restart |
US20120117040A1 (en) * | 2010-11-10 | 2012-05-10 | Oracle International Corporaton | Method and System for Verifying Data Stored on a Medium |
WO2012064634A1 (en) * | 2010-11-10 | 2012-05-18 | Oracle International Corporation | Method and system for verifying data stored on a medium |
US8681570B2 (en) * | 2012-02-24 | 2014-03-25 | GlobalFoundries, Inc. | Methods and systems for memory devices with asymmetric switching characteristics |
WO2017053100A1 (en) * | 2015-09-25 | 2017-03-30 | Microsoft Technology Licensing, Llc | Efficient detection of corrupt data |
US10489240B2 (en) * | 2015-09-25 | 2019-11-26 | Microsoft Technology Licensing, Llc | Efficient detection of corrupt data |
US20170091020A1 (en) * | 2015-09-25 | 2017-03-30 | Microsoft Technology Licensing, Llc | Efficient detection of corrupt data |
CN105161138A (en) * | 2015-09-30 | 2015-12-16 | 四川效率源信息安全技术股份有限公司 | Repair method for situation of incapability of accessing to data block caused by error of Seagate hard disk firmware manager |
US10387280B2 (en) * | 2017-06-09 | 2019-08-20 | International Business Machines Corporation | Reporting defects in a flash memory back-up system |
US10956245B1 (en) * | 2017-07-28 | 2021-03-23 | EMC IP Holding Company LLC | Storage system with host-directed error scanning of solid-state storage devices |
CN109918226A (en) * | 2019-02-26 | 2019-06-21 | 平安科技(深圳)有限公司 | A kind of silence error-detecting method, device and storage medium |
CN111858139A (en) * | 2020-07-10 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Method and device for detecting silent data errors |
Also Published As
Publication number | Publication date |
---|---|
US7103811B2 (en) | 2006-09-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7103811B2 (en) | Mechanisms for detecting silent errors in streaming media devices | |
US20130346810A1 (en) | Use of application-level context information to detect corrupted data in a storage system | |
US7640412B2 (en) | Techniques for improving the reliability of file systems | |
JP4916033B2 (en) | Data storage method, data storage system and program (verification of data integrity in storage system) (Copyright and trademark registration notice Part of the disclosure of this patent document contains copyrighted content. Voters will have no objection to facsimile copies of either patent documents or patent disclosures as long as the copies appear in the world as patent files or records of the Patent and Trademark Office, but in all other cases (Copyrights are fully reserved.) (For certain marks referred to herein, customary or registered trademarks of third parties that may or may not be affiliated with the applicant or its assignee. The use of these marks is intended to provide a disclosure that may be implemented by way of example, and only in connection with such marks. The scope of the invention should not be construed as limiting.) | |
US7447938B1 (en) | System and method for reducing unrecoverable media errors in a disk subsystem | |
US6523087B2 (en) | Utilizing parity caching and parity logging while closing the RAID5 write hole | |
US7020805B2 (en) | Efficient mechanisms for detecting phantom write errors | |
US7908512B2 (en) | Method and system for cache-based dropped write protection in data storage systems | |
US6880060B2 (en) | Method for storing metadata in a physical sector | |
US9767117B2 (en) | Method and system for efficient write journal entry management for a distributed file system | |
US7774643B2 (en) | Method and apparatus for preventing permanent data loss due to single failure of a fault tolerant array | |
US5581690A (en) | Method and apparatus for preventing the use of corrupt data in a multiple disk raid organized storage system | |
US7546436B2 (en) | Storage device with SCSI formatting | |
US20040123032A1 (en) | Method for storing integrity metadata in redundant data layouts | |
US7234024B1 (en) | Application-assisted recovery from data corruption in parity RAID storage using successive re-reads | |
US6233696B1 (en) | Data verification and repair in redundant storage systems | |
US8280855B2 (en) | Extended logical worm data integrity protection with unique worm identifier in header and database | |
US7818609B2 (en) | Methods and systems for managing corrupted meta-data in a computer system or network | |
US7594051B2 (en) | Storage apparatus | |
US20060215456A1 (en) | Disk array data protective system and method | |
US20040250028A1 (en) | Method and apparatus for data version checking | |
CN110222035A (en) | A kind of efficient fault-tolerance approach of database page based on exclusive or check and journal recovery | |
US7577804B2 (en) | Detecting data integrity | |
US6904547B2 (en) | Method and apparatus for facilitating validation of data retrieved from disk | |
US6678107B1 (en) | System and method for reading and writing N-way mirrored storage devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TALAGALA, NISHA D.;REEL/FRAME:013618/0418 Effective date: 20021219 |
|
AS | Assignment |
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WONG, BRIAN;REEL/FRAME:013952/0940 Effective date: 20030327 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: ORACLE AMERICA, INC., CALIFORNIA Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:ORACLE USA, INC.;SUN MICROSYSTEMS, INC.;ORACLE AMERICA, INC.;REEL/FRAME:037302/0616 Effective date: 20100212 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553) Year of fee payment: 12 |