Fragmaster

I completely agree with Super Fast. When navigating any Windows system folders (idk why anyone would want to, but it happens), seeing a file that you can't interact with and that has a funny name is a common occurance. However, seeing a file without a name, properties, or purpose causes a 'WTF?' reaction. These ghost blocks should list the names of the files within them and identify them as metafiles so that we can know that they are functioning and not a 'WTF?' type of glitch. I can see how not identifying them could safeguard against novice users attepting to edit these files and causing system instability, but labeling them as metafiles would tell everyone that they can't be moved or edited. I'm not entirely convinced that romanoff's explanation is necessarily addressed to this specific problem though. $MFT and $User.Dat are displayed in Defraggler along with other non-defragglerable files, so how are these other metafiles special by being "not in the block"?

SOLUTION When I used WINDOWS(XP SP3 version)Defragmenter, the ghost blocks were removed, almost all of them. The afterimage of one large file still remained, but I can live with that. Used WINDOWS Defragmenter in Computer Management to get rid of most (if not all) of these pesky blocks.

I understand your point, Rob, your point is correct and totally valid. I think all of us here know that a few (even several), large file fragments are totally acceptable (even though they're a bit of an eyesore). But what Okan and myself want to know is: FYI I'm gonna call these blue blocks with no files "ghost blocks". They mess with your files, but when you turn on the lights... nothing's there. Spooky. Annoying. Intangible. That's a ghost. What ARE these empty blue boxes, and why are we having these problems? Why can't we get rid of them? Is Piriform working on this problem? (I would think that they are, they seem to be real good people) And when can we expect a fix? I'm very interested in these answers because I've recently discovered that my \C drive has over one hundred and twenty five of these annoying little blocks. I know that at this point these ghost blocks are definitely not impacting my laptop's performance, yet. However, I'm certain that there are many other people out there experiencing the same problem that we are. Most probably don't have enough of these pesky blocks to affect performance, but some may have so many ghost blocks that the performance of their drive's are being impaired. My eleven gigabyte Batman: The Dark Knight digital copy would probably be in at least forty fragments, if I were to move it onto my \C drive (which I won't). Now, that isn't enough fragments to ruin an eleven gig movie, it might only cause a short pause every ten minutes or so. But I want answers for the few people whose drives have so many ghost blocks that they are having problems. Any new information would be greatly appreciated. The considerate response of a Piriform rep. would be amazing!

My \C drive has over a hundred of these "no file in block" blocks (hereafter reffered to as ghost blocks). Ghost blocks seem to be keeping me from writing large files to the drive without chopping them up into several fragments. (which isn't really a big deal, but it's annoying ) ghost blocks do not respond to "defrag freespace". Are these ghost blocks truly empty? Will my computer write over them without any issues? Or are they impacting my drive's writing performance? Most importantly, are they impacting Defraggler's performance? Also, does Defraggler know that these blocks are actually empty? Will it write over them during "defrag drive"? Example: If I told defraggler to "move large files to end of drive" and there were several of these ghost blocks at short intervals near the very end of the drive, and Defraggler first moved and a very large file to the end of the drive, would Defraggler actually report that very large file (say, about 2GB) was fragmented over those ghost blocks? My question really is: Is Defraggler imagining these blue ghost blocks and making it's own job exceedingly more difficult? UPDATE: The number of ghost blocks on my C\ drive have increased dramatically! Very bad news. I still don't know for sure if these blocks fragmaent larger files, but they're sticking to my drive and it's starting to become a problem. Now there are blocks that are colored solid dark blue (denoting not fragmented full occupancy) that have "no files in block. Many of these blocks are obiously afterimages of previously moved files. I'm starting to get worried about the health of my drive. I literally have hundreds of these ghost blocks on my C: drive now