Angular position tracking of data accesses to mitigate risk of data loss

Description

TECHNICAL FIELD

This disclosure relates to data storage devices and, more particularly, to tracking position of data accesses to mitigate data loss risks stemming from issues such as adjacent track interference (ATI), wide area track erasure (WATER), and so on.

BACKGROUND

Many electronic devices, such as computing systems, generate and/or receive data that may be stored persistently. These electronic devices often utilize a data storage device, such as a hard disk drive (“HDD”), for data storage and retrieval. In many cases, a HDD can include a rotational disk or other media made from a magnetic material onto (and/or into) which data may be recorded as patterns of magnetic polarity. The rotational disk may be logically divided into nested rings referred to as “tracks,” which may in turn be logically divided into multiple storage locations referred to as “sectors.” One or more read/write heads of the HDD may write data to the rotational disk in response to a write instruction and/or retrieve data from the rotational disc in response to a read instruction.

Writing data to the rotational disk may sometimes affect unintended portions. For example, writing to a particular sector of a particular track may unintentionally alter adjacent sectors or tracks. Such alterations may be caused by ATI (unintentional writing and/or erasure of tracks to one or more sides of an intentionally written track caused by stray fields from a write head), WATER (unintentional writing and/or erasure of areas outside an intentionally written area caused by stray fields from a write head and the density and narrow width of tracks), or other such issues and may relate to magnetic flux used to write data to the particular sector leaking into outside areas. These kinds of issues may degrade magnetic polarity pattern integrity, making it more difficult to retrieve data and possibly resulting in data loss.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to representative embodiments illustrated in the accompanying figures. It should be understood that the following descriptions are not intended to limit the disclosure to one preferred embodiment. To the contrary, each is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the described embodiments as defined by the appended claims.

FIG. 1 depicts a simplified block diagram of a system with an example data storage device that uses angular position tracking in mitigating ATI, WATER, and/or other issues.

FIGS. 2A-2B is a flow chart and block diagram combination that depicts a flow chart of sample operations of a first example method of using angular position tracking in mitigating ATI, WATER, and/or other issues.

FIG. 3 depicts a flow chart of sample operations of a second example method of using angular position tracking in mitigating ATI, WATER, and/or other issues. This second example method may be performed by the data storage device of FIG. 1 and/or the processor, controller and/or control circuitry of FIG. 2B.

FIG. 4 depicts a flow chart of sample operations of an example method of mitigating ATI, WATER, and/or other issues. This example method may be performed by the data storage device of FIG. 1 and/or the processor, controller and/or control circuitry of FIG. 2B.

FIG. 5 depicts a flow chart of sample operations of a third example method of using angular position tracking in mitigating ATI, WATER, and/or other issues. This third example method may be performed by the data storage device of FIG. 1 and/or the processor, controller and/or control circuitry of FIG. 2B.

FIG. 6 depicts a flow chart of sample operations of a fourth example method of using angular position tracking in mitigating ATI, WATER, and/or other issues. This fourth example method may be performed by the data storage device of FIG. 1 and/or the processor, controller and/or control circuitry of FIG. 2B.

FIGS. 7A-7E are diagrams illustrating a rotational magnetic storage medium during performance of a method of using angular position tracking in mitigating ATI, WATER, and/or other issues utilizing one or more pointers. The method may be the method illustrated in FIG. 5.

FIGS. 8A-8C are diagrams illustrating a bit mask during performance of a method of using angular position tracking in mitigating ATI, WATER, and/or other issues utilizing the bit mask. The method may be the method illustrated in FIG. 6.

FIG. 9 is a diagram illustrating writes in different tracks that angularly overlap.

The use of the same or similar reference numerals in different drawings indicates similar, related, or identical items where appropriate.

DETAILED DESCRIPTION

Issues such as ATI or WATER may be handled for a rotational magnetic storage medium by logically dividing the rotational magnetic storage medium into groups of one or more adjacent tracks. When a write is performed, counters for a group of tracks and/or other possibly affected groups of tracks may be incremented to reflect the fact that the write may have affected unintended areas (such as other nearby tracks or sectors). When one or more of the counters reaches a threshold, a procedure to mitigate data loss risks stemming from ATI, WATER, and/or other issues may be performed.

