Consider the following case: a disk has two very large files stored one after the other - the first being slightly smaller than the second. As far as I know (and please correct me if I'm wrong) - If I delete the first - defragmenting the drive will NOT move the second to where the first was. Is there any way to tell the defragmenter to do that?
I want to store disk images on a drive, and that when I create a new one, and delete an old one - the defragmenter will compact them (-move them close together), so that there will be room for the next one, so that every image will be stored sequentially (-all of its bytes). If the files will not be "compacted" (in the sense mentioned above) - when the drive will have files till close to its end - it will start fragmenting the files. Which is what I want to avoid.
No 3rd party tools please.
I don't have performance issues unless I unwisely fill a pool to more then 80% full- I want to store as many disk images as I can to serve as a makeshift "system restore"-system (because system restore does delete user files (such as JavaScript files).) So yes, it will be very full. – ispiro Jan 26 '15 at 18:58