Windows Server 2003 - Filesystem
Home | Editions | Security | Active Directory | Resources | Contents
Get the Book
Major Topics

Editions
Security
Active Directory
Resources
Contents
Other Topics
Up
MMC
Filesystem
Printers
Profiles
Policy
Installation
More Detail
Compression
EFS
Quotas
Shares
Web Sharing
ClientSide Caching
Dfs

Memory from Crucial.com


©2004 Team Approach Limited
All rights reserved


Feature FAT FAT32 NTFS v4 NTFS v5
Max size 4 GB 2 TB 16 EB 16 EB
Long names
Security    
Recoverable    
POSIX support    
Macintosh support    
Compression    
Quotas      
Encryption      
Property sets      
Junction points      
Link tracking      
AD support      

NTFS v5 had more features than any other Microsoft filesystem. NTFS v4 volumes are converted to NTFS v5 during an upgrade.

 Recoverable Filesystem

NTFS is recoverable because file system transactions are logged. If the filesystem becomes corrupt because of a system failure, the system checks the transaction log and automatically fixes any errors. The recovery is restricted to the file system infrastructure or metadata (eg. MFT Master File Table). Problems, such as lost clusters, which are common with the FAT fileystem, do not occur with NTFS. Although the file system metadata is protected, user data in the file contents may be lost. File contents can be protected using RAID technology.

C:   D: E:  

Æ
     

 
use Disk Management console    

Æ
use linkd

 

    
use linkd    
     
       
       
         

Junction Points

Junction Points provide a mechanism to create logical folders that take the user to folders in other volumes or other folders in the same volume. It provides a way to logically reorganize the tree structured file system without physically moving the files.

The following diagram shows 3 Junction Points represented by the top left folders. The first points to another volume and is created with the Disk Management console. The other junction points created with the LINKD command can link to other folders on other or the same volume.

Junction points are created with empty folders. Any valid local pathname can be mounted at the junction point. With junction points, local volumes do not need drive letters because they can be accessed through a junction point folder. This eliminates the volume restriction limited by the 26 letter alphabet. Drive letters can be removed from a volume by using the Disk Management console.

 

Reparse Points

Either folders or files can be tagged as reparse points. The reparse point tag redirects requests to the appropriate file system filter. The junction point filter redirects the request to the target path. The remote storage filter redirects the request to the remote storage manager.

Normal I/O request   Junction Point request   Remote Storage request    
↓  ↑    
↓  ↑ NTFS  
↓  ↑    
   
normal    
access   Junction Point filter   Remote Storage filter    

Distributed Link Tracking

Distributed link tracking will automatically update shortcuts and OLE links when the destination files and folders are moved or renamed. When a file that is referenced by a link is moved to another volume the Distributed Link Tracking server creates an object in Active Directory so that it can be tracked. Distributed Link Tracking is supported by the Distributed Link Track Client and Server services. Because of a potentially large overhead, these servers are disabled by default in Windows Server 2003.

ÅÆ

Distributed Link Tracking can automatically update OLE links in a MS-Word document when referenced files are moved or renamed.

 

 

Property Sets - Multiple Data Streams

Property Sets provide additional properties to any file or directory as shown for the MS-Word document example to the right.

Defragmentation

http://teamapproach.ca/trouble/Defragment.htm

Dynamic Disk

http://teamapproach.cal/trouble/DynamicDisk.htm