JS
Not many users of Windows XP would find choosing FAT 32 over NTFS a
better choice. There is no MFT file in FAT32. MFT is a product of
NTFS! I am not sure why you have introduced FAT32 to this debate.
The originator of this thread refers to "inode data".
"A data structure holding information about files in a Unix file
system. There is an inode for each file and a file is uniquely
identified by the file system on which it resides and its inode
number on that system. Each inode contains the following
information: the device where the inode resides, locking
information, mode and type of file, the number of links to the file,
the owner's user and group ids, the number of bytes in the file,
access and modification times, the time the inode itself was last
modified and the addresses of the file's blocks on disk. A Unix
directory is an association between file leafnames and inode
numbers. A file's inode number can be found using the "-i" switch to
ls." source: tldp.org/LDP/sag/html/glossary.html
Inode data seems to be specific to Unix not Windows! Odd that it
should be mentioned in the Subject of this thread.
~~~~
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
JS said:
It's not.
And if you were using FAT32 instead of NTFS and had the same files
as Gerry has on his partition then you would really see some
significant fragmentation (not reported but the fragmentation is
there) because of the folders splattered all over the partition and
the way some defragmentation tools ignore folder clusters and
sandwiched a single file between three of four folders.
JS
How often is the MFT file a really significant size in terms of the
size of modern hard drives.
The size of the of the MFT file on my 24 gb windows partitition is
79 mb! ~~~~
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
VanguardLH wrote:
Antonio Perez wrote:
VanguardLH (e-mail address removed) wrote previously in
microsoft.public.windowsxp.hardware:
Once the free sectors beyond the reserved MFT space gets
consumed, additional files will start consuming the "reserved"
MFT space.... [big snip]
You are missing completely the point here, the explanation i've
read in painful detail somewhere else.
The point is: What to do _after_ is fragmented...
After all that work, and assuming you increased the
NtfsMftZoneReservation before reformatting the partition, when you
run defrag.msc and run Analyze to look at the report, what is the
value for "Percent MFT in use"?
Was all this effort for a data-only partition? Or did you somehow
do all this for the partition containing Windows?
