Tip of the Day: NTFS and Chkdsk


Today’s tip…

 

Starting with Windows 8 and Windows Server 2012, there has been a fundamental change to NTFS in how we handle file system inconsistencies.  Previously, there were a number of reasons that Windows would mark the file system dirty and urge the user to run a Chkdsk /f.  Depending on the size of the data set, this could mean hours or even days of downtime. 

 

The new approach is to catalog the inconsistencies, verify them, and fix them while the volume is still online when possible.  If it is not possible to repair the file system while online, instead of prompting the user to run a full Chkdsk /f, they will be prompted to run a Chkdsk /spotfix.  This will take the volume offline and fix the cataloged issues, rather than needlessly checking the entire file system.  This reduces the time of running Chkdsk to minutes or even seconds.

 

While it is still possible to run a traditional Chkdsk /f to check the consistency of all metadata, it is not likely that it will be needed.

 

This has been improved in Windows 8.1 and Windows Server 2012 R2 in that a larger range of inconsistencies will now be fixed while the volume is still online.  The result being even less downtime.

 

Also, I want to take a moment to thank Deborah Pisano of Microsoft News Center for her blurb about Tip of the Day in The Fire Hose blog today. 

Comments (4)

  1. Anonymous says:

    I have Win 8.1 RTM installed (clean install) on a 512 GB SSD drive. I tried to run chkdsk /F and during the next reboot, I did see the countdown but I did not see the actual scan running? I checked the EventLog and I do not see anything. Did the scan just run too fast or did it not bother checking at all because the drive was healthy? Is this something new in Win 8.1 RTM?

  2. Anonymous says:

    Actually, if you are running CHKDSK /F, then you are doing the older style scan.  So its scanning all the metadata.  However, since you have an SSD, its going to be pretty fast since we aren't having to wait on rotating media.

  3. Anonymous says:

    Assuming you are talking about the volume that holds your Windows directory, the same rules apply.  The only difference is that if the volume needs to be taken offline to fix something, then you will have to schedule a reboot for it.

  4. Dinesh Prajapati says:

    How does it apply to system drive as can't take it offline right ?