ExFAT

src: i.ytimg.com

exFAT (Extended File Allocation Table) is a Microsoft file system introduced in 2006 optimized for flash memory such as USB flash drives and SD cards. It is proprietary and Microsoft owns patents on several elements of its design.

exFAT can be used where the NTFS file system is not a feasible solution (due to data structure overhead), yet the file size limit of the standard FAT32 file system (i.e. 4 GiB) remains.

exFAT has been adopted by the SD Card Association as the default file system for SDXC cards larger than 32 GiB.

Video ExFAT

Overview

exFAT was first introduced in late 2006 as part of Windows CE 6.0, an embedded Windows operating system. Most of the vendors signing on for licenses of exFAT are either for embedded systems or device manufacturers that produce media that will be preformatted with exFAT. The entire File Allocation Table (FAT) family, exFAT included, is used for embedded systems because it is lightweight and is better suited for solutions that have low memory and low power requirements, and can be implemented in firmware.

exFAT allows individual files larger than 4 GiB, facilitating long continuous recording of HD video which can exceed the 4 GiB limit in less than an hour. Current digital cameras using FAT32 will break the video files into multiple segments of approximately 2 or 4 GiB. With the increase of capacity and the increase of data being transferred, the write operation needs to be made more efficient. SDXC cards, running at UHS-I have a minimum guaranteed write speed of 10 MBps and exFAT plays a factor in achieving that throughput through the reduction of the file system overhead in cluster allocation. This is achieved through the introduction of a cluster bitmap and elimination (or reduction) of writes to the FAT. A single bit in the directory record indicates that the file is contiguous, telling the exFAT driver to ignore the FAT. This optimization is analogous to an extent in other file systems, except that it only applies to whole files, as opposed to contiguous parts of files.

exFAT is also supported in a number of media devices such as modern flat panel TVs, media centers, and portable media players.

Some vendors of flash media, including USB pen drives, compact flash (CF) and solid state drives (SSD) are shipping from the factory with some of their high capacity media pre-formatted with the exFAT file system. For example, Sandisk ships their 256 GB CF cards as exFAT.

Maps ExFAT

Technical specialities

File name lookup

Like NTFS and HFS+, exFAT is a proprietary file system. Microsoft asserts that exFAT is covered by US Patent 8583708, awarded on November 27, 2013, and US Patent 8321439, Quick File Name Lookup Using Name Hash, which is an algorithm used in exFAT to speed up file searches. Microsoft had also applied for, and so far in some cases, received additional US patents on separate components that are used within exFAT. Since Microsoft has not officially released the entire exFAT specification, the Name Hash patent application is a key document in providing internal details in the understanding of the file system, since those details were revealed in Appendix A of the application.

File and cluster pre-allocation

Like NTFS, exFAT can pre-allocate disk space for a file by just marking arbitrary space on disk as 'allocated'. For each file, exFAT uses two separate 64-bit length fields in the directory: the Valid Data Length (VDL) which indicates the real size of the file, and the physical data length.

To provide improvement in the allocation of cluster storage for a new file, Microsoft incorporated a method to pre-allocate contiguous clusters and bypass the use of updating the FAT table and on December 10, 2013 the US patent office granted patent US8606830. One feature of exFAT (used in the exFAT implementation within embedded systems) provides atomic transactions for the multiple steps of updating the file system metadata. The feature, called Transaction Safe FAT, or TexFAT, was granted a patent by the US patent office under US7613738 on November 3, 2009.

Directory file set

exFAT and the rest of the FAT family of file systems does not use indexes for file names, unlike NTFS which uses B-trees for file searching. When a file is accessed, the directory must be sequentially searched until a match is found. For file names shorter than 16 characters in length, one file name record is required but the entire file is represented by three 32-byte directory records. This is called a directory file set, and a 256 MiB sub-directory can hold up to 2,796,202 file sets. (If files have longer names, this number will decrease but this is the maximum based on the minimum three-record file set.) To help improve the sequential searching of the directories (including the root) a hash value of the file name is derived for each file and stored in the directory record. When searching for a file, the file name is first converted to upper case using the upcase table (file names are case insensitive) and then hashed using a proprietary patented algorithm into a 16-bit (2 byte) hash value. Each record in the directory is searched by comparing the hash value. When a match is found, the file names are compared to ensure that the proper file was located in case of hash collisions. This improves performance because only 2 bytes have to be compared for each file. This significantly reduces the CPU cycles because most file names are more than 2 characters (bytes) in size and virtually every comparison is performed on only 2 bytes at a time until the intended file is located.

Metadata and checksums

exFAT introduces metadata integrity through the use of checksums. There are three checksums currently in use. The Volume Boot Record (VBR) is a 12 sector region that contains the boot records, BIOS Parameter Block (BPB), OEM parameters and the checksum sector. (There are two VBR type regions, the main VBR and the backup VBR.) The checksum sector is a checksum of the previous 11 sectors, with the exception of three bytes in the boot sector (Flags and percent used). This provides integrity of the VBR by determining if the VBR was modified. The most common cause could be a boot sector virus, but this would also catch any other corruption to the VBR. A second checksum is used for the upcase table. This is a static table and should never change. Any corruption in the table could prevent files from being located because this table is used to convert the filenames to upper case when searching to locate a file. The third checksum is in the directory file sets. Multiple directory records are used to define a single file and this is called a file set. This file set has metadata including the file name, time stamps, attributes, address of first cluster location of the data, file lengths, and the file name. A checksum is taken over the entire file set and a mismatch would occur if the directory file set was accidentally or maliciously changed. When the file system is mounted, and the integrity check is conducted, these hashes are verified. Mounting also includes comparison of the version of the exFAT file system by the driver to make sure the driver is compatible with the file system it is trying to mount, and to make sure that none of the required directory records are missing (for example, the directory record for the upcase table and Allocation Bitmap are required and the file system can't run if they are missing). If any of these checks fail, the file system should not be mounted, although in certain cases it may mount read-only.

The file system provides extensibility through template based metadata definitions using generic layouts and generic patterns.

src: www.adslzone.net

Portability and adoption

ExFAT is a proprietary file system and Microsoft has not released a specification for it. This lack of documentation hampered the development of free and open-source drivers for exFAT. Accordingly, exFAT support was effectively limited to Microsoft's own products and those of Microsoft's licensees, which in turn inhibited exFAT's adoption as universal exchange format.

Interoperability requires that certain results be achieved in a particular, predefined way (an algorithm). For exFAT, this potentially requires every implementation to perform certain procedures in exactly the same way as Microsoft's implementation. Some of the procedures used by Microsoft's implementation are patented, and these patents are owned by Microsoft. A license to use these algorithms can be purchased from Microsoft, and some companies - including Apple, Google and Samsung - have done so. However, in the open-source ecosystem, there is no financial incentive for open-source vendors to purchase a license for these algorithms.

Regardless of whether open-source or not (including Samsung's leaked kernel driver source that was initially fraudulently rebadged as GPL-licensed), according to Microsoft "a license is required in order to implement exFAT and use it in a product or device." Unlicensed distribution of an exFAT driver would make the distributor liable for financial damages if the driver is found to have violated Microsoft's patents. While the patents may not be enforceable, this can only be determined through a legal process, which is expensive and time consuming. It may also be possible to achieve the intended results without infringing Microsoft's patents.^cf. 

The patents used by exFAT appears on a list of Microsoft's "Android-killer patents" published in June 2014 by the Government of China.

src: i.ytimg.com

Features

The specifications, features, and requirements of the exFAT file system include these:

• File size limit of 16 EiB - 1 byte (otherwise limited by maximum volume size of 128 PiB - 1 byte), raised from 4 GiB - 1 byte in a standard FAT32 file system. Therefore, for the typical user, seamless interoperability between Windows and OS X platforms for files in excess of 4 GiB.
• Scalability to large disk sizes: ca. 128 PiB maximum, 512 TiB recommended maximum, raised from the 32-bit limit (2 TiB for a sector size of 512 bytes) of standard FAT32 partitions.
• Support for up to 2,796,202 files per directory only. Microsoft documents a limit of 65,534 files per sub-directory for their FAT32 implementation, but other operating systems have no special limit for the number of files in a FAT32 directory. FAT32 implementations in other operating systems allow an unlimited number of files up to the number of available clusters (that is, up to 268,304,373 files on volumes without long filenames).
• Maximum number of files on volume ca. 2³² - 11 (4294967296) (up from ca. 2²⁸ - 11 in standard FAT32)
• Free space allocation and delete performance improved due to introduction of a free space bitmap.
• Timestamp granularity of 10 ms for Create and Modified times (down from 2 s of FAT, but not as fine as NTFS's 0.1 ms).
• Timestamp granularity for Last Access time to double seconds (FAT was date only)
• Optional support for UTC timestamps (starting with Vista SP2).
• Optional support for access control lists (not currently supported in Windows Desktop/Server versions).
• Optional support for TexFAT, a transactional file system standard (optionally WinCE activated function, not supported in Windows Desktop/Server versions).
• Boundary alignment offset for the FAT table
• Boundary alignment offset for the data region
• Provision for OEM-definable parameters to customize the file system for specific device characteristics.
• On disk storage of file Valid Data Length (VDL) through the use of two distinct lengths fields which can be used to preallocate a file.
• Cluster size up to 32 MiB.
• Metadata integrity with checksums
• Template based metadata structures
• Removal of the physical "." and ".." directory entries that appear in subdirectories
• exFAT does not support short (8.3 format) filenames
• Windows XP requires update KB955704 to be installed and Windows Vista requires its SP2 be installed.
• Windows Vista is unable to use exFAT drives for ReadyBoost. Windows 7 removes this limitation, enabling ReadyBoost caches larger than 4 GiB.
• The standard exFAT implementation is not journaled and only uses a single file allocation table and free space map. FAT file systems instead used alternating tables, as this allowed recovery of the file system if the media was ejected during a write (which occurs frequently in practice with removable media). The optional TexFAT component adds support for additional backup tables and maps, but may not be supported.

src: s-media-cache-ak0.pinimg.com

Adoption

exFAT is supported in Windows XP and Windows Server 2003 with update KB955704, Windows Embedded CE 6.0, Windows Vista with Service Pack 1, Windows Server 2008, Windows 7, Windows 8, Windows Server 2008 R2 (except Windows Server 2008 Server Core), Windows 10, and Mac OS X starting from 10.6.5.

Companies can integrate exFAT into a specific group of consumer devices, including cameras, camcorders, and digital photo frames for a flat fee. Mobile phones, PCs, and networks have a different volume pricing model.

Microsoft has entered into licensing agreements with BlackBerry, Panasonic, Sanyo, Sony, Canon, Aspen Avionics, Audiovox, Continental, Harman, LG Automotive and BMW.

A FUSE-based implementation named fuse-exfat, or exfat-fuse, with read/write support is available for FreeBSD and multiple Linux distributions. A kernel implementation has also been released, written by Samsung. It was initially released on GitHub unintentionally, and later released officially by Samsung in compliance with the GPL. None of the solutions can become an official part of Linux due to the patent encumbered status of the exFAT file system. An implementation called exFATFileSystem, based on fuse-exfat, is available for AmigaOS 4.1.

Proprietary read/write solutions licensed and derived from the Microsoft exFAT implementation are available for Android, Linux, and other operating systems from Paragon Software Group and Tuxera.

XCFiles (from Datalight) is a proprietary, full-featured implementation, intended to be portable to 32-bit systems. Rtfs (from EBS Embedded Software) is a full-featured implementation for embedded devices.

Two experimental, unofficial solutions are available for DOS. The loadable USBEXFAT driver requires Panasonic's USB stack for DOS and only works with USB storage devices; the open-source EXFAT executable is an exFAT file system reader, and requires the HX DOS extender to work. There are no native exFAT real-mode DOS drivers, which would allow usage of, or booting from exFAT volumes.

Mac OS X Snow Leopard 10.6.5 and later can create, read, write, verify, and repair exFAT file systems.

src: i.ytimg.com

See also

• Design of the FAT file system
• List of file systems
• Memory Stick XC
• Universal Disk Format

src: www.gizko.co

Notes

src: i.ytimg.com

References

src: eastmanreference.com

External links

• File System Functionality Comparison of exFAT, FAT32, NTFS, UDF
• exFAT overview in Windows Embedded CE
• Transaction-Safe FAT File System (TexFAT) overview in Windows Mobile 6.5
• Personal Storage : Opportunities and challenges for pocket-sized storage devices in the Windows world (PowerPoint presentation at WinHEC 2006)
• exFAT File System Licensing
• Reverse Engineering the Microsoft exFAT File System, SANS Institute.
• US Patent Application 2009164440 , "Quick Filename Lookup Using Name Hash"; Microsoft Corp; contains exFAT specification revision 1.00.
• US Patent Application 2009164539 , "Contiguous File Allocation In An Extensible File System"; Microsoft Corp.
• exFAT ships on all SDXC Cards, SD Card Association
• The Extended FAT file system:Differentiating with FAT32 file system, Linux Conference, October 2011.
• Benefits of exFAT over FAT32

Source of the article : Wikipedia