Is this a bug or intended?

Hello.

Using DF 2.14.[706] under Win7 x64

After analysing E: drive it shows no fragmented files. There is a data file that is fragmented (displayed in red).

I have manually set to not defrag files (or fragments) bigger than 250MB. The fragmented file size is 800 MB aprox.

Has this option something to do? It should only affect defrag not analysis.

1 PNG file attached.

post-37780-0-04382900-1368399492_thumb.png

Don't known, however a quick way to find out is to temporarily remove your 250MB file limit and re-analyse to see the results.

Yes. You are right. But I have tried removing that rule (it was for quick defrag anyway) and it's still the same.

Any more ideas?

I've seen this happening on different drives, and when you click on the non-blue blocks it clearly indicates there are fragmented files, but analysis report shows all zeros.

This happens without any limitation and with default configuration. Trying custom settings didn't help.

I have an "unused-unconfigured-default" unzip of DF 2.14.[706] under Win7 x64.

I have 6 off 1.5 GB files plus a few smaller ones totalling 9.7 GB, and 15.3 GB of free space in a "new" 25 GB NTFS partition W:\

5 of the 1.5 GB files each have 2 or 3 fragments, and the File List and the coloured map are in agreement - no discrepancies.

I ran into this the other day with a huge file I suspect Defraggler couldn't or wouldn't defrag any better than it already did so it showed no fragments.