I've been trying to defrag my Win2k workstation and it always leaves bars 'red' (fragmented) in the graphical display. I thought that if there was room, it would use that room and re-write the file into a contiguous block. I have huge amounts of what seem to be (according to the graphical display) contiguous free space. Certainly blocks larger than the largest file that remains fragmented.
Most of the un-de-fragged files I'm seeing are NOT system, read-only, or otherwise unmovable--although some of the ones listed below are r/o log files, but others not listed are simple text files I created and checked their attributes and they're clear.
It's like defrag is just lazy or stupid and doesn't do them. Sometimes if I run it again right away it gets some files that it missed. I didn't see the setting that said 'Only partially defrag and then give up', so I don't think that's checked. Why won't it simply defrag the files? Below is a curious example of the frag report:
Most interesting is the last item--a 1K file in 3 fragments--I have 4K cluster size so how does that happen??
Thanks for any help or insight into this
--jsteph
Most of the un-de-fragged files I'm seeing are NOT system, read-only, or otherwise unmovable--although some of the ones listed below are r/o log files, but others not listed are simple text files I created and checked their attributes and they're clear.
It's like defrag is just lazy or stupid and doesn't do them. Sometimes if I run it again right away it gets some files that it missed. I didn't see the setting that said 'Only partially defrag and then give up', so I don't think that's checked. Why won't it simply defrag the files? Below is a curious example of the frag report:
Code:
Fragments File Size Most fragmented files
2 77 KB \WINNT\Debug\UserMode\userenv.log
38 20 KB \WINNT\system32\config\software.LOG
2 8 KB \WINNT\system32\config\default.LOG
4 8 KB \WINNT\system32\config\SECURITY.LOG
3 1 KB \WINNT\system32\config\SAM.LOG
Most interesting is the last item--a 1K file in 3 fragments--I have 4K cluster size so how does that happen??
Thanks for any help or insight into this
--jsteph