U
User N
I've been playing around with the Windows Defragmenter and a couple
of third party tools. Each provides a graphical display of what I assume
are logical blocks along with some information about them (fragmented,
unmovable, free, etc). I've got one NTFS partition on my drive, and
the graphical representation presented by defragmenters is something
along these lines:
CCCCCCCCCCMMCCCCUUUUUCCCFFFFFFFFFFFFFBB
Where:
C = Contiguous
M = MFT related
U = Unmovable
F = Free space
B = Many boot related files according to PerfectDisk
Somewhere I read that defragmenters migrate boot related files to the
outer edge of the drive for speed. In the graphical representation of my
drive, said boot files do appear near one end. However, it is the sparse
end with all the free space. I'd think the freespace should be towards
the inner edge. So basically I'm confused, and wondering if the graphic
representations have any correlation with the physical layout of clusters
on a single partition drive. Can anyone point me in the right direction?
of third party tools. Each provides a graphical display of what I assume
are logical blocks along with some information about them (fragmented,
unmovable, free, etc). I've got one NTFS partition on my drive, and
the graphical representation presented by defragmenters is something
along these lines:
CCCCCCCCCCMMCCCCUUUUUCCCFFFFFFFFFFFFFBB
Where:
C = Contiguous
M = MFT related
U = Unmovable
F = Free space
B = Many boot related files according to PerfectDisk
Somewhere I read that defragmenters migrate boot related files to the
outer edge of the drive for speed. In the graphical representation of my
drive, said boot files do appear near one end. However, it is the sparse
end with all the free space. I'd think the freespace should be towards
the inner edge. So basically I'm confused, and wondering if the graphic
representations have any correlation with the physical layout of clusters
on a single partition drive. Can anyone point me in the right direction?