I'm trying out Defraggler for the first time and am having major issue getting it to complete a defrag. I am running a fully updated, clean install, of Windows 10 64-bit with the OS on an SSD (C:). I have all of my user data on a pair of 640GB HDDs that are configured as a dynamic striped volume (D:). It is this HDD dynamic volume that I am trying to defrag. It is quite full, with only 153GB free out of the 1.2GB capacity, and contains a number of very large video files.
Defraggler reports that the drive is 21% defragmented but after leaving it running for 24 hours it seems to be no closer to completing than when it started. The drive map does show it reading and writing to the drive and I can see activity via the drive activity light, although the light just gradually pulses on and off slowly which indicates that the activity is not continuous. If I then stop the defrag and re-run Analyze it again shows 21% fragmented.
By way of comparison, I reverted back to Auslogics Disk Defrag which is what I always used to use. This showed my drive as being 32% fragmented. Kicking off the defrag the drive activity light stayed on continuously and the intense activity could be heard as the heads moved around - which I didn't hear with Defraggler. After 30 minutes the defrag was complete but it still left the disk 25% fragmented. Checking the log it showed that it had stopped due to lack of contiguous free space to defrag the remaining very large fragmented video files. At least the defrag stopped and gave me a clear reason. Cleaning out some files to free up space and kicking the defrag off for another 30 mins resulted on 0% fragmented
So, why didn't Defraggler give up instead of just spinning its wheels fruitlessly for 24 hours? Was it that it doesn't support dynamic striped volumes? Was it that there was insufficient free disk space (in which case it should stop and tell the user)? Or was it for some other reason? All in all this seems to be a bug to me.
