Why does chkdsk take a long time on one particular index?

Posted on

Why does chkdsk take a long time on one particular index? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, ntfs, chkdsk, , .

I have a large set of data (about nine million files of various sizes and types; mostly student home directories) and when I run chkdsk on the volume it spends a long time on a particular index. By “a long time” I mean several hours, a substantial fraction of the total time the chkdsk takes. During most of the chkdsk you can see progress every second, but at a particular index number it just stops. If I do a chkdsk again (without any changes to the data) it stops at the same number.

I’ve moved the data from one volume to a newly formatted one, and the same thing happens there. As I delete chunks of the data, the chkdsk time becomes shorter, but there is still a single index that takes a sizable fraction of the total time right up to the point where the disk is nearly empty. The index number in question changes sometimes when I delete a chunk of data.

Is this normal behaviour? Can anyone explain it? Is there a special index that contains all files, or something along those lines?

Solution :

If indexation has been actived on your hard drive then there is an index table with has the location of every file on your hard drive for future research queries. This index table can be relatively big depending on your hard drive size and whatnot.

If indexation is NOT activated, i’m not entirely sure what could cause this issue. You could be experiencing corruption of data, perhaps there is something wrong with a particular cluster or other HDD issues.

Leave a Reply

Your email address will not be published.