However, not all writes may affect unintended areas in ways that result in ATI, WATER, or other issues. For example, the angular position of a write may be far enough away from data recorded in other sectors or tracks of a group of tracks such that the data is not affected, such as a situation where data is stored in a track that is adjacent to a track where a write is performed but on the opposite side of the rotational magnetic storage medium. If the counters are updated whenever a write is performed to the group of tracks or to a group of tracks that may result in the group of tracks being affected without regard to angular position, mitigation procedures may be performed more often than are actually useful to mitigate ATI, WATER, and/or other issue. Mitigation procedures may include selectively rewriting the data deemed to be at risk. For example, whether the data is rewritten may be based on error correction status of the data when read.

Performance of mitigation procedures more often than is necessary may adversely impact response time of the data storage device. For example, if each write utilizes an average of revolution of the rotational magnetic storage medium, a mitigation procedure is triggered every 50 writes, and each mitigation procedure utilizes an average of 10 revolutions of the rotational magnetic storage medium, twenty percent of the write time of the data storage device would be devoted to mitigation procedures as opposed to performing writes (is understood that the sample numbers are purely examples for the sake of illustration and are not intended to be limiting). In this example, if the mitigation procedure would have been useful every 100 writes as opposed to every 50 writes for the reasons mentioned above, the data storage device would be spending twice the percentage of its write time performing mitigation procedures than is actually useful, significantly degrading performance of the data storage device.

However, tracking of angular position may enable improved determination of when to perform a mitigation procedure such that mitigation procedures may be performed less often. This may enable a data storage device to spend less time performing mitigation procedures and more time performing writes, improving the performance of the data storage device.

Some embodiments described herein relate to systems, apparatuses, and methods related to using position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. The position tracking can be based on an angular position of the data access operation on the rotating magnetic media. Whether or not an angular position of a write operation overlaps a previously written area in a group of tracks (which may be a group of a single track) of groups of tracks into which a rotational magnetic storage medium is divided may be determined based on the angular position of the write operation. In the event that the angular position of the write operation overlaps the previously written area, a counter may be incremented. If the counter exceeds a threshold, an ATI or WATER (or other issue) mitigation procedure may be performed. In this way, performance of the mitigation procedure more often than is useful may be avoided, improving performance of a data storage device including the rotational magnetic storage medium.

In some implementations, the angular position of the write operation may be compared to one or more pointers indicating an area of the group of tracks where write operations have been performed subsequent to the last time that the counter was incremented. For example, it may be determined whether the angular position is below a maximum previous write location pointer indicting a highest written servo wedge of a group of adjacent servo wedges. By way of another example, it may be determined whether the angular position is above a maximum previous write location pointer indicting a lowest written servo wedge of a group of adjacent servo wedges. In still another example, it may be determined whether the angular position is between such a maximum previous write location pointer and a minimum previous write location pointer.

In various implementations, the angular position of the write operation may be compared to a bit mask including data indicating areas of the group of tracks where writes have been performed subsequent to the last time that the counter was incremented. The data of the bit mask may indicate angular positions of previous writes in a group of adjacent servo wedges and may indicate all areas of the group of tracks where writes have been performed subsequent to the last time that the counter was incremented.

Although the above discusses comparing the angular position to a single pointer (or set of pointers) or bit mask for a group of tracks and incrementing a counter for that group of tracks, it is understood that these are example implementations. In various implementations, the angular position may be compared to multiple pointers and/or bit masks for multiple possibly affected groups of tracks and counters for the multiple possibly affected groups of tracks may be incremented accordingly. Besides pointers, counters and bit masks, other data structures such as arrays, linked lists, etc. may be used for tracking the positions of the data access operations.

Further, in some implementations the angular position may be compared to multiple pointers and/or bit masks that are each respectively associated with ATI, WATER, or other issues and counters respectively associated with ATI, WATER, or other issues may be incremented accordingly. In this way, mitigation procedures may be separately triggered based on the possibility of ATI, WATER, and/or other issues.

Although particular embodiments are discussed herein, it should be appreciated that the various embodiments, as well as functionality, operation, components, and capabilities thereof may be combined with other elements as necessary. Any physical, functional, or operational discussion of any element or feature is not intended to be limited solely to a particular embodiment to the exclusion of others.

