We get a lot of fragmentation causing file system errors requiring (unmounted) AutoCheck.
I thought that wasn't possible with NTFS but apparently the first version(s) of it do have such a "feature". (I have several files with thousands of fragments but there is no sign of file system corruption). You should also check if the disk itself is healthy and not starting to fail.
but I want (also) to oik out the big database files into free space at the end of the disk.
That is not a good idea since the end of the disk is a lot slower than the beginning.
About the script:
- AddGap does not really "add" a gap to a zone. You always have to use "ZoneEnd + ..." to achieve that.
- By using the AddGaps you're wasting the first few mb's of the disk. The default scripts have a MakeGap(0) to reset the zone point to the beginning of the disk, using the fast space there.
- You're writing in the comments that you're adding 10% but instead you add 20% (if you would fix your AddGaps like I've mentioned above)
You should rethink your placement strategy. Take a look at the default scripts, they exclude a lot of unused files that are best placed towards the slow end of the disk.