6:36
 | |
| Developer(s) | Tuxera Inc. |
|---|---|
| Stable release | 2017.3.23
/ March 23, 2017[1] |
| Preview release | 2017.3.23AR.6
/ February 1, 2021[2] |
| Repository |  |
| Written in | C |
| Operating system | Unix-like, Haiku |
| Type | File system driver |
| License | Dual-licensed GNU GPL[3] |
| Website | www |
NTFS-3G is an open-source cross-platform implementation of the Microsoft Windows NTFS file system with read/write support. NTFS-3G often uses the FUSE file system interface, so it can run unmodified on many different operating systems. It is runnable on Linux, FreeBSD, NetBSD, OpenSolaris, illumos, BeOS, QNX, WinCE, Nucleus, VxWorks, Haiku,[1]MorphOS, Minix, macOS[4] and OpenBSD.[5][6] It is licensed under the GNU General Public License. It is a partial fork of ntfsprogs and is under active maintenance and development.
NTFS-3G was introduced by one of the senior Linux NTFS developers, Szabolcs Szakacsits, in July 2006. The first stable version was released on February 21, 2007, as version 1.0. The developers of NTFS-3G later formed a company, Tuxera Inc., to further develop the code. NTFS-3G is now the free "community edition",[1][failed verification] while Tuxera NTFS is the proprietary version.
NTFS-3G supports all operations for writing files: files of any size can be created, modified, renamed, moved, or deleted on NTFS partitions. Transparent compression is supported, as well as system-level encryption.[7] Support to modify access control lists and permissions is available.[8] NTFS partitions are mounted using the Filesystem in Userspace (FUSE) interface. NTFS-3G supports hard links, symbolic links, and junctions. With the help of NTFS reparse point plugins, it can be made to read chunk-deduplicated files, system-compressed files, and OneDrive files.[9] NTFS-3G provides complete support and translation of NTFS access control list (ACL) to POSIX ACL permissions. A "usermap" utility is included to record the mapping from UIDs to Windows NT SIDs.
NTFS-3G supports partial NTFS journaling, so if an unexpected computer failure leaves the file system in an inconsistent state, the volume can be repaired. As of 2009, a volume having an unclean journal file is recovered and mounted by default. The ‘norecover’ mount option can be used to disable this behavior.[10]
Benchmarks show that the driver's performance via FUSE is comparable to that of other filesystems' drivers in-kernel,[11] provided that the CPU is powerful enough. On embedded or old systems, the high processor usage can severely limit performance. Tuxera sells optimized versions of the driver that claims to have improved CPU utilization for embedded systems and MacOS.[12]
The slowness of NTFS-3G (and FUSE in general) on embedded systems is attributed to the frequent context switching associated with FUSE calls. Some open-source methods provided to reduce this overhead include:[13]
big_writes to use larger blocks when writing. Using a larger block means fewer context switches. This is in fact a solution recommended by Tuxera.[14] A patch is available to use an even larger block.[15]lazytime to reduce the writes on file access.CACHE_NIDATA_SIZE with a different mechanism with unsure benefit. (It also includes an alternative Security Identifier translation for the NAS.)While Tuxera Ltd. rarely releases updates to the NTFS-3G software, the software's main maintainer Jean-Pierre André has kept the development active on SourceForge, providing bug fixes and new features. He runs a parallel release system on his website as the NTFS-3G Advanced Version (NTFS-3G AR). Each version is run through a test suite and is considered stable.[18][2]
Linux distributions that have switched to NTFS-3G AR include Debian and its derivatives (Ubuntu, PureOS, Pardus, Parrot OS, Trisquel), Gentoo Linux, and LiGurOS.[19]
Workaround: using the mount option “big_writes” generally reduces the CPU usage, provided the software requesting the writes supports big blocks.
By: Wikipedia.org
Edited: 2021-06-18 18:48:37
Source: Wikipedia.org
