This thread has the potential to break a live server therefore only issue commands shown in this thread if you know what you are doing, the owner of the blog accepts no responsibility for data loss or service issues this thread may cause...
FSUTIL is a very powerful disk analyser that can tell you issues that may occur with the File System (FS) before Windows breaks your server....from a DOS prompt you can enter the command:
fsutil
It supports a wealth of commands...
---- Commands Supported ----
behavior Control file system behavior
dirty Manage volume dirty bit
file File specific commands
fsinfo File system information
hardlink Hardlink management
objectid Object ID management
quota Quota management
reparsepoint Reparse point management
sparse Sparse file control
usn USN management
volume Volume management
So ask this utility for your disk statistics using the command:
fsutil fsinfo statistics c:
You get the results as shown below:
File System Type : NTFS
UserFileReads : 44546
UserFileReadBytes : 1061528576
UserDiskReads : 45843
UserFileWrites : 28122
UserFileWriteBytes : 1032515584
UserDiskWrites : 31732
MetaDataReads : 3418
MetaDataReadBytes : 33697792
MetaDataDiskReads : 4863
MetaDataWrites : 9813
MetaDataWriteBytes : 56332288
MetaDataDiskWrites : 14010
MftReads : 3000
MftReadBytes : 31985664
MftWrites : 7631
MftWriteBytes : 41050112
Mft2Writes : 0
Mft2WriteBytes : 0
RootIndexReads : 0
RootIndexReadBytes : 0
RootIndexWrites : 0
RootIndexWriteBytes : 0
BitmapReads : 301
BitmapReadBytes : 1232896
BitmapWrites : 1806
BitmapWriteBytes : 13570048
MftBitmapReads : 3
MftBitmapReadBytes : 12288
MftBitmapWrites : 367
MftBitmapWriteBytes : 1675264
UserIndexReads : 1445
UserIndexReadBytes : 5918720
UserIndexWrites : 3554
UserIndexWriteBytes : 18247680
LogFileReads : 6
LogFileReadBytes : 24576
LogFileWrites : 11839
LogFileWriteBytes : 131252224
Finally the best feature is the "Dirty" bit settings, to check your C: use this command:
fsutil dirty query c:
You will get the result:
Volume - c: is NOT Dirty
If you want to make the drive Dirty then use the command:
fsutil dirty set c:
Volume - c: is now marked dirty
You will now get a full CHKDSK on your C: use caution when using this command on a server....
FSUTIL is a very powerful disk analyser that can tell you issues that may occur with the File System (FS) before Windows breaks your server....from a DOS prompt you can enter the command:
fsutil
It supports a wealth of commands...
---- Commands Supported ----
behavior Control file system behavior
dirty Manage volume dirty bit
file File specific commands
fsinfo File system information
hardlink Hardlink management
objectid Object ID management
quota Quota management
reparsepoint Reparse point management
sparse Sparse file control
usn USN management
volume Volume management
So ask this utility for your disk statistics using the command:
fsutil fsinfo statistics c:
You get the results as shown below:
File System Type : NTFS
UserFileReads : 44546
UserFileReadBytes : 1061528576
UserDiskReads : 45843
UserFileWrites : 28122
UserFileWriteBytes : 1032515584
UserDiskWrites : 31732
MetaDataReads : 3418
MetaDataReadBytes : 33697792
MetaDataDiskReads : 4863
MetaDataWrites : 9813
MetaDataWriteBytes : 56332288
MetaDataDiskWrites : 14010
MftReads : 3000
MftReadBytes : 31985664
MftWrites : 7631
MftWriteBytes : 41050112
Mft2Writes : 0
Mft2WriteBytes : 0
RootIndexReads : 0
RootIndexReadBytes : 0
RootIndexWrites : 0
RootIndexWriteBytes : 0
BitmapReads : 301
BitmapReadBytes : 1232896
BitmapWrites : 1806
BitmapWriteBytes : 13570048
MftBitmapReads : 3
MftBitmapReadBytes : 12288
MftBitmapWrites : 367
MftBitmapWriteBytes : 1675264
UserIndexReads : 1445
UserIndexReadBytes : 5918720
UserIndexWrites : 3554
UserIndexWriteBytes : 18247680
LogFileReads : 6
LogFileReadBytes : 24576
LogFileWrites : 11839
LogFileWriteBytes : 131252224
Finally the best feature is the "Dirty" bit settings, to check your C: use this command:
fsutil dirty query c:
You will get the result:
Volume - c: is NOT Dirty
If you want to make the drive Dirty then use the command:
fsutil dirty set c:
Volume - c: is now marked dirty
You will now get a full CHKDSK on your C: use caution when using this command on a server....
Tags
Windows