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

Improving CHKDSK Performance for High Performance File System Drives

IP.com Disclosure Number: IPCOM000114682D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 57K

Publishing Venue

IBM

Related People

Yammine, GA: AUTHOR

Abstract

Disclosed as method for improving CHKDSK performance for High Performance File System (HPFS) drives.

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

Improving CHKDSK Performance for High Performance File System Drives

      Disclosed as method for improving CHKDSK performance for High
Performance File System (HPFS) drives.

      As disk storage devices grow in size, the ability of file
systems to recover from system crashes takes on new importance.  In
addition, recovery speed becomes very critical, since it directly
affects downtime which translates into productivity loss.  Some disk
formats such as HPFS, were not designed to be used on huge drives
even though they are being used on these drives.  The drive recovery
mechanism slows significantly as the drive size increases.  In such
situations, system crashes are very costly.  For example, some
customers plan to use the HPFS disk format for drives that are 64GB.

      All file systems have consistency checking mechanisms.  If the
file system tree structure is inconsistent, a recovery mechanism is
initiated.  Techniques such as "journalling" rely on recorded
transactions to bring back the file system tree to a consistent
state.  Journalling is a fast recovery mechanism, but it incurs a
performance hit during normal file system operation because it has to
record transactions in a synchronous manner.  Other file systems use
the "DIRTY" bit mechanism to determine whether the file system was
shut down abnormally as in the case of a system crash.  This "DIRTY"
bit means that the file system tree structure of a particular drive
is not consistent and ne...