FIG. 1 depicts a simplified block diagram of a system 100 with an example data storage device 105 that uses angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. As illustrated, the system 100 may include one or more data storage devices 105 that may be configured to communicate with one or more host devices 110. The host device 110 may be any electronic device such as a laptop computer, desktop computer, server, cellular phone, tablet computer, and so on. In some embodiments, the host device 110 can be implemented as a system of individual electronic devices, for example, as a network of servers.

The host device 110 may send commands 115 to the data storage device 105. The commands 115 may be any number of commands 115 including, but not necessarily limited to, write commands, erase commands, and read commands. The data storage device 105 may include a controller 120 (such as a controller, a processing unit, an electrical circuit, an integrated circuit, instructions executed by a processor, and so on), a memory 135 (which may be a volatile memory such as dynamic random access memory (DRAM) or non-volatile memory such as magneto-resistive random access memory (MRAM)), and a rotational magnetic storage media 155 (such as a circular recording disk made from a magnetic material onto and/or into which data can be recorded as patterns of magnetic polarity, and so on). The controller 120 may receive and execute the commands 115. The controller 120 may transmit one or more responses 145 to the host device 110 (such as in response to receiving a command, as part of executing a received command, and so on).

As shown, the rotational magnetic storage media 155 include one or more tracks 165 that are divided into one or more sectors. As shown, the rotational magnetic storage media 155 and the tracks 165 may be angularly divided logically into one or more pseudo wedges 160 (that may be made up of one or more servo wedges). The controller 120 may be connected to a voice coil motor (“VCM”) 150 that controls the location of a read head and a write head over a the rotational magnetic storage media 155 in order to retrieve data from the rotational magnetic storage media 155 and/or write data to the rotational magnetic storage media 155 in response to the commands 115.

The controller 120 may perform a method for using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. The controller 120 may determine whether or not an angular position of a write operation overlaps a previously written area of one of the group of tracks based on the angular position of the write operation. If so, the controller 120 may increment a counter (such as for the group of tracks or another affected group of tracks) (which may be stored in the memory 135). If the counter exceeds a threshold (such as 50, 150, 300, and so on), an ATI or WATER (or other issue) mitigation procedure may be performed (such as on the group of tracks or another affected group of tracks).

Although the above describes the controller 120 as either incrementing the counter or not, it is understood that this is an example. The above may be handled differently in various implementations, such as to handle ATI, WATER, and/or other issues differently. For example, in some implementations the counter may be incremented by different amounts based on how close and/or far the write operation is from a previously written area. By way of another example, in some implementations a counter may only be updated if the angular position of a write operation is within a previously written area and the radial position of the write operation is within a threshold number of tracks (such as five) of the previously written area (and/or updated by different amounts depending on the number of tracks between the radial position of the write operation and the previously written area).

For purposes of clarity, FIG. 9 illustrates an example rotational magnetic storage media 900 that is divided into groups of tracks including a group of tracks 901 made up of tracks 902a-902c. As illustrated, the rotational magnetic storage media is also angularly divided logically into one or more pseudo wedges including pseudo wedges. FIG. 9 shows a first write 904 and a second write 905. Although the first write 904 and the second write 905 do not overlap radially within the track 902b, the first write 904 and the second write 905 angularly overlap as at least a portion of each is within the angular area defined as pseudo wedge 903b. In various implementations of the present disclosure, such an occurrence may result in the incrementing of one or more counters.

FIGS. 2A-2B is a flow chart and block diagram combination that depicts a flow chart of sample operations of a first example method 200 of using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues.

The method of FIG. 2A may begin at operation 210 where a determination is made whether or not an angular position of a write operation within a group of tracks (of groups into which a rotational magnetic storage disk is divided) overlaps a previously written area in the group of tracks. Next, at operation 220, a counter is incremented in the event the angular position overlaps the previously written area (such as a counter for the group of tracks and/or another affected group of tracks). Then, at operation 230, a data loss risk mitigation procedure is performed (such as on the group of tracks and/or another affected group of tracks).

Although the first example method 200 of FIG. 2A is illustrated and described as including particular operations performed in a particular order, it is understood that this is an example. In various implementations, various orders of the same, similar, and/or different operations may be performed without departing from the scope of the present disclosure. For example, although the method 200 discusses incrementing a counter if the angular position is determined to overlap a previously written area in the group of tracks, it is understood that this is an example. In various implementations, multiple groups of tracks may be affected by the angular position of the write and counters may be incremented for each of the affected multiple groups of tracks without departing from the scope of the present disclosure. In some cases, counters may be incremented differently for different affected groups of tracks, such as incrementing counters by a higher value for closer writes and a lower value for further writes. This may enable different handling of ATI, WATER, and/or other issues.

In many embodiments, the method of FIG. 2A can be implemented by a data storage device, such as depicted by the simplified block diagram of FIG. 2B. As shown, data storage device may include a processor, controller and/or control circuitry 260 that performs or coordinates one or more of the operations of the data storage device, such as performance of the method 200 of FIG. 2A. For example, the processor, controller and/or control circuitry 260 can be connected to a voice coil motor (“VCM”) 270 that controls the location of a read head and a write head along a rotatable disk 280 (and/or other rotational magnetic storage medium) that is formed from a magnetic material. The processor, controller and/or control circuitry 260 may also communicate with one or more host devices 250 coupled to the data storage device.

FIG. 3 depicts a flow chart of sample operations of a second example method 300 of using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. This second example method 300 may be performed by the data storage device 105 of FIG. 1 and/or the processor, controller and/or control circuitry 260 of FIG. 2B.

The flow may begin block 301 and proceed to block 302 where a controller operates. Next, the flow may proceed to block 303 where the controller may determine whether or not a write operation within a group of tracks has been received for a rotational magnetic storage media that is divided into groups of tracks. If not, the flow may return to block 302 where the controller continues to operate. Otherwise, the flow may proceed to block 304.

At block 304, after the controller determines that a write has been received, the controller may translate the logical address of the write to the angular position of the write. This may be performed utilizing logical to physical address translation. The flow may then proceed to block 305.

At block 305, the controller may determine whether or not the angular position of the write overlaps a previously written area in the group of tracks. If so, the flow may proceed to block 307 where the controller increments a counter for the group of tracks before the flow proceeds to block 308. Otherwise, the flow may proceed to block 306 where the controller updates tracking of previously written areas based on the write before the flow returns to block 302.

At block 308, the controller may determine whether or not the counter exceeds a threshold. If not, the flow may return to block 302 where the controller continues to operate. Otherwise, the flow may proceed to block 309 where the controller performs a data loss risk mitigation procedure on the group of tracks, to counter increased risks due to ATI, WATER, and/or other issues, before the flow returns to block 302 where the controller continues to operate.

Although the example method 300 is illustrated and described as including particular operations performed in a particular order, it is understood that this is an example. In various implementations, various orders of the same, similar, and/or different operations may be performed without departing from the scope of the present disclosure.

For example, although the method 300 discusses incrementing a counter for a group of tracks if the angular position is determined to overlap a previously written area in that group of tracks, it is understood that in various implementations multiple groups of tracks may be affected and counters may be incremented for each of the affected multiple groups of tracks. By way of another example, although performance of a mitigation procedure is discussed as being triggered by a single counter exceeding a threshold, it is understood that in some implementations separate ATI, WATER, and/or other issue counters may be incremented based on the angular position of a write and mitigation procedures may be triggered by any one of such counters exceeding a threshold, or comparisons of a combination of counters and/or thresholds.

FIG. 4 depicts a flow chart of sample operations of an example method 400 of mitigating ATI, WATER, and/or other issues. This example method 400 may be performed by the data storage device 105 of FIG. 1 and/or the processor, controller and/or control circuitry 260 of FIG. 2B.

The flow may begin block 401 and proceed to block 402 where a controller may read the data of a group of tracks. The flow may then proceed to block 403 where the controller determines whether or not an error correcting code correction of the read data is above a threshold. For example, if the controller used an error correcting code to correct more than 5% of the read data, the controller may determine that the error correcting code correction is above the threshold.

If the controller determines the error correcting code correction of the read data is above the threshold, the flow may proceed to block 405 where the controller rewrites the read data back to the group of tracks. Rewriting of the read data may mitigate integrity issues in the group of tracks caused by ATI, WATER, and/or other issues. Otherwise, if the flow may proceed to block 404 and end.

Although the example method 400 is illustrated and described as including particular operations performed in a particular order, it is understood that this is an example. In various implementations, various orders of the same, similar, and/or different operations may be performed without departing from the scope of the present disclosure.

