exFAT

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
exFAT
Developer(s) Microsoft
Full name Extended File Allocation Table
Introduced November 2006 with Windows Embedded CE 6.0
Partition identifier MBR/EBR: 0x07 (same as for HPFS/NTFS)
BDP/GPT: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
Structures
Directory contents Table
File allocation bitmap, linked list
Bad blocks Cluster tagging
Limits
Max. volume size ca. 128 PiB, 512 TiB recommended[1]
Max. file size ca. 128 PiB (theoretical 16 EiB–1)[nb 1]
Max. number of files up to 2,796,202 per directory[2]
Max. filename length 255 UTF-16 characters
Allowed characters in filenames Unicode UTF-16 except U+0000 (NUL) through U+001F (US) / (slash) \ (backslash) : (colon) * (asterisk) ? (Question mark) " (quote) < (less than) > (greater than) and | (pipe)
Features
Dates recorded Creation, modified, last access
Date range 1980-01-01 to 2107-12-31
Date resolution 10 ms
Forks No
Attributes Read-only, hidden, system, subdirectory, archive
File system permissions ACL (Windows CE 6 only)
Transparent compression No
Transparent encryption No
Other
Supported operating systems Windows Embedded CE 6.0
Windows XP (including x64) SP2 and later (optional[1])
Windows Server 2003 SP2 (optional[1])
Windows Vista SP1 and later
Windows 7
Windows 8
Windows 10
Windows Server 2008
Windows Server 2008 R2
Linux (via FUSE or non-mainline kernel driver)
Mac OS X 10.6.5 and later
Some Android OS devices like the Sony Xperia Z (running the latest firmware)

exFAT (Extended File Allocation Table) is a Microsoft file system optimized for flash drives.[3] It is proprietary and Microsoft owns patents on several elements of its design.[2]

exFAT can be used where the NTFS file system is not a feasible solution (due to data structure overhead), or where the file size limit of the standard FAT32 file system is unacceptable.

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

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 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 table. A single bit in the directory record indicates that the file is contiguous, telling the exFAT driver to ignore the FAT table. 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,[4] media centers, and portable media players.[5]

Some vendors of flash media, including USB pen drives, compact flash (CF) and solid state drives (SSD) are shipping from the factory some of their high capacity media pre-formatted with the exFAT file system. For example, Sandisk ships their 256 GB CF cards as 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,[6] awarded on November 27, 2013, and US Patent 8321439,[7] 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.[8] 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.[9]

Directory file set

exFAT and the rest of the FAT family of filesystems does not use indexes for filenames, 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 filenames shorter than 16 characters in length, one filename 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 3 record file set.) To help improve the sequential searching of the directories (including the root) a hash value of the filename 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 filenames are compared to ensure that the proper file was located in case of collisions. This improves performance because only 2 bytes have to be compared for each file. This significantly reduces the CPU cycles because most filenames are more than 2 characters (bytes) in size and each comparison is virtually only performed on 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 filesystem is mounted, and the integrity check is conducted, these hashes are verified. Mounting also includes comparison of the version of the exFAT filesystem by the driver to make sure the driver is compatible with the filesystem 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 filesystem can't run if they are missing). If any of these checks fail, the filesystem 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.[10][11]

Restrictive licensing and software patents

