Why does Windows start chkdsk at boot time?

We have a file system filter driver.

It has a feature which crypt some files.

We implemented this feature yesterday. But after shipped the feature, when we do reboot, sometimes Windows check the file system by chkdsk.

Is this a common problem while filter driver is developing?
How can we solve this?

If you guess this problem, please let me know.
Thanks.

You have somehow “corrupted” the volume or at least the FSD and its
supporting utilities believe it.

If its NTFS look for MTF corruption (for instance). Are you handling small
files correctly?

wrote in message news:xxxxx@ntfsd…
> We have a file system filter driver.
>
> It has a feature which crypt some files.
>
> We implemented this feature yesterday. But after shipped the feature, when
> we do reboot, sometimes Windows check the file system by chkdsk.
>
> Is this a common problem while filter driver is developing?
> How can we solve this?
>
> If you guess this problem, please let me know.
> Thanks.
>

Dirty bit is set in FS’s sector 0.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> We have a file system filter driver.
>
> It has a feature which crypt some files.
>
> We implemented this feature yesterday. But after shipped the feature, when we do reboot, sometimes Windows check the file system by chkdsk.
>
> Is this a common problem while filter driver is developing?
> How can we solve this?
>
> If you guess this problem, please let me know.
> Thanks.
>

By the way… doesn’t this lead to wearing out the sector 0? It gets
rewritten too often.
–pa

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
> Dirty bit is set in FS’s sector 0.
>
> –
> Maxim S. Shatskih
> Windows DDK MVP
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> wrote in message news:xxxxx@ntfsd…
>> We have a file system filter driver.
>>
>> It has a feature which crypt some files.
>>
>> We implemented this feature yesterday. But after shipped the feature,
>> when we do reboot, sometimes Windows check the file system by chkdsk.
>>
>> Is this a common problem while filter driver is developing?
>> How can we solve this?
>>
>> If you guess this problem, please let me know.
>> Thanks.
>>
>

> By the way… doesn’t this lead to wearing out the sector 0?

On each mount/dismount/shutdown?


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

Assuming this is a serious question, and assuming you’re referring to SSDs…

Modern SSDs typically have lifetimes of more than 1 Million re-write cycles. If that’s not enough, I believe that’s NOT COUNTING wear-leveling.

In other words: Not a problem.

Peter
OSR

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
>> By the way… doesn’t this lead to wearing out the sector 0?
>
> On each mount/dismount/shutdown?

Maxim, are you sure that writing this flag occurs only on mount and
dismount?
From my observation, chkdsk does not run after every OS crash.
Can this mean that this flag in sector 0 is reset more often, say, after the
flush occurred and the disk was idle for some time?

Regards,
- pa