For example, block 403 is illustrated and described as rewriting the read data if an error correcting code correction of the read data is above a threshold. However, in other implementations the controller may rewrite the read data to the group of tracks without making any kind of determination. In still other implementations, the controller may determine whether or not to rewrite the read data based on determinations other than an error correcting code correction. For example, the controller may determine to rewrite the read data based on various out of band information such signal amplitude of the read, signal shapes of the read, and/or any other information indicating that the integrity of the magnetic patterns of the group of tracks has been impaired by ATI, WATER, and/or other issues.

Returning to FIG. 1, the controller 120 may compare the angular position of the write operation to one or more pointers or bit masks indicating an angular area of the group of tracks where write operations have been performed subsequent to the last time that the counter was incremented. The resolution of such pointers or bit masks may correspond to space available in the memory 135 for tracking previously written areas while the storage device 105 is in operation.

For example, 16 bits of the memory 135 (e.g., DRAM) may be available per group of tracks for tracking previously written areas while the storage device 105 is in operation. The resolution of any pointers or bit masks per group of tracks may thus correspond to the information that can be tracked with 16 bits. In one example, this could result in approximately 1.7 megabytes of the memory 135 out of a possible 128 megabytes dedicated to tracking previous writes with groups of tracks of four tracks each for a data storage device with a capacity of six terabytes.

In one case of such an example, the 16 bits may be used to implement an 8-bit maximum previously written pointer and an 8-bit minimum previously written pointer that indicate an upper boundary and a lower boundary of previous angular write locations corresponding to the highest and lowest servo wedges logically dividing a group of tracks, resulting in a resolution of 256 servo wedges per group of tracks.

However, in another case of such an example, the group of tracks may be split into 4 angular sections that each have a 2-bit maximum previously written pointer and a 2-bit minimum previously written pointer. This would result in a resolution of 16 servo wedges per group of tracks, but allow for greater granularity in tracking previously written areas thus reducing the possibility of triggering mitigation procedures when not useful.

In still another case of such an example, a single 16-bit maximum or previously written pointer may be utilized, referenced from a zero index of the group of adjacent pseudo wedges logically dividing a group of tracks. This may reduce the granularity of tracking previously written areas, but may increase the number of servo wedges that can be tracked per group of tracks.

In yet another case of such an example, the 16 bits may be used to implement a bit mask of 16 bits. Higher resolution bit masks (such as a bit mask of 32 bits) may allow for allow for greater granularity in tracking previously written areas, but may require more processing time to search, update, and/or otherwise administer.

Although the above describes 16 bits of the memory 135 available per group of tracks for tracking previously written areas while the storage device 105 is in operation, it is understood that this is an example and is not intended to be limiting. Any amount of the memory 135 may be available per group of tracks for tracking previously written areas while the storage device 105 is in operation in various implementations, such as 32 bits.

Although the above discusses the group of tracks logically divided by adjacent servo wedges, it is understood that these are examples for the purposes of clarity. In some cases, the memory 135 available per group of tracks for tracking previously written areas while the storage device 105 is in operation may not be sufficiently large to allow tracking of individual adjacent servo wedges. In such cases, groups of adjacent servo wedges may be pseudo servo wedges that are actually each made up of groups of adjacent actual servo wedges. The number of servo wedges or pseudo servo wedges that logically divide a group of tracks may correspond to the memory 135 available per group of tracks for tracking previously written areas while the storage device 105 is in operation.

FIG. 5 depicts a flow chart of sample operations of a third example method 500 of using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. This third example method 500 may be performed by the data storage device 105 of FIG. 1 and/or the processor, controller and/or control circuitry 260 of FIG. 2B.

The flow may begin block 501 and proceed to block 502 where a controller operates. Next, the flow may proceed to block 503 where the controller may determine whether or not a write operation within a group of tracks has been received for a rotational magnetic storage media that is divided into groups of tracks. If not, the flow may return to block 502 where the controller continues to operate. Otherwise, the flow may proceed to block 504.

At block 504, after the controller determines that a write has been received, the controller may translate the logical address of the write to the angular position of the write. This may be performed utilizing logical to physical address translation (i.e., the angular position may be obtained by performing logical to physical address translation). The flow may then proceed to block 505.

At block 505, the controller may compare the angular position of the write to one or more pointers indicating an area of the group of tracks where a write has been performed previous to incrementing of a counter. The flow may then proceed to block 506 where the controller determines whether or not the comparison indicates that the angular position of the write overlaps a previously written area. If so, the flow may proceed to block 508. Otherwise, the flow may proceed to block 507.

