exFAT

exFAT (Extensible File Allocation Table) is a file system introduced by Microsoft in 2006 and optimized for flash memory such as USB flash drives and SD cards.[5] exFAT was proprietary until 28 August 2019, when Microsoft published its specification.[6] Microsoft owns patents on several elements of its design.[2]

exFAT
Developer(s)Microsoft
Full nameExtensible File Allocation Table
IntroducedNovember 2006 (2006-11) 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 contentsTable
File allocationbitmap, linked list
Bad blocksCluster tagging
Limits
Max. volume sizec. 128 PiB, 512 TiB recommended[1]
Max. file sizec. 128 PiB (theoretical 16 EiB–1)[nb 1]
Max. number of filesup to 2,796,202 per directory[2]
Max. filename length255 characters
Allowed characters in filenamesall Unicode characters except U+0000 (NUL) through U+001F (US) / (slash) \ (backslash) : (colon) * (asterisk) ? (question mark) " (quote) < (less than) > (greater than) and | (pipe)
(encoding in UTF-16LE)
Features
Dates recordedCreation, last modified, last access
Date range1980-01-01 to 2107-12-31
Date resolution10 ms
ForksNo
AttributesRead-only, hidden, system, subdirectory, archive
File system permissionsACL (Windows CE 6 only)
Transparent compressionNo
Transparent encryptionNo
Other
Supported operating systems

exFAT can be used where NTFS is not a feasible solution (due to data-structure overhead), but a greater file-size limit than the standard FAT32 file system (i.e. 4 GiB) is required.

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

History

exFAT was introduced in late 2006 as part of Windows CE 6.0, an embedded Windows operating system. Most of the vendors signing on for licences are manufacturers of embedded systems or device manufacturers that produce media formatted 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 easily implemented in firmware.

