glossary.html

这是NTFS文件0.5版本技术文件

      <dd><a name="dos_file_permissions"></a></dd>
      <dt>DOS File Permissions <a href="#file_permissions">(see File Permissions)</a></dt>

      <dd><a name="dot"></a></dd>
      <dt>Dot, Root Directory <a href="../files/dot.html">(More...) </a></dt>
        <dd>
        Root directory of the disk
        </dd>

      <dd><a name="drive"></a></dd>
      <dt>Drive <a href="#volume">(See Volume)</a></dt>

      <dd><a name="dynamic_disk"></a></dd>
      <dt>Dynamic Disk</dt>
        <dd>
	<pre>
        Dynamic disk SDS, win2k
	</pre>
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="e"></a></dd>

      <dd><a name="ea"></a></dd>
      <dt>$EA <a href="../attributes/ea.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> is used to implement
        the <a href="#hpfs">HPFS</a> extended attribute under NTFS.
        It is only used for OS/2 compatibity.
        </dd>

      <dd><a name="ea_information"></a></dd>
      <dt>$EA_INFORMATION <a href="../attributes/ea_information.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> is used to implement
        the <a href="#hpfs">HPFS</a> extended attribute under NTFS.
        It is only used for OS/2 compatibity.
        </dd>

      <dd><a name="efs"></a></dd>
      <dt>$EFS</dt>
        <dd>
	$EFS is the named $LOGGED_UTILITY_STREAM of any encrypted file.
        <br>See also:
        <a href="#logged_utility_stream">$LOGGED_UTILITY_STREAM</a>.
        </dd>

      <dd><a name="extend"></a></dd>
      <dt>$Extend <a href="../files/extend.html">(More...) </a></dt>
        <dd>
        This <a href="#metadata">metadata</a> directory contains the
        <a href="#metadata">metadata</a> files:
        <a href="#objid">$ObjId</a>,
        <a href="#quota">$Quota</a>,
        <a href="#reparse">$Reparse</a>.
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="f"></a></dd>

      <dd><a name="file"></a></dd>
      <dt>File <a href="../concepts/file.html">(More...) </a></dt>
        <dd>
         In the NTFS terminology, a file can be a normal file, directory
         (like in Linux) or a system file.
        </dd>

      <dd><a name="file_name"></a></dd>
      <dt>$FILE_NAME <a href="../attributes/file_name.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> represents the file's name.
        A file can have one or more names, which can be in any directory.
        This is the NTFS equivalent to Unix's hard links.
        </dd>

      <dd><a name="filename_namespace"></a></dd>
      <dt>Filename Namespace <a href="../concepts/filename_namespace.html">(More...) </a></dt>
        <dd>
        Not all characters are valid in DOS filenames.
        For compatibity NTFS stores which namespace the name belongs to.
        </dd>

      <dd><a name="file_permissions"></a></dd>
      <dt>File Permissions</dt>
        <dd>
        NTFS supports the standard set of DOS file permissions, namely
        <q>Archive</q>, <q>System</q>, <q>Hidden</q> and <q>Read Only</q>.
        In addition, NTFS supports <q>Compressed</q> and <q>Encrypted</q>.
        <br>See also:
        <a href="#security_descriptor">$SECURITY_DESCRIPTOR</a> and
        <a href="#compression">Compression</a>
        </dd>

      <dd><a name="file_record"></a></dd>
      <dt>FILE Record</dt>
        <dd>
        The $MFT is made up of FILE records, so named because of
        a magic number of <q>FILE</q>.  Each record has a standard
        header and a list of attributes.  If the attributes don't
        fit into a single record, then more records will be used
        and a $ATTRIBUTE_LIST attribute will be needed.
        <br>See also:
        <a href="#attribute">Attribute</a>,
        <a href="#attribute_list">Attribute List</a>,
        <a href="#magic_number">Magic Number</a> and
        <a href="#mft">$MFT</a>.
        </dd>

      <dd><a name="file_record_segment"></a></dd>
      <dt>File Record Segment (FRS)</dt>
        <dd>
	<pre>
	FRS = MFT File Record
	</pre>
        </dd>

      <dd><a name="file_reference"></a></dd>
      <dt>File Reference</dt>
        <dd>
        Each file record has a unique number identifying it.
        The first 48 bits are a sequentially allocated number
        which is the offset in the $MFT.  The last 16 bits
        are a sequence number.  Every time the record is altered
        this number is incremented.  The sequence number can
        help detect errors on the volume.

        <br>See also:
        <a href="#file_record">File Record</a>,
        <a href="#mft">$MFT</a> and
        <a href="#volume">Volume</a>.
        </dd>

      <dd><a name="file_runs"></a></dd>
      <dt>File Runs <a href="#data_runs">(See Data Runs)</a></dt>

      <dd><a name="filesize"></a></dd>
      <dt>File Size</dt>
        <dd>
	There are three file sizes that NTFS records.
	Each of them stores the number of bytes
	<ul>
	  <li>R) Real.  The number of bytes of data.</li>
	  <li>A) Allocated.  The size taken up on disk.</li>
	  <li>I) Initialised.  Size of compressed file.</li>
	</ul>

	If the file is compressed, the Initialised Size may be smaller
	than the Real Size.
        </dd>

      <dd><a name="filesystem"></a></dd>
      <dt>Filesystem</dt>
        <dd>
        The physical structure an operating system uses to store and organize files on a storage unit.
	A commonly used filesystem is FAT (used by DOS).
        </dd>

      <dd><a name="fixup"></a></dd>
      <dt>Fixup <a href="#update_sequence">(See Update Sequence)</a></dt>

      <dd><a name="fork"></a></dd>
      <dt>Fork <a href="#resource_fork">(See Resource Fork)</a></dt>

      <dd><a name="fragmented"></a></dd>
      <dt>Fragmented</dt>
        <dd>
         (un)f file
        </dd>

      <dd><a name="frs"></a></dd>
      <dt>FRS <a href="#file_record_segment">(See File Record Segment)</a></dt>

      <dd><a name="fsck"></a></dd>
      <dt>fsck</dt>
        <dd>
        This is a utility to check and repair filesystems.
        Its name is an abbreviation of filesystem check.
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="g"></a></dd>

      <dd><a name="gb"></a></dd>
      <dt>GB <a href="#units">(See Units)</a></dt>

      <dd><a name="guid"></a></dd>
      <dt>GUID <a href="#units">(See Units)</a></dt>
      <dd>
      <pre>
      The valid format for a GUID is {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}

      Globally Unique Identifier (GUID)

      GUID structures store globally unique identifiers (GUID). A GUID is a 
      128-bit value consisting of one group of eight hexadecimal digits, followed
      by three groups of four hexadecimal digits each, followed by one group of
      twelve hexadecimal digits. GUIDs are Microsoft's implementation of the
      distributed computing environment (DCE) universally unique identifier (UUID).
      Example of a GUID:
      	1F010768-5A73-BC91-0010A52216A7

      order stored on disk?

      01020304-0506-0708-090A0B0C0D0E0F010

      0x00  04030201
      0x04  0605
      0x06  0807
      0x08  090A0B0C0D0E0F010
      </pre>
      </dd>

    </dl>

    <hr>

    <dl>
      <dd><a name="h"></a></dd>

      <dd><a name="hex"></a></dd>
      <dt>Hex, Hexadecimal</dt>
        <dd>
        Maths carried out in base sixteen.  In this documentation,
        many numbers represented in hex, e.g. 0x02E0, 0xF100.
        <br>See also:
        <a href="#binary">Binary</a>,
        <a href="#decimal">Decimal</a> and
        <a href="#units">Units</a>.
        </dd>

      <dd><a name="hfs"></a></dd>
      <dt>HFS <a href="#hfs">(See Hierarchical File System)</a></dt>

      <dt>Hierarchical File System (HFS)</dt>
        <dd>
        The MacOS filesystem.
        </dd>

      <dd><a name="hpfs"></a></dd>
      <dt>High Performance File System (HPFS)</dt>
        <dd>
        The OS/2 filesystem. Remember: once upon a time, OS/2 had to be the
        operating system developed by both IBM and Microsoft. There was a break
        between the 2 giants. IBM continued to develop OS/2 (it became OS/2
        Warp), and that explains why OS/2 knows how to execute Windows
        applications. Microsoft decided to make its own operating system:
        Windows NT. HPFS design influenced NTFS design, so the 2 filesystems
        share many features.
        </dd>

      <dt>HPFS <a href="#hpfs">(See High Performance File System)</a></dt>
    </dl>

    <hr>

    <dl>
      <dd><a name="i"></a></dd>

      <dd><a name="i30"></a></dd>
      <dt>$I30</dt>
        <dd>
        This is the named index used by directories.
        The name refers to attribute 0x30 ($FILE_NAME).
        <br>See also:
        <a href="#attribute">Attribute</a>,
        <a href="#directory">Directory</a>,
        <a href="#file_name">$FILE_NAME</a> and
        <a href="#index">Index</a>
        </dd>

      <dd><a name="index"></a></dd>
      <dt>Index</dt>
        <dd>
        (just the whole index idea)
        </dd>

      <dd><a name="index_allocation"></a></dd>
      <dt>$INDEX_ALLOCATION <a href="../attributes/index_allocation.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> contains the location of the entries
        that make up an index.
        </dd>

      <dd><a name="index_root"></a></dd>
      <dt>$INDEX_ROOT <a href="../attributes/index_root.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> is the root of an index.
        The index is stored as a balanced binary tree.
        The only attribute which is indexed is <a href="#file_name">$FILE_NAME</a>
        and the index is called <a href="#i30">$I30</a>.
        </dd>

      <dd><a name="indx_record"></a></dd>
      <dt>INDX Record <a href="../concepts/index_record.html">(More...) </a></dt>
        <dd>
        Index records are used by directories, $Quota, $Reparse
        and $Secure.  The contents depend on the type of index
        being kept.  Directories store $FILE_NAME attributes.
        <br>See also:
        <a href="#directory">Directory</a>,
        <a href="#i30">$I30</a>,
        <a href="#quota">$Quota</a>,
        <a href="#reparse">$Reparse</a> and
        <a href="#secure">$Secure</a>.
        </dd>

      <dd><a name="infinite_logging_area"></a></dd>
      <dt>Infinite Logging Area</dt>
        <dd>
        Something contained in $LogFile. It consists of a
        sequence of 4KB log records.
        <br>See also:
        <a href="#logfile">$LogFile</a>
        </dd>

      <dd><a name="inode"></a></dd>
      <dt>Inode</dt>
        <dd>
        An inode is the filesystems representation of a file, directory, device, etc.
        In NTFS every inode it represented by an MFT FILE record.
        <br>See also:
        <a href="#directory">Directory</a>,
        <a href="#file">File</a>,
        <a href="#file_record">FILE Record</a> and
        <a href="#filesystem">Filesystem</a>
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="j"></a></dd>

      <dd><a name="j"></a></dd>
      <dt>$J</dt>
        <dd>
        $J is a named data stream of the Metadata File $UsnJrnl.
        <br>See also:
        <a href="#usnjrnl">$UsnJrnl</a>
        </dd>

      <dd><a name="junction_point"></a></dd>
      <dt>Junction Point</dt>
        <dd>
        Microsoft term for a mount point, available in NT 5.0.
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="k"></a></dd>

      <dd><a name="kb"></a></dd>
      <dt>KB <a href="#units">(See Units)</a></dt>
    </dl>

    <hr>

    <dl>
      <dd><a name="l"></a></dd>

      <dt>LCN <a href="#lcn">(See Logical Cluster Number)</a></dt>

      <dd><a name="log_record"></a></dd>
      <dt>Log Record</dt>
        <dd>
        One 4KB chunk of the infinite logging area. It starts with
        the magic number 'RCRD' and a fixup, then has undocumented variable
        length data. [The log record might be further subdivided - I cannot
        imagine they waste 4KB if they only have to log a few bytes. Custer
        mentions high level and low level 'records'. High level are: - allocate
        inode n, - make a directory entry foo in directory m low level are: -
        modify inode n with the new contents of <1KB>]
        </dd>