It is normal for chkdsk /F to remove unused index entries and unused security descriptors every
time you run it, these do not indicate a problem with the file system.
Scan only (without /f switch)
If a file needs to be fixed chkdsk will alert you with a message but will not fix the error(s).
chkdsk may report lost allocation units on the disk - it will produce this report even if the files are
in-use (open). If corruption is found, consider closing all files and repairing the disk with /F.
Running chkdsk on a data volume that is in use by another program or process may incorrectly
report errors when none are present. To avoid this, close all programs
or processes that have
open handles to the volume.
On computers running Windows 2003 SP1, chkdsk automatically creates a shadow copy, so you
can check volumes that are 'in use' by another program or process. This
enables an accurate
report against a live file server. On earlier versions of Windows, chkdsk would always lock the
volume, making data unavailable.
Run at Bootup
Running at bootup is often the easiest way to close all open file handles.
Use the GUI,
chkntfs
or the
FSUTIL
dirty commands to set or query the volumes 'dirty' bit so that
Windows will run chkdsk when the computer is restarted.
Event Logs
Chkdsk will log error messages in the Event Viewer - System Log.
Chkdsk /f removes ACLs that are no longer used and reports this in the Event Viewer -
Application Log.
Chia sẻ với bạn bè của bạn: