Question Locked

MFT padding - diskeeper - 3.7Gb???

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, I noticed some discussion on this forum and hope someone could explain this.

I used a current version of Diskeeper (Frag Shield) to pad the MFT as it advised. Ok on a couple of partitions, but one one, I noticed a huge amount of System reserved space.

This turned out to be
\$Extend\$UsnJm1

O&O lists this as MFT.

The size is incredible- 3.7Gb.

But Windows says the partition is 12.3Gb, used space 6.3Gb, 6Gb free.

Any ideas welcome! Thanks.

(One post here relates something that sounds similar, but incidental to its main topic).

4 replies

by who am i really

that's why it says it's a good idea to bloat the MFT in advance;

however, this is only necessary if the system is going to be a file server with millions or more small to medium sized user files

I run all my work stations without diskkeeper and there's no need to bloat the MFT

I have a 6 year old XP install and the MFT has never gone beyond 2 fragments on a 100GB partition

however, that partition is only used for OS / Programs & temporary working copies of files, all stored user files are on separate HDDs

if I was storing a full disk of user files then I may have a sorely fragmented MFT but seriously doubt it with a 100GB partition
but, if it was a 2TB C:\ then I'd say it could become a problem, but only if the partition was used for user files.

so, pre-bloating the MFT isn't necessary for a workstation and will play havoc with backup sizes, but can be beneficial for a File Server with large disk(s)

yes I see, that this old but it was never answered, so I answered it.

by seanferd

I'be got an 80Gb drive with 20Gb free and I grew the MFT space with DK some time ago as it was at 99% full. After, the allocated size was still only 158Mb.

If you have millions of tiny files, 3.7 Gb may be almost reasonable, but I rather suspect an error in reporting where a G was used instead of an M.

You can always manually reconfigure for a certain number of files (get the file count from your drive and double it, or something). Check the result. Then let DK do it again and see what happens.

Of course, if you had manually configured it when growing the MFT space, perhaps you had put in an overly large number.

by who am i really

by the calculation show by the OP 370MB makes more sense than 3.7GB

the last time I used diskkeeper all it had was an MFT percentage slider and no way to give it an exact number

and I ended up with a 1500MB MFT on a 320GB HDD,
which I soon learned I would never ever use, given the fact that I don't store my user files on the C:\
and even still
my 1398GB E: HDD with only 280GB free and 10's of thousands of files, the MFT still isn't anywhere near the size of the C:\ MFT that diskkeeper bloated.

too bad there's no way to purge obsolete MFT records

that was and still is the number one advantage of a FAT formatted disk
because a properly programmed defrag utility will reset the FAT to only contain records of existing files / folders
and all references to deleted files are removed, thus shrinking the fat chain

This discussion is closed to new replies.