The present invention relates to disk based storage devices and, more particularly, to positioning heads based on servo burst patterns on a disk.
A simplified diagrammatic representation of a disk drive, generally designated as 10, is illustrated in
The actuator arm assembly 18 includes a read/write head 20 mounted to a flexure arm 22 which is attached to an actuator arm 24 that can rotate about a pivot bearing assembly 26. The actuator arm assembly 18 also includes a voice coil motor (VCM) 28 which moves the head 20 relative to tracks defined on the disk 12. The spindle motor 14, VCM 28, and head 20 are coupled to a number of electronic circuits 30 mounted to a printed circuit board 32. Although a single disk 12 is illustrated in
A servo controller in the electronic circuits 30 determines the position of the head 20 relative to the tracks 40 in response to the servo information read from the servo sectors 44. The servo controller uses the determined position to move the head 20 from an initial track to a target track (i.e., seek operation), and to maintained the head 20 aligned with the target track while data is read/written on the disk 12 (i.e., track following operation). During a seek operation, the track addresses are used as coarse positioning information to estimate the position of the head 20 as it is moved to the target track. During track following, the servo bursts are used as fine positioning information to precisely align the head 40 over the selected track.
A servo track writer (STW) can be used to the write the servo information 73 in the servo sectors 44 during a manufacturing process. To form the data tracks 40 across the disk 12, the STW controls each head 20 to write servo information at locations that are distributed across the disk 12 with incremental radial steps (pitch) therebetween. An attempt is made to write the servo information 73 with a constant pitch, so that the resulting data tracks 40 will have a constant pitch across the disk 12. As used herein, the term “pitch” is the radial distance between centers of adjacent regions on the surface of a disk 12. For example, track pitch 48 (shown in
During manufacturing, an attempt may be made to correct excessive track pitch variation by identifying the addresses for groups of tracks that have insufficient track pitch or excessive track pitch, and storing those track addresses in a table. Track addresses listed in the table are then not used during operation of the disk drive, which can be referred to as the tracks being “mapped out”.
The continuing need for higher capacity disk drives continues to drive higher track densities (i.e., smaller track pitch). With higher track densities, an acceptable margin for track pitch variation can correspondingly decrease and can cause a greater number of formatted disks to fail qualification tests and/or may result in reduced capacity and performance from the disk drive.
In some embodiments of the present invention, a disk drive includes a rotatable data storage disk having a plurality of radially distributed tracks, where the radial pitch between at least some of the tracks varies across the disk. A head is configured to read/write data on the tracks. An actuator is configured to position the head relative to the disk. A controller is configured to respond to a host read/write command identifying a track address on the disk by determining a corresponding shifted radial location on the disk that is radially offset from an actual location of the addressed track by a distance that at least partially compensates for the radial pitch variation between at least some of the tracks on the disk.
Some other embodiments of the present invention are directed to corresponding methods of positioning a head that is adjacent to a rotatable disk in a disk drive, and so as to at least partially compensate for radial pitch variation between at least some of the tracks on the disk.
The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.
It also will be understood that, as used herein, the term “comprising” or “comprises” is open-ended, and includes one or more stated elements, steps and/or functions without precluding one or more unstated elements, steps and/or functions. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “and/or” and “/”includes any and all combinations of one or more of the associated listed items. In the drawings, the size and relative sizes of regions may be exaggerated for clarity.
Some embodiments of the present invention can provide disk drives, servo channels, and methods. Accordingly, the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Consequently, as used herein, the term “signal” may take the form of a continuous waveform and/or discrete value(s), such as digital value(s) in a memory or register. Furthermore, the present invention may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
The present invention is described below with reference to block diagrams and operational flow charts. It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
The read/write channel 404 can operate in a conventional manner to convert data between the digital form used by the data controller 402 and the analog form conducted through the head 20 in the HDA 410. The read/write channel 404 provides servo positional information read from the HDA 410 to the servo controller 406. The servo positional information can be used to detect the location of the head 20 in relation to LBAs on the disk 12. The servo controller 406 can use LBAs from the data controller 402 and the servo positional information to seek the head 20 to an addressed track and block on the disk 12, and to maintain the head 20 aligned with the track while data is written/read on the disk 12.
The electronic circuits 400 are also configured to at least partially compensate for radial pitch variation between at least some of the tracks on the disk 12, such as variation in pitch 48 between tracks 40 in
The servo controller 406 responds to a track address on the disk 12 that is identified by a host read/write command by determining a corresponding shifted radial location on the disk that is radially offset from the track address by a distance that at least partially compensates for radial pitch variation between at least some of the tracks on the disk 12. The repository 408 identifies track addresses and corresponding radial offset information. The servo controller 406 can access the repository 408 using the track address as a lookup pointer to obtain the corresponding radial offset information which may identify a radial distance that the head 20 needs to be moved from the addressed track centerline to at least partially compensate for track pitch variation. The servo controller 406 can determine therefrom the shifted radial location on the disk 12 to read/write data.
The repository 408 may be recorded on the disk 12 in the HDA 410 and/or it may reside in a semiconductor memory device within or otherwise accessible by the electronic circuits 400. Moreover, as will be further explained below, the repository 408 may reside at a reserved location on the disk 12 and/or it may be radially distributed across the disk 12 so that the radial offset information may be recorded at locations that are radially aligned with the corresponding addressed tracks on the disk 12. For example, the radial offset information may be included as part of the servo information within at least one of the servo sectors 44.
exemplary flowchart of operations that may be carried out by the data controller 402 and/or servo controller 406 to at least partially compensate for radial pitch variation. At Block 500, a read/write command from a host device is received. The read/write command identifies a track address on the disk 12. At Block 502, the repository 408 is accessed to determine the track offset distance. At Block 504, a shifted radial location on the disk 12 for performing a read/write operation is determined in response to the commanded track address and the determined track offset distance. At Block 506, the head is moved via a seek operation to the shifted radial location on the disk 12 and data is read/written along that location.
The repository 408 may, for example, identify radial offset information for each track address that has at least a threshold amount of pitch variation. However, identifying radial offset information for each track may result in a high storage space requirement for the repository 408 as the number of tracks on disk 12 increases. Various further embodiments of the present invention are directed to operations and methods for representing the radial offset information that can be used to compensate for radial pitch variation between tracks.
The repository 408 may contain a listing of each of the track addresses (TA1, to TA7) and corresponding offset distances that the head 20 needs to be radially offset from the track centerline to at least substantially remove the squeeze (narrowness) present in tracks TA2 to TA6.
The track offset information for removing the squeeze in tracks TA1 to TA5 may be represented in the repository 408 more compactly by storing in the repository 408 the range of the squeezed group of tracks and the mapped out track(s). For example, if 10 tracks corresponding to track 100-110 were squeezed, the repository may store the information (100, 109, 110). The servo controller 406 can then determine from this information that track 110 has been mapped out and that the other tracks 100 to 109 are to be expanded by the radial distance (110-100)/109-100) or 1.11. Thus, to seek to track 105, the servo controller 406 positions the head 20 at the following shifted radial location to remove the effect of track squeeze:
Accordingly, the LBA of a host read/write command is converted into a track address, which is used as a reference pointer in the repository 408 to determine the track offset distance and, therefrom, the shifted radial location of the track on the disk 12. Through a seek operation, the head 20 is positioned over the shifted radial location of the track while data is read from or written to the disk 12.
The track offset information may be developed and stored within the disk drive 10 during the manufacturing of the disk drive 10. For example, after a STW writes servo information on the disk 12 to define track locations, the pitch between the tracks across the disk 12 can be tested. When the pitch variation exceeds defined thresholds, track offset information can be defined for individual tracks and groups of tracks. Some tracks may be mapped out from use so that their space can be used for adjusting track pitch among other tracks.
alternately radially offset by 10% in a direction to increase the width of a track followed by a radial offset of 10% in an opposite direction to decrease the width of the next adjacent track to decrease the width of that track (i.e., increase width of tracks TA1, TA3, and TA5, and decrease width of tracks TA2, TA4, and TA6). Accordingly, track pitch variation among tracks TA1 to TA6 can be corrected without mapping out (removing from use) any of those tracks.
a diagram that illustrates the desired reference tracks TR1 to TR6 and actual tracks TA1 to TA6, with track TA3 more narrow than the desired width of each of tracks TR1 to TA6. The width of track TA3 may be expanded by mapping-out one of the other tracks (e.g., mapping out one of TR1, TR2, TR4, TR5, or TR6) and shifting the tracks between track TA3 and the mapped out track to provide the desired width. Alternatively, when a nearby track is wider than the preferred width, the width of track TA3 can be expanded by shifting the tracks between track TA3 and the wider track so as to add the excessive width of the wider track to the narrow track. For example, if track TA7 (not shown) is sufficiently wider than the desired track width to allow expansion of track T3, tracks TA4 to TA6 can be shifted toward track TA7 so that the track TA3 is widened and tracks TA4 to TA6 maintain the same width. The repository may represent this desired shifting by identifying track offset information that can include the address for TA3 and the address for TA6. The servo controller 406 may then respond to the track offset information by shifting track TA4 to TA6 in a direction that expands track TA3 and narrows the track immediately following the defined range (i.e., narrows track TA7). Accordingly, radial track pitch variation caused by the narrow track TA3 and by the wide track TA7 may be substantially removed by shifting some of the tracks as described.
As will be appreciated, one or more of the these processes may be carried out to compensate for radial track pitch variation. Moreover, some groups of tracks may be mapped out so as not to be used for data storage because of, for example, excessive track pitch variation, while other individual ones or groups of tracks may be shifted and/or selectively mapped out to allow compensation for track pitch variation associated with those tracks.
As explained above, the repository 408 may be consolidated at a defined location on the disk 12, in a semiconductor memory in the electronic circuits 30, and/or it may be distributed across the disk 12 with relevant portions of the radial offset information being aligned with the corresponding tracks.
Referring to
The controller 406 determines (Block 1206) a shifted radial location on the disk 12 to read/write data in response to the radial offset information that was read among the servo information. The controller 406 micro-jogs (Block 1208) the head 20 a determined radial distance to align the head 20 with the shifted radial location on the disk 12. Data is then read/written (Block 1210) on the disk 12 along the shifted radial location to carry out the host read/write command.
As will be appreciated, distributing partial portions of the radial offset information among a plurality of servo sectors 44 may decrease the amount of storage space needed in the each servo sector 44 for the radial offset information, however it may also result in a longer delay between when the head 20 arrives on track and when it can be micro-jogged to a final position to allow reading/writing along the shifted radial position.
In the drawings and specification, there have been disclosed typical preferred embodiments of the invention and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the invention being set forth in the following claims.
This application claims the benefit of and priority to U.S. Provisional Patent Application No. 60/733,074, filed Nov. 3, 2005, the disclosure of which is hereby incorporated herein by reference as if set forth in its entirety.
Number | Date | Country | |
---|---|---|---|
60733074 | Nov 2005 | US |