NTFS Master File Table (MFT)
Each file on an NTFS volume is represented by a record in a special file called the master file table (MFT). NTFS reserves the first 16 records of the table for special information. The first record of this table describes the master file table itself, followed by a MFT mirror record. If the first MFT record is corrupted, NTFS reads the second record to find the MFT mirror file, whose first record is identical to the first record of the MFT. The locations of the data segments for both the MFT and MFT mirror file are recorded in the boot sector.
NTFS includes several system files, all of which are hidden from view on the NTFS volume. A system file is one used by the file system to store its metadata and to implement the file system. System files are placed on the volume by the Format utility.Table 5-4 Metadata Stored in the Master File Table
System File | File Name | MFT Record | Purpose of the File |
---|---|---|---|
Master file table | $Mft | 0 | Contains one base file record for each file and folder on an NTFS volume. If the allocation information for a file or folder is too large to fit within a single record, other file records are allocated as well. |
Master file table 2 | $MftMirr | 1 | A duplicate image of the first four records of the MFT. This file guarantees access to the MFT in case of a single-sector failure. |
Log file | $LogFile | 2 | Contains a list of transaction steps used for NTFS recoverability. Log file size depends on the volume size and can be as large as 4 MB. It is used by Windows NT/2000 to restore consistency to NTFS after a system failure. |
Volume | $Volume | 3 | Contains information about the volume, such as the volume label and the volume version. |
Attribute definitions | $AttrDef | 4 | A table of attribute names, numbers, and descriptions. |
Root file name index | $ | 5 | The root folder. |
Cluster bitmap | $Bitmap | 6 | A representation of the volume showing which clusters are in use. |
Boot sector | $Boot | 7 | Includes the BPB used to mount the volume and additional bootstrap loader code used if the volume is bootable. |
Bad cluster file | $BadClus | 8 | Contains bad clusters for the volume. |
Security file | $Secure | 9 | Contains unique security descriptors for all files within a volume. |
Upcase table | $Upcase | 10 | Converts lowercase characters to matching Unicode uppercase characters. |
NTFS extension file | $Extend | 11 | Used for various optional extensions such as quotas, reparse point data, and object identifiers. |
12-15 | Reserved for future use. | ||
Quota management file | $Quota | 24 | Contains user assigned quota limits on the volume space. |
Object Id file | $ObjId | 25 | Contains file object IDs. |
Reparse point file | $Reparse | 26 | This file contains information about files and folders on the volume include reparse point data |
MFT Structure
The master file table allocates a certain amount of space for each file record. The attributes of a file are written to the allocated space in the MFT. Small files and directories (typically 512 bytes or smaller), such as the file illustrated in next figure, can entirely be contained within the master file table record.MFT Record for a Small File or Directory:
This design makes file access very fast. Consider, for example, the FAT file system, which uses a file allocation table to list the names and addresses of each file. FAT directory entries contain an index into the file allocation table. When you want to view a file, FAT first reads the file allocation table and assures that it exists. Then FAT retrieves the file by searching the chain of allocation units assigned to the file. With NTFS, as soon as you look up the file, it's there for you to use.
Directory records are housed within the master file table just like file records. Instead of data, directories contain index information. Small directory records reside entirely within the MFT structure. Large directories are organized into B-trees, having records with pointers to external clusters containing directory entries that could not be contained within the MFT structure.
Cross linked from ntfs.com
Post a Comment