The trial of fire for defraggers

Hello.

There is one "trial of fire" that I like to run on every defragmeter I try and, believe me, I have tried almost 15 or 20 of them.

Namely, to hit *again*^the "defrag" button after finishing defragmenting. Then if defragmenter starts again, it's a bad one for me. A good one would say "drive already defragmented". Unfortunately, using Defraggler 1.20 on WinXP on a non-system 100GB partition, it starts moving data all around even if it's has been defragmented a few minutes before (and it took it a long time to complete). Of course, the partition was defragmented and no process was having any access to it. What do you think? Could this be considered a bug or just a bad placement strategy choice?.

PS - Well, it's true defraggler won't start again when defragging an already defragged drive, but it will move a lot of files from the center of the drive if some files are added/modified. Still testing.

How full is that 100GB partition? I've seen several defrag programs over the years do what seems like another full defrag if a hard disk is very full.

43.1 Gb free. Almost 50%.