World Library  
Flag as Inappropriate
Email this Article

Chkdsk

Article Id: WHEBN0001909823
Reproduction Date:

Title: Chkdsk  
Author: World Heritage Encyclopedia
Language: English
Subject: Recover (command), ReFS, Technical features new to Windows Vista, OS/2, CHK
Collection: External Dos Commands, Hard Disk Software, Os/2
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Chkdsk

chkdsk
A component of Microsoft Windows
Chkdsk.exe in action on drive C: in Windows 10
Details
Type Utility software
Included with DOS, OS/2 and Windows
Related components
Microsoft ScanDisk (Co-existed with Chkdsk in Windows 9x and MS-DOS 6.x)

CHKDSK (short for "check disk") is a system tool in DOS, OS/2 and Windows. It verifies the file system integrity of a volume and fixes logical file system errors. It is similar to the fsck command in Unix.

On Windows NT operating systems, CHKDSK can also check the disk surface for bad sectors and mark them. (In MS-DOS 6.x and Windows 9x, this is a task done by Microsoft ScanDisk.) Windows Server version of CHKDSK is RAID-aware and can fully recover data in bad sectors of a disk in a RAID-1 or RAID-5 array if other disks in the set are intact.[1]

CHKDSK can be run from DOS prompt, Windows Explorer, Windows Command Prompt or Recovery Console.[2]

Contents

  • Overview 1
  • The MS-DOS 5 bug 2
  • The alleged Windows 7 bug 3
  • See also 4
  • References 5

Overview

On Windows NT family, a standard CHKDSK scan consists of three phases of testing file metadata. It looks for errors but does not fix them unless it is explicitly ordered to do so. Same applies to surface scan: This test, which could be extremely time-consuming on large or low-performance disks, is not carried out unless explicitly requested. CHKDSK requires exclusive write access to the volume to perform repairs.[3][4]

Because of the exclusive access requirement and the time-consuming nature of CHKDSK operation, Windows 8 implemented a new file system health model in which the operating system fixes errors on the volumes as it encounters them. In the event that the problem is grave and a full scan is required, Action Center notifies the user to take the volume offline at the first convenience.[5]

Windows Vista and Windows Server 2008 added self-healing ability, turned on by default, in addition to providing the CHKDSK command. It detects physical file system errors and silently fixes them on the fly. Thus, many problems previously discovered on running CHKDSK never appear. It is administrated by fsutil repair command.[6][7]

The MS-DOS 5 bug

CHKDSK and UNDELETE in MS-DOS 5.0 have a bug which can corrupt data: If the file allocation table of a disk uses 256 sectors, running CHKDSK /F can cause data loss and running UNDELETE can cause unpredictable results. This normally affects disks with a capacity of approximately a multiple of 128 MB. This applies to CHKDSK.EXE and UNDELETE.EXE bearing April 9, 1991 datestamp. This bug was fixed in MS-DOS 5.0a.[8]

The alleged Windows 7 bug

Before the release of Windows 7, InfoWorld reported an alleged memory leak in CHKDSK; according to the report, the chkdsk /r command would cause the memory consumption to reach the maximum and the system to crash. Randall C. Kennedy of InfoWorld attributed the original report to "various Web sources" and said that in his tests, the memory consumption reached above 90%, although he did not experience a crash. Nevertheless, Kennedy took the memory consumption for a critical bug that would derail Windows 7's launch and cynically chastised Microsoft.[9] Tom Warren of Neowin dismissed Kennedy's assessment of the alleged leak's significance.[10] Steven Sinofsky of Microsoft also responded that Microsoft could not reproduce a crash either but that the massive memory consumption was by design, to improve performance, and not a leak. Ed Bott of ZDNet also reviewed the claim with his own tests and observed that no crash would occur. Noting that chkdsk /r, by design, does not work on the system drive while Windows is online, Bott concluded "it’s arguably a feature, not a bug, and the likelihood that you’ll ever crash a system this way is very, very small and completely avoidable."[11]

See also

References

  1. ^ Holm, Dan; Thomas, Orin (2003). "11-3: Maintaining Disk Storage Volumes". Managing and Maintaining a Microsoft Windows Server 2003 Environment. Microsoft Press. p. 11.25.  
  2. ^ "Description of the Windows XP Recovery Console for advanced users". Support (8.0 ed.).  
  3. ^ "An explanation of the new /C and /I Switches that are available to use with Chkdsk.exe". Support (4.4 ed.).  
  4. ^ "Troubleshooting Disks and File Systems". Windows XP Professional Resource Kit.  
  5. ^ Bangalore, Kiran (10 May 2012). Sinofsky, Steven, ed. "Redesigning chkdsk and the new NTFS health model". Building Windows 8.  
  6. ^ Chen, Ken (4 August 2014). "NTFS Self-Healing is An Overlooked but Useful Feature in Windows 7". Next of Windows. 
  7. ^ Pawar, Amit (13 February 2008). "Self-healing NTFS in Windows Server 2008 and Windows Vista". Amit Pawar - Infrastructure blog.  
  8. ^ "When Not to Use MS-DOS 5.0 CHKDSK and UNDELETE Commands". Support (1.1 ed.).  
  9. ^ Kennedy, Randall C. (5 August 2009). "Critical Windows 7 bug risks derailing product launch".  
  10. ^ Warren, Tom (5 August 2009). "Windows 7 RTM contains a rather nasty chkdsk bug".  
  11. ^ Bott, Ed (5 August 2009). "A killer Windows 7 bug? Sorry, no".  
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.