At block 508, if the comparison of the angular position of the write to the one or more pointers indicates that the angular position of the write overlaps a previously written area, the controller may reset the one or more pointers. For example, if maximum and minimum pointers are used that indicate the highest and lowest servo wedges of a group of servo wedges logically dividing the group of tracks that have been previously written to, the maximum pointer may be set to a zero index for the group of servo wedges and the minimum pointer may then be set to the maximum pointer. The flow may then proceed to block 509 where the controller reapplies the write before the flow proceeds to block 510 where the controller increments a counter for the group of tracks.

Although blocks 508-509 are illustrated and described as resetting one or more pointers and reapplying the write, it is understood that this is an example and that the function is to update the one or more pointers for the write. In various implementations, the one or more pointers may be updated for the write by other procedures other than resetting the one or more pointers and reapplying the write.

After the controller increments the counter for the group of tracks, the flow may proceed to block 511 where the controller determines whether or not any other additional groups of tracks may be affected by the write. If so, the flow returns to block 505 where the controller compares the angular position of the write to an additional group of tracks. Otherwise, the flow returns to block 502 where the controller continues to operate.

At block 507, if the comparison of the angular position of the write to the one or more pointers indicates that the angular position of the write is does not overlap a previously written area, the flow may proceed to block 511 where the controller determines whether or not any other additional groups of tracks may be affected by the write.

Although blocks 505-511 are illustrated and described as incrementing a counter for a group of tracks and then determining whether or not to evaluate any additional groups of tracks, it is understood that this is an example simplified for clarity. At any time after a counter is incremented for a group of tracks, the controller may determine whether or not that counter exceeds a threshold. If so, the controller may perform a mitigation procedure on the respective group of tracks. This may be performed while one or more other groups of tracks are being evaluated.

Although the example method 500 is illustrated and described as including particular operations performed in a particular order, it is understood that this is an example. In various implementations, various orders of the same, similar, and/or different operations may be performed without departing from the scope of the present disclosure.

For example, the method 500 is illustrated and described as comparing the angular position to a single set of one or more pointers for a group of tracks. However, in various implementations the angular position may be compared to multiple sets of one or more pointers that are each respectively associated with ATI, WATER, or other issues. As such, counters associated with ATI, WATER, or other issues may be respectively incremented based on such comparisons such that controller may separately trigger mitigation procedures separately for ATI, WATER, or other issues, or these issues may be considered in combination in determining whether mitigation procedures are triggered.

FIG. 6 depicts a flow chart of sample operations of a fourth example method 600 of using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. This fourth example method 600 may be performed by the data storage device 105 of FIG. 1 and/or the processor, controller and/or control circuitry 260 of FIG. 2B.

The flow may begin block 601 and proceed to block 602 where a controller operates. Next, the flow may proceed to block 603 where the controller may determine whether or not a write operation within a group of tracks has been received for a rotational magnetic storage media that is divided into groups of tracks. If not, the flow may return to block 602 where the controller continues to operate. Otherwise, the flow may proceed to block 604.

At block 604, after the controller determines that a write has been received, the controller may translate the logical address of the write to the angular position of the write. This may be performed utilizing logical to physical address translation (i.e., the angular position may be obtained by performing logical to physical address translation). The flow may then proceed to block 605.

At block 605, the controller may compare the angular position of the write to a bit mask indicating an area of the group of tracks where a write has been performed previous to incrementing of a counter. Such a bit mask may include a location storing information corresponding to the angular position and may indicate all areas of the group of tracks where writes have been performed subsequent to incrementing the counter. The flow may then proceed to block 606 where the controller determines whether or not the comparison indicates that the angular position of the write overlaps a previously written area. If so, the flow may proceed to block 608. Otherwise, the flow may proceed to block 607.

At block 608, if the comparison of the angular position of the write to the bit mask indicates that the angular position of the write overlaps one of the previously written areas, the controller may reset the bit mask. The flow may then proceed to block 609 where the controller updates the reset bit mask for the write before the flow proceeds to block 610 where the controller increments a counter for the group of tracks.

After the controller increments the counter for the group of tracks, the flow may proceed to block 611 where the controller determines whether or not any other additional groups of tracks may be affected by the write. If so, the flow returns to block 605 where the controller compares the angular position of the write to an additional group of tracks. Otherwise, the flow returns to block 602 where the controller continues to operate.

