Data Disk Monthly Seems to miss some fragmented files?

[Norm@Home]

I've noticed this problem since shortly after the 4.3.1 release but had hoped I would see some mention of this in the forums or an updated release.

For example, I have a small home server running Windows Server 2008 R2 and it runs the Firebird database server; I have a separate disk in the system just for the database files and nothing else. While the server automatically runs a script twice a week to backup my main database, every month (sometimes every other month if I'm busy) after the backup I'll stop the server and rename my main .gdb file; and restore from the backup and then delete the renamed gdb file and do a "Data Disk Monthly" defrag and then restart the database server. What I've noticed after the defrag is that the gdb file will still be in several fragments, this month it was four. I use a separate simpler file defrag program after MyDefrag, which indicated that the file was in four fragments. I have to say that my main gdb file is pretty large, just a hair over 8gb. I don't know if that's a factor or not.

I also have on the server a disk where I keep over a 500,000 assorted files (I add and remove files throughout the month) and I've also noticed that after a Data Disk Monthly defrag some of the files still appear to be in fragments; then I use the same program to find and defrag these as well. As far as I can tell these files are just a fraction of the size of the gdb file on the database disk so I'm not sure that the fact that some files are being skipped has anything to do with the size of the file.

Is this any kind of a known problem? Anything in the script that may need to be changed?

Thanks,

- Norm

[Darlis]

.I use a separate simpler file defrag program after MyDefrag, which indicated that the file was in four fragments. I have to say that my main gdb file is pretty large, just a hair over 8gb. I don't know if that's a factor or not.

4 fragments on a 8GB file is negligible. The main reason MyDefrag can't move a file is that it is write-locked by a process. The file size doesn't matter.

It's also possible that the file is wrapped around unmovable files and thus shows as fragmented in other programs (see [FAQ]Why does MyDefrag not perfectly optimize my disk? on that matter).

[Norm@Home]

4 fragments on a 8GB file is negligible. The main reason MyDefrag can't move a file is that it is write-locked by a process. The file size doesn't matter.

It's also possible that the file is wrapped around unmovable files and thus shows as fragmented in other programs

Before I start to defrag the disk I use the Firebird server manager to turn the Firebird server service off so there's no way the file is locked by the database server. As I had mentioned the disk that the actual database files are on is a data disk and I only keep my database files on it, the MyDefrag diskmap also does not show any unmovable files so I don't believe that is what is causing the file to be unmovable.

Do I understand you correctly that MyDefrag does not consider a file fragmented if it is in multiple segments but those segments are separated by one or more unmovable files?

I don't doubt that there are instances where a file can't be moved for the reasons you state, I just don't see that being the case here.

Thanks,

Norm@Home

[Darlis]

Do I understand you correctly that MyDefrag does not consider a file fragmented if it is in multiple segments but those segments are separated by one or more unmovable files?

Yes, that's the "wrap-around" fragmentation.

There are several unmovable system files on an NTFS volume, it's likely that the file was wrapped around some of those.
The Daily and Weekly scripts don't do any sorting (on normal files) and thus create no wrap-around fragmentation.