I think if you defrag all files start at the 1 sector, sort by name, it may finish faster and 0 fragment.
I using PerfectDisk for 10 year but it doesn't support portable.
You cannot stop a file system from fragmenting it's the behaviour caused by deleting, appending data and downloading (appending) files.
Furthermore having files in alphanumeric order won't speed up file access anymore than having them arranged in size order because you also have the hard drive's cache RAM to take into consideration.
Richard S.
I would like to use this function on USB drive. I can't sucessful defrag .ISO file. Grub4dos require file that unfragment. I tried every softwares out there but none of them successful. Then I deleted all files and re-copy file to my USB drive again.
You don't really need to defrag USB drives (I'm assuming you mean a flash drive) because they use flash memory which doesn't suffer from fragmentation because there's no head to reposition.
You don't really need to defrag USB drives (I'm assuming you mean a flash drive) because they use flash memory which doesn't suffer from fragmentation because there's no head to reposition.
I do believe that you are incorrect on this.
While flash drives have no moving parts, fragmentation is not something that occurs only if a drive is spinning. Files can be very fragmented on a flash drive, the same as on a normal rotary drive.
The key difference is, the controller unit may see it a different way because of how flash drives handle "fragmented" files.
Ordinarily, the end user would not notice a thing, but certain software(s) requiring a file to be fully contiguous may throw a fit.
Files may be spread all over a flash drive (non-contiguous).
Although the performance is much better due to the speed of the memory & having no moving parts, this in no way relates to fragmentation (or lack thereof) on a drive.
Flash drives can become very fragmented. It may appear to be contiguous because of how the controller unit presents it to the OS, but at a deeper level, it's really not.
I understand what the guy is saying here.
* To be honest, BECAUSE of the way the files are handled, it may be impossible to make files fully contiguous (at least on partially filled drives, depending on available contiguous free space & file size being copied over) because of the way the controller unit handles things. I suspect, that it may even fragment files on a fully blank configuration. The operating system will not see this, because the controller steps in.
I am sure that some other programs ignore this & have their own way of finding out, whether it is through actually accessing the file (on access scanning) for contiguousness, or whatever...
Winapp is correct in general terms, for reasons which have been explained both in this forum and ad infinitum elsewhere. What defragger users see is the logical representation of the clusters on the drive as held in the MFT, and that's what gets defragged. Whilst on a HD the physical representation of the clusters is close(ish) to the logical rep, on an SSD there is no representation whatsoever, either before or after defragging. The only advantage of defragging an SSD is that you would reduce the logical I/O's when requesting a file.
A USB flash drive may work better with chunks of KB data in contiguous alignment but a fragmented file system is unlikely to cause noticeable slow down when compared to a hard drive of moving parts.
Furthermore due to limited write cycles (before malfunctioning) it's not advisable to defrag because this would involve a lot of reading and writing data.
Richard S.
Winapp is correct in general terms, for reasons which have been explained both in this forum and ad infinitum elsewhere. What defragger users see is the logical representation of the clusters on the drive as held in the MFT, and that's what gets defragged. Whilst on a HD the physical representation of the clusters is close(ish) to the logical rep, on an SSD there is no representation whatsoever, either before or after defragging. The only advantage of defragging an SSD is that you would reduce the logical I/O's when requesting a file.
Yes, you are correct. It is not advisable to defrag such a drive due to the limitations of write cycles (although normal pata/sata have limited write cycles, in the sense that sectors can go bad, etc, but it may take longer).
The reason a normal pata/sata drive is defragged, is to yield better drive performance & reduced overhead through contiguous block reads.
SSD drives would have a slightly lower I/O when defragged, but they are so much faster than normal drives due to not having to spin up or down that it wouldn't even be noticeable.
the way to "defragment" flash is to cut all information from the drive & then repaste it back into the drive.