One of the side effects I have found from this is that the file system systematically 
consumes the available harddrive space to the point where WindowsXP no longer functions. 
On my system it takes about 24-36 hours for Windows to report 4.5GB of free space 
as being in use, when in fact it is really not. A reboot will free up all the space 
again and then the process starts over.

I did find this article at MS: How to Locate and Correct Disk Space Problems on NTFS 
Volumes in Windows XP, but it hasn't provided any viable solutions.

http://support.microsoft.com/?kbid=315688

If anyone has a solution to these problems, please please post it!

-Fred






On Friday, October 4, 2002 at 10:02 pm, Paul wrote:
>I have a question about Prevent 
>file corruption problems:

>
>I have tried running the "new" CHKDSK under Windows XP using both the Error Checking 
>tool in "My Computer/File/Properties" and from the command line.
>
>When I used the Error Checking tool (without selecting the Automatic fix of file 
>system errors or the scan for bad sectors) XP displayed a dialogue with a sequence 
>of messages, telling me that the Error Checker was performing phase 1 of its check, 
>then phases 2 and 3 and finally a new dialogue appeared telling me that the check 
>had been completed - and nothing more.
>
>When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the 
output 
>was more informative:
>
>"The type of the file system is NTFS.
>
>WARNING!  F parameter not specified.
>Running CHKDSK in read-only mode.
>
>CHKDSK is verifying files (stage 1 of 3)...
>File verification completed.
>CHKDSK is verifying indexes (stage 2 of 3)...
>Index verification completed.
>Detected minor inconsistencies on the drive.
>CHKDSK is verifying security descriptors (stage 3 of 3)
>Cleaning up 33 unused index entries from index
>Cleaning up 33 unused index entries from index
>Cleaning up 33 unused security descriptors.
>Security descriptor verification completed.
>CHKDSK is verifying Usn Journal...
>Usn Journal verification completed.
>Correcting errors in the Volume Bitmap.
>Windows found problems with the file system.
>Run CHKDSK with the /F (fix) option to correct"
>
>My question is, which should I trust - the Error Checking tool (which I assume invokes 
>CHKDSK in the background) or the command line? Or perhaps a third party program?

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject