FAT32 and NTFS

catford

This is a big learning curve--Fitting new hard drive -whats the difference between them in relation to the format??

cougar_3

This site sums up the pros and cons of each. Not much between them really!

http://cquirke.mvps.org/ntfs.htm

rogerramjet

ntfs required if you want to set up accounts with passwords - more secure

Mr_Skint_2

Just some Blurb

NTFS or New Technology File System is the standard file system of Windows NT and its descendants Windows 2000, Windows XP and Windows Server 2003. Windows versions 95, 98, 98SE and ME cannot natively read NTFS filesystems, although third-party utilities do exist for this purpose.

NTFS replaced Microsoft's previous FAT file system, used in MS-DOS and early versions of Windows. NTFS has several improvements over FAT such as improved support for metadata and the use of advanced data structures to improve performance, reliability and disk space utilization plus additional extensions such as security access control lists and file system journaling. Its main drawback is its very limited support by non-Microsoft OSes, since the exact specification is a trade secret of Microsoft.

NTFS has five versions: v1.0, v1.1 and v1.2 found in NT 3.51 and NT 4, v3.0 found in Windows 2000 and v3.1 found in Windows XP and Windows Server 2003. These versions are sometimes referred to as v4.0, v5.0 and v5.1, after the version of Windows they ship with. Newer versions added extra features: Windows 2000 introduced quotas.


Internals
In NTFS, everything that has anything to do with a file (file name, creation date, access permissions and even contents) is stored as metadata. This elegant, albeit abstract approach allowed easy addition of filesystem features during the course of Windows NT's development – an interesting example is the addition of fields for indexing used by the Active Directory software. File names are stored in Unicode (encoded as UTF-16, although limited to the BMP in early versions before Windows 2000). The downside of this approach is that corruption of a disk can be difficult to recover from.

Internally, NTFS uses B+Trees to index file system data. Although complex to implement, this allows faster access times in some cases. A file system journal is used in order to guarantee the integrity of the file system itself (but not of each individual file). Systems using NTFS are known to have improved reliability compared to FAT file systems.

Details on the implementation's internals are closed, so third-party vendors have a difficult time providing tools to handle NTFS.

NTFS Partitions can be read by Linux since Version 2.2.0. Linux 2.6 contains a new driver written by Anton Altapamarkov (Cambridge University) and Richard Russon. It offers limited write support. At this time (August 2005) only existing and non-write protected files can be changed and overwritten. The creation and deletion of folders is not yet supported. Full write support is available using Paragon[1]'s NTFS for Linux 3 driver. Alternatively the Windows driver ntfs.sys can be used with Captive NTFS.

Mac OS X v10.4 offers read-only NTFS support.

eComStation offers read-only NTFS support.

The Master File Table (MFT) essentially contains metadata about every file and directory on an NTFS file system. It includes parameters such as location, size, and permissions. It is used to aid in minimizing disk fragmentation.


Interoperability
Microsoft currently provides a tool to convert the FAT32 format to NTFS, but not the other way around. PartitionMagic by Symantec and the open source NTFSResize utility are both capable of resizing NTFS partitions.

For historical reasons, the versions of Windows that do not support NTFS all keep time internally as local zone time, and therefore so do all file systems other than NTFS that are supported by current versions of Windows. However, Windows NT and its descendants keep internal timestamps as GMT/UTC and make the appropriate conversions for display purposes. Therefore, NTFS timestamps are in GMT/UTC. This means that when files are copied or moved between NTFS and non-NTFS partitions, the OS needs to convert timestamps on the fly. But if some files are moved when summer or "daylight" local time is in effect, and other files are moved when winter or "standard" local time is in effect, there can be some ambiguities in the conversions. As a result, especially shortly after one of the days on which local zone time changes, users may observe that some files have timestamps that are incorrect by one hour.


Features
NTFS 5.0 was the third version of NTFS to be introduced to the Windows world by Microsoft. It included several new features: quotas, sparse file support, reparse points, distributed link tracking and the Encrypting File System (EFS).

Alternate Data Streams (ADS)
ADS allows files to be associated with more than one data stream. For example, a file such as text.txt can have a ADS with the name of text.txt:secret.txt (of form filename:ads) that can only be accessed by knowing the ADS name or by specialized directory browsing programs. Alternate streams are not detectable in the original file's size but are lost when the original file (i.e. text.txt) is deleted, or when the file is copied or moved to a partition that doesn't support ADS (e.g. a FAT partition, a floppy disk, or a network share). While ADS is a useful feature, it can also easily eat up hard disk space if not detected or forgotten.
Quotas
File system quotas were introduced in NTFS 5. They allow the administrator of a computer that runs a version of Windows that supports NTFS to set a threshold of disk space that users may utilise. It also allows administrators to keep a track of how much disk space each user is using. An administrator may specify a certain level of disk space that a user may use before they receive a warning, and then deny access to the user once they hit their upper limit of space. Disk quotas do not take into account NTFS's transparent file-compression, should this be enabled. Applications that query the amount of free space will also see the amount of free space left to the user who has a quota applied to them.
Sparse files
These are files which are mostly filled with zeros. This is called a sparse data set, and most things that generate such data sets are scientific applications, and they can generate very large sparse data sets. Because of this, Microsoft has implemented support for sparse files by only allocating disk space for regions that do not contain blocks of zero data. An application that reads a sparse file reads it in the normal manner with the file system calculating what data should be returned based upon the file offset. As for compressed files, the actual size of sparse files are not taken into account when determining quota limits. [2]
Reparse points
Introduced in NTFS 5.0. These are used by associating a reparse tag in the user space attribute of a file or directory. When the object manager (see executive) parses a file system name lookup and encounters a reparse attribute, it knows to reparse the name lookup, passing the user controlled reparse data to every file system filter driver that is loaded into Windows 2000. Each filter driver examines the reparse data to see if it is associated with that reparse point, and if that filter driver determines a match then it intercepts the file system call and executes its special functionality. Reparse points are used to implement Volume Mount Points, Directory Junctions, Hierarchical Storage Management, Native Structured Storage and Single Instance Storage:
Volume mount points
Similar to Unix mount points, where the root of another file system is attached to a directory. In NTFS, this allows additional file systems to be mounted without requiring a separate drive letter (like C: or ) for each.
Directory Junctions
Similar to Volume Mount Points, but reference other directories in the file system instead of other volumes. For instance, the directory C:\exampledir with a directory junction attribute that contains a link to \linkeddir will automatically refer to the directory \linkeddir when it is accessed by a user-mode application. They are the equivalent of a Unix symbolic link, though in Unix a symbolic link can be applied on files as well as on directories [3].
Hard links
Similar to directory junctions, but used for files instead of directories. Hard links can only be applied to files on the same volume since a second MFT record is added to point at the same data on the current volume.
Hierarchical Storage Management (HSS)
Hierarchical storage management is a means of transferring files that are not used for some period of time to less expensive storage media. When the file is next accessed the reparse point on that file determines that it is needed and retrieves it from storage.
Native Structured Storage (NSS)
NSS was an ActiveX document storage technology that has since been discontinued by Microsoft. It allowed ActiveX documents to be stored in the same multi-stream format that ActiveX uses internally. An NSS file system filter was loaded and used to process the multiple streams transparently to the application, and when the file was transferred to a non-NTFS formatted disk volume it would also transfer the multiple streams into a single stream [4].
Volume Shadow Copy (VSS)
Efficiently keeps historical versions of files and folders on NTFS volumes by copying old, newly-overwritten data to shadow copy (copy-on-write). The old file data is overlaid on the new when the user requests a revert to an earlier version. On heavily loaded systems, Microsoft recommends setting up a shadow copy volume on separate disk to reduce the I/O load on the main volume.
File compression
NTFS can compress files using a variant of the LZ77 algorithm (also used in the popular ZIP file format). [5] Although read-write access to compressed files is transparent, Microsoft recommends avoiding compression on server systems and/or network shares holding roaming profiles because it puts a considerable load on the processor. [6]
Single Instance Storage (SIS)
When there are several directories that have different, but similar files, some of these files may have identical content. Single instance storage allows identical files to be merged to one file and create references to that merged file. SIS consists of a file system filter that manages copies, modification and merges to files; and a user space service (or groveler) that searches for files that are identical and need merging. SIS was mainly desiged for remote installation servers as these may have multiple installation images that contain many identical files; SIS allows these to be consolidated but, unlike for example hard links, each file remains distinct; changes to one copy of a file will leave others unaltered [7].
Encrypting File System (EFS)
Provides strong and user-transparent encryption of any file or folder on an NTFS volume. EFS works in conjunction with the EFS service, Microsoft's CryptoAPI and the EFS File System Run-Time Library (FSRTL). As of February 2004, its encryption has not been compromised.
EFS works by encrypting a file with a bulk symmetric key (also known as the File Encryption Key, or FEK), which is used because it takes a relatively smaller amount of time to encrypt and decrypt large amounts of data than if an asymmetric key cipher is used. The symmetric key that is used to encrypt the file is then encrypted with a public key that is associated with the user who encrypted the file, and this encrypted data is stored in an alternate data stream of the encrypted file. To decrypt the file, the file system uses the private key of the user to decrypt the symmetric key that is stored in the file header. It then uses the symmetric key to decrypt the file. Because this is done at the file system level, it is transparent to the user. [8] Also, in case of a user losing access to their key, support for recovery agents that can unencrypt files has been built in to the EFS system.
Symbolic links
Introduced in Windows Vista onward, they are similar to Windows' shortcuts, but inside the NTFS' metadata.
[edit]
Limitations
The following are a few limitations of the NTFS file system.

Reserved File Names
Though the filesystem supports paths up to ca. 32,000 Unicode characters with each path component (directory or filename) up to 255 characters long, certain names are unusable, since NTFS stores its metadata in regular (albeit hidden and for the most part inaccessible) files; accordingly, user files cannot use these names. These files are all in the root directory of a volume (and are reserved only for that directory). The names are: $Mft, $MftMirr, $LogFile, $Volume, $AttrDef, . (dot), $Bitmap, $Boot, $BadClus, $Secure, $Upcase, and $Extend [9]; . and $Extend are both directories, the others are files.
Maximum Volume Size
In theory, the maximum NTFS volume size is 264-1 clusters. However, the maximum NTFS volume size as implemented in Windows XP Professional is 232-1 clusters. For example, using 64 KiB clusters, the maximum NTFS volume size is 256 TiB minus 64 KiB. Using the default cluster size of 4 KiB, the maximum NTFS volume size is 16 TiB minus 4 KiB. Because partition tables on master boot record (MBR) disks only support partition sizes up to 2 TiB, you must use dynamic volumes to create NTFS volumes over 2 TiB.
Maximum File Size
Theory: 16 EiB minus 1 KiB (264 bytes minus 1 KiB). Implementation: 16 TiB minus 64 KiB (244 bytes minus 64 KiB)
Alternate Data Streams
When a multi-stream file is copied to non-NTFS volumes, only the main stream is copied and the lost data are not re-gained by re-copying the file to a NTFS drive.

payless

did you type that all yourself ?

Mr_Skint_2

payless wrote:

did you type that all yourself ?

Did I heck :rotfl: I knew what NTFS is and does but know way was I gonna type it, One paper on it is enough... :beer:

John_Gray

Isn't the standard response to that sort of outburst of data, "Too Much Information"?!

My summary would be:
a) use NTFS
b) keep to the default 4 kB cluster/allocation size
c) if you use the CONVERT program to change the disk from FAT-32 to NTFS you get a 512 byte cluster size, so try to format it as NTFS from scratch, before installing any files on it

There, wasn't that simpler?! [evilgrin]

John

Mr_Skint_2

John_Gray wrote:

Isn't the standard response to that sort of outburst of data, "Too Much Information"?!

My summary would be:
a) use NTFS
b) keep to the default 4 kB cluster/allocation size
c) if you use the CONVERT program to change the disk from FAT-32 to NTFS you get a 512 byte cluster size, so try to format it as NTFS from scratch, before installing any files on it

There, wasn't that simpler?! [evilgrin]

John

And thats why up the top of the post it says

Just Some Blurb...... = Way to much info..... :rotfl:

catford

Mr skint --I nearly missed my tea reading that lot!!but it's as clear as mud now .cheers----ntfs for me!

CIS

One problem with NTFS, if your have drive problems goes you cant access it from DOS like you can with FAT32 (you need something like NTFSDOS).

Being able to access a disk in DOS can sometimes give you little bit extra when your drive goes belly up.

DonnyDave

I've just got an Acer Aspire 5622 Laptop and found it's FAT32. Can't work out whether that's good or bad.

What's more, it has two partitions; the everyday one and one 'factory restore' one. Both are 35GB which means that my available space if therefore 35GB and not 80GB as the specification states.

I've just burned a restore DVD, as the eRecovery software advised. Can I remove or reduce the size of this 'hidden' partition to gain more space on the main one?