Features

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

  • File size limit of 16 exbibytes (264−1 bytes, or about 1019 bytes, which is otherwise limited by a maximum volume size of 128 PiB[nb 1], or 257−1 bytes), raised from 4 GiB (232−1 bytes) in a standard FAT32 file system.[1] Therefore, for the typical user, seamless interoperability between Windows and macOS platforms for files in excess of 4 GiB.
  • Scalability to large disk sizes: ca. 128 PiB (257−1 bytes)[7][nb 2] maximum, 512 TiB (249−1 bytes) recommended maximum, raised from the 32-bit limit (2 TiB for a sector size of 512 bytes) of standard FAT32 partitions.[8]
  • Support for up to 2,796,202 files per directory.[2][nb 3] Microsoft documents a limit of 65,534 (216−2) 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 C, to 4,294,967,285 (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 (down from 2 s of FAT, but not as fine as NTFS's 100 ns).[2]
  • Timestamp granularity for Last Access time to double seconds (FAT had date only).
  • Timestamps come with a time zone marker in offset relative to UTC (starting with Vista SP2).[9]
  • Optional support for access control lists (not currently supported in Windows Desktop/Server versions).[10]
  • 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.[11][12]
  • Valid Data Length (VDL): through the use of two distinct lengths fields, one for "allocated space" and the other for "valid data", exFAT can preallocate a file without leaking data that was previously on-disk.
  • Cluster size up to 32 MiB.[13]
  • Metadata integrity with checksums.
  • Template based metadata structures.
  • Removal of the physical . and .. directory entries that appear in subdirectories.
  • exFAT is not limited to the short 8.3 filenames.

Windows XP requires update KB955704 to be installed and Windows Vista requires its SP1 or SP2 be installed.[13][14][15] Windows Vista is unable to use exFAT drives for ReadyBoost. Windows 7 removes this limitation, enabling ReadyBoost caches larger than 4 GiB.[16] Windows 10 only allows formatting exFAT on volumes sized 32 GiB or larger with the default user interface, and FAT32 format is suggested for lower sizes; command-line utilities still accept a full range of file systems and allocation unit sizes.

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.

The exFAT format 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.

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,[17] Windows Server 2008,[18] Windows 7, Windows 8, Windows Server 2008 R2 (except Windows Server 2008 Server Core), Windows 10, Mac OS X starting from 10.6.5, Linux starting from 5.4 and iPadOS.[19][20][21]

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

exFAT is supported in a number of media devices such as modern flat-panel TVs,[22] media centers, and portable media players.[23]

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

Microsoft has entered into licensing agreements with BlackBerry,[24][25] Panasonic, Sanyo, Sony, Canon, Aspen Avionics,[26] Audiovox, Continental, Harman, LG Automotive[27] and BMW.[28]

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

Linux has support for exFAT via FUSE since 2009[4]. In 2013, Samsung Electronics published a Linux driver for exFAT under GPL.[29] On 28 August 2019, Microsoft published the exFAT specification[6] and released the patent to the OIN members.[30] The Linux kernel introduced native exFAT support with the 5.4 release.[31]

Technical specialities
Default exFAT cluster sizes in Windows
Volume
size		 Cluster
size		 Cluster
count
007–256 MiB004 KiB<64 K
256 MiB–32 GiB032 KiB0<1 M
032–512 GiB[upper-alpha 1][upper-alpha 2]128 KiB0<4 M
512 GiB–1 TiB256 KiB
001–2 TiB512 KiB
002–4 TiB001 MiB
004–8 TiB002 MiB
008-16 TiB004 MiB
016–32 TiB008 MiB
032–64 TiB016 MiB
064–512 TiB032 MiB<16 M
Notes:
  1. Windows 8/10 defaults to exFAT on volumes sized ≥32 GiB, and FAT32 on volumes <32 GiB.
  2. Windows XP/Vista/7 defaults to 128 KiB clusters for volumes sized ≥32 GiB.

File name lookup

exFAT employs a filename hash-based lookup phase to speed certain cases, which is described in US Patent 8321439,[32] Quick File Name Lookup Using Name Hash, which document perhaps contains additional details helpful in understanding of the file system, in Appendix A.

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.[33] 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.[34]

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.[35][36]

Flash optimizations

exFAT contains a few features that, according to Microsoft, makes it flash-friendly:

  • Boundary alignment for filesystem structures. The offsets for the FAT and the cluster heap is adjustable at format-time, so that writes to these areas will happen in as few flash blocks as possible.
  • An "OEM Parameters" field can be used to record features such as block size of the underlying storage.[37]
  • The lack of a journal, so that less data is written. (Although FAT32 also lacks a journal.)

However, Microsoft's own implementation on Windows is not truly optimized for flash drives. The OEM parameters are ignored by Windows CE,[37] and it is unknown whether the desktop version performs TRIM at all.

Other implementations

exFAT was a proprietary file system until 2019 when Microsoft released the specification and allowed OIN members to use their patents.[38] This lack of documentation along with the threat of a patent infringement lawsuit, as happened previously when Microsoft sued various companies over the VFAT long file name patent (before it expired), hampered the development of free and open-source drivers for exFAT, and led to a situation where Linux distributions couldn't even tell users how to get an exFAT driver. Accordingly, exFAT official support was effectively limited to Microsoft's own products and those of Microsoft's licensees. This, in turn, inhibited exFAT's adoption as a universal exchange format, as it was safer and easier for vendors to rely on FAT32 than it was to pay Microsoft or risk being sued.

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.[39] A license to use these algorithms can be purchased from Microsoft,[40][39] and some companies – including Apple, Google and Samsung – have done so.[41] However, in the open-source ecosystem, users have typically responded to vendors being unwilling to pay for patent licenses by procuring an implementation for themselves from unofficial sources. For example, this is what happened with LAME when MP3 patents were still valid. (Alternatively, the user may decide that the feature is unimportant to them.)

Regardless of whether open-source or not, Microsoft stated that "a license is required in order to implement exFAT and use it in a product or device."[39] 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.[42][43] 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. [44] In October 2018, Microsoft released 60,000 patents to the Open Invention Network members for Linux systems, but exFAT patents were not initially included at the time. There was, however, discussion within Microsoft of whether Microsoft should allow exFAT in Linux devices,[45][46] which eventually resulted in Microsoft publishing the official specification for open usage[6] and releasing the exFAT patents to the OIN in August 2019.[30]

A FUSE-based implementation named fuse-exfat, or exfat-fuse[4], with read/write support is available for FreeBSD, multiple Linux distributions, and older versions of Mac OS X. It supports TRIM.[47][48][49][50][51] An implementation called exFATFileSystem, based on fuse-exfat, is available for AmigaOS 4.1.[52] A Linux kernel implementation has also been released, written by Samsung Electronics.[53] It was initially released on GitHub unintentionally,[54] and later released officially by Samsung in compliance with the GPLv2 in 2013.[55][56] (This release does not make exFAT royalty-free, as licensing from Samsung does not remove Microsoft's patent rights.)[57][58]

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

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.[62] There are no native exFAT real-mode DOS drivers, which would allow usage of, or booting from, exFAT volumes.

gollark: You can, I believe, do* this in python.
gollark: ApioSort™:- store array- patch the language's comparison operators/functions such that lists will always appear sorted- return array exactly as provided
gollark: Yes. Humanity annihilation time is independent of the size of the array.
gollark: Nihilism sort:- store array- annihilate humanity- there is nobody to care if it is sorted, all is meaningless- done
gollark: You could write the algorithm directly in hardware, but this is still susceptible to problems (less so than RAM or R"O"M).

See also

Notes
  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 would make the maximum addressable file system 512 × 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. 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. "KB955704". January 27, 2009. Description of the exFAT file system driver update package [for Windows XP and Windows Server 2003]
  2. US 8321439 contains Microsoft exFAT specification (revision 1.00)
  3. corbet (2019-11-25). "The 5.4 kernel has been released". LWN.net. Retrieved 2019-12-01.
  4. "exfat -Free exFAT file system implementation". Retrieved October 14, 2015.
  5. Marius Oiaga (December 11, 2009). "Microsoft Licenses Windows 7's exFAT Flash File Format". Softpedia.com.
  6. Microsoft (August 28, 2019). "exFAT Specification". Archived from the original on 2020-07-11.
  7. "File System Functionality Comparison". Microsoft. Retrieved February 26, 2015..
  8. "Limitations of the FAT32 File System in Windows XP". Microsoft. December 1, 2007. Retrieved February 11, 2011.
  9. Nash, Mike (October 24, 2008). "Windows Vista Service Pack 2 Beta". The Windows Blog. Archived from the original on May 9, 2013.
  10. "A Second Shot: Windows Vista SP1". Retrieved November 5, 2013.
  11. "Licensing exFAT". Retrieved March 1, 2017.
  12. "OEM Parameter Definition with exFAT (Windows Embedded CE 6.0)". Retrieved November 25, 2013.
  13. "Description of the exFAT file system driver update package". Microsoft. Retrieved February 26, 2015.
  14. "Information about support for exFAT under Windows Vista". Archived from the original on May 7, 2013.
  15. "Download Windows Vista Service Pack 1 Five Language Standalone (KB936330) from Official Microsoft Download Center". Microsoft. Retrieved February 26, 2015.
  16. "exFAT Versus FAT32 Versus NTFS". February 27, 2008. Retrieved October 2, 2009.
  17. LeBlanc, Brandon (August 28, 2007). "Vista SP1 Whitepaper". Microsoft. Retrieved August 28, 2007.
  18. "Adding Hard Disk Drives". Microsoft TechNet. Retrieved September 15, 2009.
  19. "Mac OS X 10.6.5 Notes: exFAT Support, AirPrint, Flash Player Vulnerability Fixes". Retrieved November 25, 2013.
  20. "fsck_exfat(8) Mac OS X Manual Page". Retrieved November 25, 2013.
  21. Friday, rew O'Hara; June 07; 2019; PT, 12:11 pm. "How to use external storage on iPad and iPhone with iOS 13". AppleInsider. Retrieved 2020-02-26.CS1 maint: numeric names: authors list (link)
  22. "exFAT support on Sony". Retrieved January 6, 2013.
  23. Hamm, Jeff (2009). "Extended FAT File System" (PDF). Paradigm Solutions. Retrieved April 9, 2013.
  24. "Microsoft Licenses exFAT to Research In Motion". Tom's Hardware. September 20, 2012.
  25. "Microsoft Signs Licensing Agreement With Research In Motion" (Press release). Microsoft. 18 September 2012.
  26. "Microsoft Signs Patent Licensing Agreement With Aspen Avionics" (Press release). Microsoft.
  27. "In-vehicle infotainment gets boost from new Microsoft exFAT file system deals". Stories. June 19, 2013.
  28. "Microsoft Signs exFAT Licensing Agreement With BMW" (Press release). Microsoft.
  29. "Conservancy Helps Samsung Resolve GPL Compliance Matter Amicably". Software Freedom Conservancy. Retrieved 2019-03-15.
  30. John Gossman (2019-08-28). "exFAT in the Linux kernel? Yes!". Microsoft. Retrieved 2019-09-02.
  31. Abhishek Prakash (November 25, 2019). "Linux Kernel 5.4 Release Features". itsfoss.com. Retrieved April 1, 2020.
  32. US 8321439, "Quick File Name Lookup Using Name Hash"
  33. US 8606830, "Contiguous File Allocation in an Extensible File System"
  34. US 7613738, "FAT Directory Structure for use in Transaction Safe File System"
  35. 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
  36. US Patent Application 2008168029, "Extensible File System"; States in Abstract and elsewhere that directory records can be custom defined.
  37. "OEM Parameter Definition with exFAT (Windows Embedded CE 6.0)". Microsoft documentation.
  38. Larabel, Michael. "Microsoft Publishes exFAT Specification, Encourages Linux Support". Phoronix. Retrieved 28 August 2019.
  39. "Licensing exFAT", Microsoft IP licensing, Microsoft Legal Resources, 1 March 2017
  40. Protalinski, Emil (December 10, 2009), "Microsoft licenses out exFAT file system", ArsTechnica.
  41. Girard, David (21 June 2013), "Can Microsoft's exFAT file system bridge the gap between OSes?", ArsTechnica.
  42. Corbet, Jonathan (July 24, 2013), The exfiltrated exFAT driver, LWN.
  43. Finley, Klint; McMillan, Robert (July 25, 2013), "Free Software Robin Hood Liberates Leaked Samsung Code", Wired Magazine.
  44. Else, Sylvia (November 19, 2016), exFat patent avoidance, Linux.com kernel development forums.
  45. Vaughan-Nichols, Steven J. "What does Microsoft joining the Open Invention Network mean for you?". ZDNet. Retrieved 2018-12-29.
  46. "Merging exFAT Support For Linux Is Being Talked About - Waiting On Microsoft's Blessing - Phoronix". www.phoronix.com. Retrieved 2019-08-08.
  47. "exFAT fs and Linux". Retrieved September 28, 2009.
  48. "exFAT fs on FUSE". Retrieved May 15, 2010.
  49. "exFAT fs on linux UBUNTU". Retrieved October 11, 2012.
  50. "exFAT in FreeBSD". Retrieved April 8, 2013.
  51. "ExFAT support for Mac OS X 10.5 Leopard and 10.4 Tiger (via Homebrew and Fuse for macOS)". Retrieved July 6, 2018.
  52. "Amigaworld.net". Retrieved February 18, 2015.
  53. "Open Source Release Center". Samsung. Retrieved November 25, 2013.
  54. Corbet, Jonathan (July 24, 2013). "The exfiltrated exFAT driver". LWN.net. Retrieved November 25, 2013.
  55. "Conservancy Helps Samsung Resolve GPL Compliance Matter Amicably". Software Freedom Conservancy. August 16, 2013. Retrieved November 25, 2013.
  56. "GPL'ed sources for the Samsung exfat module as released by Samsung". Retrieved 2017-08-20.
  57. Corbet, Jonathan (August 16, 2013), Samsung releases exFAT filesystem source, LWN.
  58. McMillan, Robert (August 20, 2013), "Busted for Dodging Linux License, Samsung Makes Nice With Free Code", Wired.com.
  59. Clarke, Gavin (August 8, 2012). "Sharp cuts exFAT deal with Microsoft for Android mobes". The Register. Retrieved August 12, 2012.
  60. "XCFiles". Retrieved June 21, 2010.
  61. "Rtfs". Retrieved January 19, 2011.
  62. "exFAT". February 2, 2011.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.