Microsoft has not officially released the complete exFAT file system specification and a restrictive license from Microsoft is required in order to make and distribute exFAT implementations. Microsoft also asserts software patents on exFAT which make it difficult to re-implement its functionality in a compatible way without violating a large percentage of them.[12] This renders the implementation, distribution, and use of exFAT as a part of free or open-source operating systems or of commercial software, for which the vendors could not obtain a license from Microsoft, legally difficult, especially in countries that recognize United States software patents. Although exFAT is now widely supported, initially Mac OS X and many consumer devices could only handle FAT12, FAT16, and FAT32. The situation had formerly rendered exFAT, and flash memory formatted with it, impractical as a universal exchange format. Native Linux support for exFAT is still limited.[13][14][15][16][17] As of 2010, a working implementation under FUSE exists, which reached version 1.0 in 2013.[18]

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),[nb 1] raised from 4 GiB − 1 byte in a standard FAT32 file system.[1] 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[19][nb 2] maximum, 512 TiB recommended maximum, raised from the 32-bit limit (2 TiB for a sector size of 512 bytes) of standard FAT32 partitions.[20]
  • Support for up to 2,796,202 files per directory only.[2][nb 3] 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).[nb 4]
  • Maximum number of files on volume ca. 232 − 11 (up from ca. 228 − 11[nb 4] 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 (but not as fine as NTFS's 0.1 ms).[2]
  • Timestamp granularity for Last Access time to double seconds (FAT was date only)
  • Optional support for UTC timestamps (starting with Vista SP2).[21]
  • Optional support for access control lists (not currently supported in Windows Desktop/Server versions).[22]
  • 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.[12][23]
  • 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.[24]
  • Metadata integrity with checksums[clarification needed]
  • Template based metadata structures[clarification needed]
  • 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.[24][25][26]
  • Windows Vista is unable to use exFAT drives for ReadyBoost. Windows 7 removes this limitation, enabling ReadyBoost caches larger than 4 GiB.[27]
  • 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.

Adoption

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

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.[3]

Microsoft has entered into licensing agreements with BlackBerry,[32][33] Panasonic, Sanyo, Sony, Canon, Aspen Avionics,[34] Audiovox, Continental, Harman, LG Automotive[35] and BMW.[36]

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

Proprietary read/write solutions licensed and derived from the Microsoft exFAT implementation are available for Android,[45] 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.[46] Rtfs (from EBS Embedded Software) is a full-featured implementation for embedded devices.[47]

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 filesystem reader, and requires the HX DOS extender to work.[48] 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.[30][31]

See also

Notes

  1. ↑ 1.0 1.1 Although Microsoft published a different value in KB955704, the file size is in bytes and is stored as a 64-bit number. The largest theoretical file size would be 16 EiB−1 byte, the same as in NTFS. However, since the true theoretical maximum volume size under the current specification cannot exceed 128 PiB, a file can never reach that file length. Another reason for the limit is that current IDE/ATA disk addressing is LBA-48, and uses a 48 bit block address to address a sector. A 512 byte sector size is represented by 29, which makes the maximum addressable file system 29 × 248 = 257, which is 128 PiB. In other words, the 128 PiB limit on the architecture is a hardware restriction. This scenario does not include AF (4k sectors) and exFAT is limited to 128 PiB regardless of sector size based on the specification.
  2. ↑ The theoretical maximum volume size is defined by up to 232 − 11 possible clusters with up to 225 − 1 bytes per cluster = ca. 128 PiB. The size is currently also limited by the LBA48 addressing scheme, as with a 512 byte sector size, only 248 × 512 = 257 bytes = 128 PiB can be addressed.
  3. ↑ This limit applies because the maximum directory size is 256 MiB.
  4. ↑ 4.0 4.1 268,304,373 files = 228 − 11 reserved clusters - 131,072, the minimum number of 64 kiB clusters occupied for the 268,435,445 directory entries (á 32 bytes) without VFAT LFNs, which are required for 268,435,445 files with sizes between 1 and 65,535 bytes. With VFATs, the 131,072 number must be multiplied by 21 (worst case), which would result in 265,682,933 files instead.

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.2 2.3 US 8321439  contains Microsoft exFAT specification (revision 1.00)
  3. ↑ 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ US Patent Application 2008168029 , "Extensible File System";
  7. ↑ US 8321439 , "Quick File Name Lookup Using Name Hash'"
  8. ↑ US 8606830 , "Contiguous File Allocation in an Extensible File System'"
  9. ↑ US 7613738 , "FAT Directory Structure for use in Transaction Safe File System'"
  10. ↑ US Patent Application 2009164440 , "Quick Filename Lookup Using Name Hash"; Microsoft Corp; contains exFAT specification revision 1.00. See Tables 8, 12, 13, 14, 15, 16, & 17
  11. ↑ US Patent Application 2008168029 , "Extensible File System"; States in Abstract and elsewhere that directory records can be custom defined.
  12. ↑ 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Information about support for exFAT under Windows Vista.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.[unreliable source?]
  31. ↑ 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.[unreliable source?]
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

he:ExFAT

Retrieved from "https://infogalactic.com/w/index.php?title=ExFAT&oldid=2078741"