At block 607, if the comparison of the angular position of the write to the bit mask indicates that the angular position of the write does not overlap a previously written area (i.e., is outside one of the previously written areas), the flow may proceed to block 611 where the controller determines whether or not any other additional group of tracks may be affected by the write.

Although blocks 605-611 are illustrated and described as incrementing a counter for a group of tracks and then determining whether or not to evaluate any additional groups of tracks, it is understood that this is an example simplified for clarity. At any time after a counter is incremented for a group of tracks, the controller may determine whether or not that counter exceeds a threshold. If so, the controller may perform a mitigation procedure on the respective group of tracks. This may be performed while one or more other groups of tracks are being evaluated.

Although the example method 600 is illustrated and described as including particular operations performed in a particular order, it is understood that this is an example. In various implementations, various orders of the same, similar, and/or different operations may be performed without departing from the scope of the present disclosure. For example, the method 600 is illustrated and described as comparing the angular position to a single bit mask for a group of tracks. However, in various implementations the angular position may be compared to multiple bit masks that are each respectively associated with ATI, WATER, or other issues. As such, counters associated with ATI, WATER, or other issues may be respectively incremented based on such comparisons such that controller may separately trigger mitigation procedures separately for ATI, WATER, or other issues, or these issues may be considered in combination in determining whether mitigation procedures are triggered.

FIGS. 7A-7E are diagrams illustrating a rotational magnetic storage medium during performance of a method of using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues utilizing one or more pointers 701 and 702. The method may be the method illustrated in FIG. 5.

FIG. 7A illustrates a minimum previous write location pointer 701 that represents the lowest written servo wedge of a group of adjacent servo wedges 160 angularly logically dividing a group of tracks 165. FIG. 7A also illustrates a maximum previous write location pointer 702 that represents the highest written servo wedge of the group of adjacent servo wedges 160 logically dividing the group of tracks 165. Thus, the minimum previous write location pointer 701 and the maximum previous write location pointer 702 represent upper and lower angular boundaries of the group of tracks 165 that have been written.

FIG. 7B illustrates the angular position of a write 703. As shown, the angular position of the write 703 is not between the minimum previous write location pointer 701 and the maximum previous write location pointer 702. To the contrary, as shown, the angular position of the write 703 is above the maximum previous write location pointer 702. Thus, the write 703 does not overlap a previously written area of the group of tracks 165. As such, a counter for the group of tracks 165 is not incremented and the maximum previous write location pointer 702 is updated for the write 703, as shown in FIG. 7C.

FIG. 7D illustrates the angular position of a write 704. As shown, the angular position of the write 704 is between the minimum previous write location pointer 701 and the maximum previous write location pointer 702. Thus, the write 704 overlaps a previously written area of the group of tracks 165. As such, a counter for the group of tracks 165 is incremented. Further, the minimum previous write location pointer 701 and the maximum previous write location pointer 702 are updated for the write 704 (shown spaced by the resolution of the write 704), as shown in FIG. 7E.

FIGS. 8A-8C are diagrams illustrating a bit mask during performance of a method of using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues utilizing the bit mask 801. The method may be the method illustrated in FIG. 6.

As illustrated in FIG. 8A, the bit mask 801 includes a series of indexes 802 and a series of values 803 corresponding to a group of adjacent servo wedges that angularly logically divide a group of tracks. The values 803 indicate whether or not a write has been performed to the group of tracks with an angular position corresponding to a servo wedge of the group of adjacent servo wedges that is indicated by a particular index 802. In this example, a value 803 of “1” indicates that a write has been performed and a “0” indicates that a write has not been performed. As shown, the indexes 802 of “3,” “6,” “13,” and “15” have values 803 of “1,” indicating that the group of tracks have previously been written to at angular positions corresponding to associated servo wedges.

FIG. 8B illustrates the bit mask 801 after a write to the group of tracks with an angular position corresponding to servo wedge associated with the index 802 “8.” FIG. 8A previously illustrated the index 802 “8” with a value 803 of “0,” indicating that the group of tracks had not been written to at an angular position corresponding to associated servo wedge. Thus, when the angular position of the write was compared to the bit mask 801, it was determined that the write did not overlap a previously written area of the group of tracks. Thus, a counter associated with the group of tracks was not incremented and, as shown in FIG. 8B, the bit mask 801 was updated such that the index 802 “8” has a value 803 of “1.”

