3.25 Issues

[schitzn]

Hi Jeroen,

I've found 2 issues to raise with full 3.25 (have not confirmed if these issues occur with previous versions):

Issue 1
On one of my drives, JKDefrag refuses to defragment the entire drive.  It also seems to be unable to consolidate free space.  The finished result looks like this:



While were on this issue, I noticed that the Properties Window of the drive looks like:


According to this, 8.34% of the disk is free space (333Mb of 3.9Gb):

However the debug log (-6) reports at the bottom:
Free disk space: 114491392 bytes, 27952 clusters, 2.73% of disk


Here is the d -6 log file:
www.schitzn.com/whyulookhere/325log.zip



Issue 2
Before I bring out this issue, I'll ask a question, and post my issue after you answer.
Does JKDefrag drive map image use a pixel for each cluster, thus meaning the size of the Window restricts how much of the drive map you will see.  Also, is there a limit to how large a drive can be to visually see it in JKDefrag (this question more relevant if you answer no to first question)

[Myriades]

Hi, schitzn

Do u know the actual size of the allocared space for the mft (pink clusters)
On the bitmap u show, it seems to be smaller than it does
it must be about 1/8 of 3.9GB->499.2MB
If not, the size have been shrink by windows and if my calcul are exact, the size is actually about 223MB (windows show u the allocated space for mft as free, jkdefrag does not)

[schitzn]

Do u know the actual size of the allocared space for the mft (pink clusters)

How do you find this out.

If not, the size have been shrink by windows and if my calcul are exact, the size is actually about 223MB (windows show u the allocated space for mft as free, jkdefrag does not)

Ah, that sound like what may be happening. What a spagehog the MFT is. Surely a filesystem doesn't need to use that much space for a Master File Table???

Anyway, that would explain the second part of issue one. Thx Myriades

[Myriades]

How do you find this out.

Using DiskView from sysinternals utility. double click on the mft allocated space, it will show u the size in cluster then
[ size in cluster ] x [ clustersize ] / [ 1024^2 ] -> size (in MB) of the allocated space for mft

CU later

[jeroen]

On one of my drives, JKDefrag refuses to defragment the entire drive.  It also seems to be unable to consolidate free space.

Windows reserves a certain percentage of the disk for expansion of the MFT. This space is counted by Windows as free space because it can/will be used for regular files when the rest of the disk is full. But JkDefrag cannot use this free space, and does not count it in the report at the end of the logfile. The 2 files that JkDefrag could not defrag, are both bigger than any gap, and therefore cannot be defragged. Please note that the biggest gaps on your disk are now the free spaces between the directories and the regular files, and between the regular files and the spacehogs, but the 2 files are both spacehogs.

Does JKDefrag drive map image use a pixel for each cluster

No. The diskmap is automatically scaled and always shows the full disk. A pixel therefore can span multiple clusters on a small disk, or multiple clusters can be mapped in a single pixel on a big disk.

[jeroen]

Do u know the actual size of the allocared space for the mft (pink clusters)

How do you find this out.

See the report at the end of the JkDefrag.log file. The actually used size of the $MFT is reported in any of the lists (for example the "The 25 largest items on disk" list). The size of the MFT reserved space is reported in the beginning of the logfile, the 3 MftExcludes items (numbers are clusters).