I tried defragging the whole disk, it worked fine with a datarate about 20MB/s up to ~50% - random high CPU usage on both on my cores.
Position where it stops:
Then it slows down to almost nothing speed of below 10KB/s = it stops working.
And the CPU usage is now constant at 100%, but only on one core.
I've gave up after a few hours and tried a reboot.
After the reboot nothing changes, i.e. its crawling with <10KB/s.
With this 'speed' it won't finish in my life.
Because I noticed this behaviour, i ran it in debug mode.
This is the log. It ran yesterday, than i "Paused" it and hibernated windows. Today i booted and un-paused defraggler and everything went fine for hours, until its read-write-rate goes to zero.
Hm, log file is too big. (2,15MB) I will cut it into parts.
I'm sorry I cant upload the whole log, but it only continious this row ... until I aborted it.
[2010-10-31] [17:45:57.687] 00db4 1 DefragVolumeSinglePassHelper::LayFileAt#268 MoveFileRegionWithMarking for file "V:\int2" to 183159361, 182804008, 1 finished (hr=0x00000000). Destination block is not free.
[2010-10-31] [17:45:58.015] 00db4 1 DefragVolumeSinglePassHelper::LayFileAt#268 MoveFileRegionWithMarking for file "V:\int2" to 183159362, 182804009, 1 finished (hr=0x00000000). Destination block is not free.
Make sure you have a good system backup, then move say, 25% of your old drive to the new one to free up space to defrag.
Of course, sometimes it happens that you can have a lot of system restore points. May be able to disable system restore for that drive & see if that frees up space.
Additionally, I don't really think it is always good to try to use every last byte on a drive like that. Strange things can happen to your data when attempting to copy/move/delete/change things when you really don't have any space left.