FIG. 8C illustrates the bit mask 801 after a write to the group of tracks at an angular position corresponding to the servo wedge associated with the index 802 “6.” FIG. 8B previously illustrated the index 802 “6” with a value 803 of “1,” indicating that the group of tracks had been written to at an angular position corresponding to the associated servo wedge. Thus, when the angular position of the write was compared to the bit mask 801, it was determined that the write overlapped a previously written area of the group of tracks. Thus, a counter associated with the group of tracks was incremented, and, as shown in FIG. 8C, the bit mask 801 was reset and then updated for the write such that the index 802 “6” has a value 803 of “1” but the values 803 of all other indexes 802 are “0.”

As described above and illustrated in the accompanying figures, some embodiments described herein relate to systems, apparatuses, and methods related to using angular position tracking in mitigating data loss risks stemming from ATI, WATER, and/or other issues. Whether or not an angular position of a write operation overlaps a previously written area of a group of tracks of groups of tracks into which a rotational magnetic storage medium is divided may be determined based on the angular position of the write operation. In the event that the angular position of the write operation overlaps the previously written area, a counter may be incremented. If the counter exceeds a threshold, a data loss risk mitigation procedure may be performed. In this way, performance of the mitigation procedure more often than is useful may be avoided, improving performance of a data storage device including the rotational magnetic storage medium.

In various embodiments, a storage device includes a rotational magnetic storage medium divided into groups of tracks and a controller, communicably coupled to the rotational magnetic storage medium. The controller may be configured to: determine, based on an angular position of a write operation within a group of tracks, whether the angular position of the write operation overlaps a previously written area in the group of tracks; in the event the angular position of the write operation overlaps the previously written area, increment a counter; and in the event the counter exceeds a counter threshold, perform a data loss risk mitigation procedure.

In one or more embodiments, a method for determining when to perform an adjacent track interference or wide area track erasure mitigation procedure includes: comparing an angular position of a current write to at least one pointer indicating an area of a group of tracks of a rotational magnetic storage medium where at least one write has been performed subsequent to incrementing a counter; in the event the comparison indicates the angular position overlaps the area, incrementing the counter; and in the event the counter exceeds a threshold, performing a data loss risk mitigation procedure.

In some embodiments, a method for determining when to perform an adjacent track interference or wide area track erasure mitigation procedure includes: comparing an angular position of a current write to a bit mask including data indicating areas of a group of tracks of a rotational magnetic storage medium where writes have been performed subsequent to incrementing a counter; in the event the bit mask indicates the angular position overlaps the areas, incrementing the counter; and in the event the counter exceeds a threshold, performing a data loss risk mitigation procedure.

In the present disclosure, the methods disclosed may be implemented as sets of instructions or software readable by a device. Further, it is understood that the specific order or hierarchy of steps in the methods disclosed are examples of sample approaches. In other embodiments, the specific order or hierarchy of steps in the method can be rearranged while remaining within the disclosed subject matter. The accompanying method claims present elements of the various steps in a sample order, and are not necessarily meant to be limited to the specific order or hierarchy presented.

The described disclosure may be provided as a computer program product, or software, that may include a non-transitory machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic devices) to perform a process according to the present disclosure. A non-transitory machine-readable medium includes any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The non-transitory machine-readable medium may take the form of, but is not limited to, a magnetic storage medium (e.g., floppy diskette, video cassette, and so on); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; and so on.

The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the described embodiments. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the described embodiments. Thus, the foregoing descriptions of the specific embodiments described herein are presented for purposes of illustration and description. They are not meant to be exhaustive or to limit the embodiments to the precise forms disclosed. It will be apparent to one of ordinary skill in the art that many modifications and variations are possible in view of the above teachings. In particular, any features described with respect to one embodiment may also be used in some embodiments, where compatible. Likewise, the features of the different embodiments may be exchanged, substituted, or omitted where compatible and appropriate.

Many embodiments of the foregoing disclosure may include or may be described in relation to various methods of operation, use, manufacture, and so on. Notably, the operations of methods presented herein are meant only to be exemplary and, accordingly, are not necessarily exhaustive. For example an alternate operation order, or fewer or additional steps may be required or desired for particular embodiments.