A method and apparatus recovers data from a storage medium. The storage medium includes at least one data unit having a plurality of segments for storing data. The plurality of segments include k number of segments and r number of segments. Each k segment includes user data and inner code parity for providing inner code protection against errors within the segment and each r segment includes outer code parity and inner code parity for providing outer code protection against inner code failures.
In the storage medium, the r number of parity segments are associated with the k number of data segments to derive a plurality of symbol-based outer code words. Each outer code word contains m number of symbols from each segment for correcting m number of symbols in each outer code word.
A processor is configured to carry out data recovery from the storage medium by iteratively performing error correction by alternating between using the inner code parity to correct errors within the segment and using the outer code parity to correct errors in the outer code words. In particular, the processor performs a first iteration of inner code error correction on a plurality of symbol-based inner code words, a first iteration of outer code error correction on a plurality of symbol-based outer code words and performs a second iteration of inner code error correction on the plurality of symbol-based inner code words. When performing the first iteration of outer code error correction, at least one of the outer code words is correctable. When performing the second iteration of inner code error correction, at least one of the inner code words is correctable.
These and other features and benefits that characterize various embodiments of the disclosure can be understood in view of and upon reading the following detailed description and review of the associated drawings.
Embodiments of the disclosure provide a method and apparatus for recovering data on a storage medium. More specifically, the disclosure provides a method and apparatus for iteratively using inner and outer codes to recover data. For example, on a shingled magnetic recording (SMR) medium, data units, such as data tracks, partially overlap like shingles on a roof. In this type of format, physical writes tend to be sequential, and as a result, can accommodate longer code words (or outer codes) than code words in other types of recording. Such an exemplary type of data storage provides an embodiment where using inner and outer codes to correct errors is possible.
A code includes rules for converting a piece of information into another representation (i.e., one symbol into another symbol). A code word is an element of a code. Each code word includes a sequence of assembled symbols that correspond with the rules of the code. For example, codes can be used in the error-correction of data. These types of codes, often described as channel codes, contain redundancy to provide for the communication of more reliable data in the presence of noise. One example error-correcting code is a concatenated code. Concatenated codes are derived by using an inner code and an outer code.
Outer codes improve the tolerance to defects, by allowing one or more inner code failures. The size of a defect that can be corrected is closely related to the code overhead (i.e., the outer code). Therefore, an outer code or longer code word can achieve the desired defect coverage with less relative overhead. Having an outer code that can recover inner code failures also allows the inner code to be optimized for random error performance. LDPC (low density parity check) codes (which are generally included in an inner code) trade off performance to lower the error floor below the unrecoverable error rate. With an outer code as a safety mechanism, the error floor can be relaxed and LDPC codes can be optimized for performance.
Outer codes can be implemented by x-or'ing data across all inner code words. Such an implementation provides the capability to recover from a single inner code word failure. The main drawback of this implementation is that the signal-to-noise (SNR) gain for the overhead expended is relatively small. In another implementation, outer codes can be derived based on Reed-Solomon codes. Such codes allow for multiple inner code failures and offer a significant SNR benefit for random errors. Furthermore, outer codes can “average out” the SNR variability. In sequential writing, such as in SMR, many sources of variability are removed. For example, degraded signals due to adjacent track interference (ATI) or adjacent track erasure (ATE) are greatly diminished because repeated writes to adjacent or neighboring tracks are eliminated. However, variability in regards to SNR, primarily due to transducer positioning, can occur. Yet, outer codes (or very long code words) can exceed the time constants of the SNR variability and offer the “averaged out” SNR variability.
System processor 102 executes read and write operations on data storage medium 108. In one embodiment, system processor 102 is also used for carrying out data recovery from data storage medium 108. In some embodiments, data storage medium 108 is one or more magnetic discs. In other embodiments, data storage medium 108 can be a collection of solid-state memory elements. These read/write operations executed by system processor 102 may be performed directly on data storage medium 108 or through optional read/write channel 110. Read/write channel 110 receives data from system processor 102 during a write operation, and provides encoded write data to data storage medium 108. During a read operation, read/write channel 110 processes a read signal in order to detect and decode data recorded on data storage medium. The decoded data is provided to system processor 102 and ultimately through an interface 112 to an external host 114.
External host 114 is a processor in an electronic device, such as a processor in a computing device. Although
Data storage medium 108 includes a plurality of data units. Each data unit is subdivided into a plurality of storage segments. As defined herein, a storage segment is the basic unit of data storage on data storage medium 108. Each storage segment is identified and located at various positions on medium 116.
As previously discussed, data storage medium 108 can include one or more magnetic discs.
Each track or data unit has related logical block addressing (LBA). For disc-type storage media, the LBA includes a cylinder address, head address and sector address. A cylinder identifies a set of specific tracks on the disc surface to each disc 116 which lie at equal radii and are generally simultaneously accessible by a collection of transducing heads in a data storage device. The head address identifies which head can read the data and therefore identifies which disc from the plurality of discs 216 the data is located. As mentioned above, each track within a cylinder is further divided into sectors for storing data. The data sector is identified by an associated sector address.
With reference back to
Segments 302 are further divided into k number of segments 304 and r number of segments 306, wherein k and r are integers greater than or equal to 1. Each of the k number of segments 304 includes a first portion 308, which contains user data encoded by the inner code. Each of the k number of segments 304 also includes a second portion 310, which contains inner code parity data encoded by an inner code. This inner code parity 310 provides inner code protection against errors in the segment to which it belongs. More specifically, inner code parity 310 can provide protection against errors in the inner code data 308.
Each of the r number of segments 306 includes a first portion 312, which contains parity data encoded by the outer code. Each of the r number of segments 306 also includes a second portion 314, which contains inner code parity data encoded by the inner code. The outer code parity 312 provides outer code protection against inner code failures, while the inner code parity 314 of r number of segments 306 provides inner code protection against errors in the segment to which it belongs. More specifically, the inner code parity 314 provides protection against errors in the outer code parity 312. Therefore, each row of segments is considered to be an inner code word 316 starting with inner code word 0 and ending with inner code word k+r−1.
Any number of segments 306 (as represented by rows) can be provided for the outer code. The more segments that are provided for the outer code, the more errors that can be detected and corrected by the outer code parity 312. However, increasing the number of segments for the outer code and thereby increasing the number of parity data symbols, comes at the cost of reduced storage capacity of user data. As illustrated in
In one embodiment, each of the plurality of segments 302 indicated by a row in
Using the RS outer code illustrated in
Because data unit 500 includes three inner code failures and data unit 500 includes only two parity segments, the RS outer code cannot correct the three inner code failures using erasures. However, each outer code can correct one symbol in error in an outer code word 518 without erasures, and therefore the three errors shown can be corrected and the corresponding three inner code words can be recovered. It should be realized though that with higher bit error rates, the probability of having two or more symbol errors in the same outer code word in the configuration illustrated in
If, on the other hand, any of the outer code words 718 had more than eight symbol errors 720, then the outer code 712 illustrated in
Given the correction capability discussed above, exemplary data unit 900 cannot recover all of the symbol errors using the inner code on its own or by using the outer code on its own. For example, the amount of symbol errors in each inner code word 916 exceeds the correction capability or correction reliability of inner code 910 and is unable to recover these inner code words. Furthermore, outer code word 0 includes nine symbol errors 920 and outer code word 3 includes ten symbol errors 920. Therefore, the amount of symbol errors in these outer code words 918 exceeds the correction capability of outer code 912 and is unable to recover these outer code words. However, the symbol errors in the exemplary embodiment illustrated in
With reference back to block 802 of
At block 812, the method 800 determines if more inner code words 916 need to be selected for analysis. If all inner code words have been selected for analysis, then the method 800 passes to block 814. If not all inner code words have been selected for analysis, the method passes back to block 802. At block 814, it is determined whether there are any uncorrected inner code words 916 from block 804. If so, method 800 passes to block 808. If not, all inner code words 916 are corrected and the method ends. As illustrated in
In conjunction with the exemplary embodiment illustration in
At block 822, the method 800 determines if more outer code words 918 need to be selected for analysis. If all outer code words have been selected for analysis, then the method 800 passes to block 824. If not all outer code words have been selected for analysis, the method passes back to block 808 to select those outer code words. At block 824, it is determined whether there were any uncorrected outer code words 918 as determined from block 816. If so, method 800 passes back to block 802 to perform a second iteration 805 of error correction using the inner code. If not, all outer code words 916 are corrected and the method ends. An indication that all outer code words 918 are corrected is also an indication that all inner code words 916 are corrected. As illustrated in
With more outer code word symbol errors to correct, method 800 is passed back to block 802 to begin performing a second iteration 805 of inner code. At block 802, an inner code word 916 is selected. At block 804, it is determined whether the inner code can correct the select inner code word. In
At block 812, the method 800 determines if more inner code words 916 need to be selected for analysis. If all inner code words have been selected for analysis, then the method 800 passes to block 814. If not all inner code words have been selected for analysis, the method passes back to block 802. At block 814, it is determined whether there are any uncorrected inner code words 916 from block 804. If so, method 800 passes to block 808. If not, all inner code words 916 are corrected and the method ends.
In conjunction with the exemplary illustration in
At block 822, the method 800 determines if more outer code words 918 need to be selected for analysis. If all outer code words have been selected for analysis, then the method 800 passes to block 824. If not all outer code words have been selected for analysis, the method passes back to block 808 to select those outer code words. At block 824, it is determined whether there were any uncorrected outer code words 918 as determined from block 816. If so, method 800 passes back to block 802 to perform a third iteration of error correction using the inner code. If not, all outer code words 918 are corrected and the method ends. As illustrated in
It is to be understood that even though numerous characteristics and advantages of various embodiments have been set forth in the foregoing description, together with details of the structure and function of various embodiments of the invention, this disclosure is illustrative only, and changes may be made in detail, especially in matters of structure and arrangement of parts within the principles of the disclosure to the full extent indicated by the broad general meaning of the terms in which the appended claims are expressed. For example, the particular elements may vary depending on the particular type of data storage device while maintaining substantially the same functionality without departing from the scope and spirit of the present invention.
In addition, embodiments described herein can be directed to a data storage device for disc media, however, it will be appreciated by those skilled in the art that the teachings of the present invention can be applied to other types of data storage devices, without departing from the scope and spirit of the present invention.
Number | Name | Date | Kind |
---|---|---|---|
5517484 | Takagi et al. | May 1996 | A |
5844919 | Glover et al. | Dec 1998 | A |
5991911 | Zook | Nov 1999 | A |
6772384 | Noguchi | Aug 2004 | B1 |
6903887 | Asano et al. | Jun 2005 | B2 |
6981197 | Liu et al. | Dec 2005 | B2 |
6989776 | Tsang | Jan 2006 | B2 |
7000168 | Kurtas et al. | Feb 2006 | B2 |
7038993 | Minamino et al. | May 2006 | B2 |
7080306 | Sugawara et al. | Jul 2006 | B1 |
7263650 | Keeler et al. | Aug 2007 | B2 |
7356753 | Chen | Apr 2008 | B2 |
7415651 | Argon | Aug 2008 | B2 |
7536625 | Seng et al. | May 2009 | B2 |
7724853 | Jin et al. | May 2010 | B2 |
8230296 | Belogolovy et al. | Jul 2012 | B2 |
20070150798 | Shieh et al. | Jun 2007 | A1 |
20100146372 | Tomlinson et al. | Jun 2010 | A1 |
20100253555 | Weingarten et al. | Oct 2010 | A1 |
Entry |
---|
Greaves, S.; Kanai, Y.; Muraoka, H.; , “Shingled Magnetic Recording on Bit Patterned Media,” Magnetics, IEEE Transactions on , vol. 46, No. 6, pp. 1460-1463, Jun. 2010. |
U.S. Appl. No. 12/790,120, filed May 28, 2010 entitled “Outer Code Protection for Solid State Memory Devices”. |
Number | Date | Country | |
---|---|---|---|
20120278679 A1 | Nov 2012 | US |