A curious little oddity about Windows Disk Defragmenter...

Status
Not open for further replies.

Fawfulfan

The Tortured Planet guy
No, this isn't a computer-threatening issue. It's just something I'm curious about.

Anyway...I bet all of you (the computer-savvy ones, anyway) know about disk defragmentation. For those of you who don't know, here's how it works: As computers save files to a volume (like the hard disk, or an external drive), they have a tendency to split them into pieces in the file systems, so as to completely fill specific groups of clusters. This is called fragmentation. It doesn't damage the files, but the more fragmentation there is, the less efficient the computer tends to be at retrieving files from that volume, which means that everything is a bit slower. However, there is a system maintenance process called defragmentation, which moves fragmented files around and puts them back together, to help restore a little sanity and make your computer run better.

Which brings me to my question.

The Disk Defragmenter tool that comes with Windows XP (which is what I'm using) shows your disk usage in vertical bars of four different colors. White stripes represent free space, blue stripes represent unfragmented files, red stripes represent fragmented files. And then there are green stripes, which signify "unmovable" files. It is these green stripes that lie at the heart of my question.

On my old computer, when I ran the Disk Defragmenter, the green stripes would never move around during the process (which is quite understandable). They were all grouped together in a solid green band, and stayed in one place. But on the computer I currently use, not only are the green stripes spread out all over the place, but they move, despite the fact that the files they represent are supposed to be "unmovable".

Why might this happen?
 
Might be filesystem-related, might not be. The green stripes probably represent files that are currently in use by the system and are therefore locked (which is why Windows' method of repairing the plane while it's still flying doesn't work - the Unix approach is far better).

Just taking stabs in the dark here, but it could be due to having some hooks in the OS that allow it to give up control of certain system files for a brief period of time. It could also be that the visualization is just plain inaccurate (again, probably FS-related).
 
Aren't the unmovable files the ones like (and including) pagefile.sys? You can still defragment those on startup, anyway.
 
Status
Not open for further replies.

Who is viewing this thread (Total: 1, Members: 0, Guests: 1)

Back
Top