Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Lumped Error Recovery Process

IP.com Disclosure Number: IPCOM000123480D
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 1 page(s) / 50K

Publishing Venue

IBM

Related People

Kanamaru, A: AUTHOR [+7]

Abstract

Disclosed is an algorithm for a HDD (Hard Disk Drive) to minimize the required time for the error recovery. Generally an error recovery process is composed of re-read/write operations with a combination of off track following, channel parameters' modification and so on.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 57% of the total text.

Lumped Error Recovery Process

   Disclosed is an algorithm for a HDD (Hard Disk Drive) to
minimize the required time for the error recovery.  Generally an
error recovery process is composed of re-read/write operations with a
combination of off track following, channel parameters' modification
and so on.

   Heretofore, whenever a error is observed during a
read/write operation, the operation is paused and whole recovery
process is performed against the error until the error gets
recovered, then the radical read/write operation is resumed.  For
example, if N errors are observed on one track read operation and
all errors are recovered with one recovery process, the whole
process requires n+1 revolutions.

   The new algorithm continues the read/write operation until
certain boundary even if errors are observed, and performs the
recovery process against the all errors observed in a lump.  This
algorithm requires only 2 revolutions for the above example of one
track read operation.

   The new algorithm proposes the following error recovery
process against the plural errors which are observed during
read/write operation.
  1.  Even if errors are observed, the read/write operation is
      never paused but continued to certain boundary (recovery
      execution point).  If no error is observed before the
      recovery execution point, the read/write operation shall
      be continued without being paused until next error
      recovery point.
...