Take advantage of Windows 7's Disk Defragmenter to get detailed drive data

As you know by now, Microsoft Windows 7’s Disk Defragmenter is configured to run on a regular schedule right out of the box. And, when it runs, it is hidden in the background with no visible interface or icon. This means that Disk Defragmenter will always keep your hard disk in tip-top shape and you never even have to think about defragmenting your hard disk.

This is an awesome feature as disk fragmentation can take a huge toll on the overall performance of your operating system. For instance, disk defragmentation can be the source of long boot-times, random crashes, as well as unexplained lock-ups. In fact, an extremely fragmented hard disk can even prevent a system from booting up.

Even though the disk defragmenting operation is totally automated in Windows 7, such that you really never need to manually run the utility, the user interface in Disk Defragmenter has been redesigned so that it can provide you with detailed defragmentation status information, allowing you to monitor the progress of the operation if you wish to run it manually.

In this edition of the Windows Desktop Report, I’ll take a closer look at Windows 7’s Disk Defragmenter. As I do, I’ll describe and show you how to take advantage of the new features built in to the new version.

The problem of disk fragmentation

Before we get started with the new Disk Defragmenter, let’s briefly explore the problem of fragmentation. You probably already know that disk fragmentation is a normal occurrence that happens over time as you use your hard disk.

On the hard disk, a cluster is the smallest unit of disk space that the operating system can address, and as such it is the smallest amount of space that can be allocated to a file. On a typical hard disk formatted with NTFS, the maximum default cluster size is 4KB, or 4,096 bytes.

Every time you copy new files to and delete old files from your hard disk, as well as when you add information to existing files, chances are good that your hard disk is becoming more and more fragmented with each operation you perform. For example, when you copy a file to your hard disk, the operating system attempts to place the file into the first available cluster that it finds on the hard disk. If the file is larger than that cluster, the operating system breaks the file into pieces and attempts to place the rest of the file in the next available clusters. If these subsequent clusters are not located right next to the first one, the file is fragmented.

Fragmentation also occurs when you add information to an existing data file. If the file you’re working on outgrows its original cluster, the operating system will place the rest of the file in the next available cluster. Again the file becomes fragmented when the next available cluster isn’t located right next to the first one. Furthermore, each time you delete files from your hard disk, you create available clusters, thus increasing the chances for future file fragmentation — especially if the files you delete are themselves fragmented.

Over time, fragmentation can become a big problem if left unchecked. As pieces of files become spread out, the hard disk’s read/write heads have to do more work to locate and transfer files to memory. The more the read/write heads move, the longer it takes to access files. Consequently, hard disk performance suffers.

Windows 7’s answer to the problem

Of course, the answer to this problem is to defragment the hard disk on a regular basis in order to keep all of the related pieces of a file as contiguous as possible. However, rather than attempting to keep every single piece of a file in one place, as Windows XP’s Disk Defragmenter did, Windows 7’s Disk Defragmenter uses a new algorithm that analyzes each piece of a fragmented file and determines its size.

If a piece is larger than 64MB, then it is left where it is. The reason being that a piece that large will have a smaller impact on performance during disk read/write operations as opposed to the performance hit that Disk Defragmenter would take if it attempted to move the piece closer to the rest of the file. In other words, the benefit gained from leaving the 64MB fragment where it is far outweighs the benefit of moving it.

For example, moving one 64MB piece closer to the rest of the file’s other pieces could potentially involve moving hundreds or thousands of other file pieces in order to make room. Doing so is a very disk-intensive operation that can cause other problems. For example, the additional disk I/O can put unnecessary wear and tear on the disk’s physical components and increase the MTBF. Furthermore, Disk Defragmenter will hog system resources, and the system will be less responsive if you happened to need to perform some work while the hard disk was being defragmented. Another thing to consider is what happens to all those pieces that Disk Defragmenter was working on when it gets interrupted? Chances are that the fragmentation could get worse.

As such, Windows 7’s Disk Defragmenter is designed to recognize that a certain amount of fragmentation is acceptable and that it can finish its job more quickly and more efficiently.

Source: TechRepublic