NTFS-3G is an open source implementation of Microsoft NTFS that includes read and write support (the Linux kernel only supports reading NTFS). NTFS-3G developers use the FUSE file system to facilitate development and to help with portability.
- 1 Installation
- 2 Manual mounting
- 3 Formatting
- 4 Configuring
- 5 Resizing NTFS partition
- 6 Troubleshooting
- 7 Beta features and releases
- 8 See also
Install the package.
Two options exist when manually mounting NTFS partitions. The traditional:
# mount /dev/your_NTFS_partition /mount/point
The mount type
ntfs-3g does not need to be explicitly specified in Arch. The mount command by default will use
/usr/bin/mount.ntfs which is symlinked to
/usr/bin/ntfs-3g after the ntfs-3g package is installed.
The second option is to call
# ntfs-3g /dev/your_NTFS_partition /mount/point
Seefor the available options.
# mkfs.ntfs -Q -L diskLabel /dev/sdXY
-Qspeeds up the formatting by not zeroing the drive and not checking for bad sectors.
Your NTFS partition(s) can be setup to mount automatically, or pre-configured to be able to mount in a certain way when you would like them to be mounted. This configuration can be done in the static filesystem configuration (fstab) or by the use of udev rules.
Using the default settings will mount the NTFS partition(s) at boot. With this method, if the parent folder that it is mounted upon has the proper user or group permissions (e.g. /run/media/<username>/), then that user or group will be able to read and write on that partition(s).
# <file system> <dir> <type> <options> <dump> <pass> /dev/NTFS-part /mnt/windows ntfs-3g defaults 0 0
Linux compatible permissions
Permissions on a Linux system are normally set to 755 for folders and 644 for files. It is recommended to keep these permissions in use for the NTFS partition as well if you use the partition on a regular basis. The following example assigns the above permissions to a normal user:
# Mount internal Windows partition with linux compatible permissions, i.e. 755 for directories (dmask=022) and 644 for files (fmask=133) /dev/NTFS-partition /mnt/windows ntfs-3g uid=userid,gid=groupid,dmask=022,fmask=133 0 0
Alternatively, if the Windows permissions do matter to you, you can use thecommand to map Windows users to Linux ones. ntfs-3g will handle the translation of these permissions.
/etc/fstab you can also specify other options like those who are allowed to access (read) the partition. For example, for you to allow people in the
groupid group to have access:
/dev/NTFS-partition /mnt/windows ntfs-3g gid=groupid,umask=0022 0 0
By default, the above line will enable write support for root only. To enable user writing, you have to specify the user who should be granted write permissions. Use the
uid parameter together with your user id to enable user writing:
/dev/NTFS-partition /mnt/windows ntfs-3g uid=userid,gid=groupid,umask=0022 0 0
If you are running on a single user machine, you may like to own the file system yourself and grant all possible permissions:
/dev/NTFS-partition /mnt/windows ntfs-3g uid=userid,gid=groupid 0 0
Basic NTFS-3G options
For most, the above settings should suffice. Here are a few other options that are general common options for various Linux filesystems. For a complete list, see.
- umask is a built-in shell command which automatically sets file permissions on newly created files. For Arch Linux, the default umask for root and user is 0022. With 0022 new folders have the directory permissions of 755 and new files have permissions of 644. You can read more about umask permissions here.
- fmask and dmask
umaskbut defining file and directory respectively individually.
noautois set, NTFS entries in
/etc/fstabdo not get mounted automatically at boot.
- The user id. This allows a specific user to have full access to the partition. Your uid can be found with the
- This FUSE option enables the use of a 128 KiB write buffer as opposed to the libfuse2 default of 4 KiB. It will reduce the CPU utilization of the ntfs-3g process and generally increase write performance. One should always include it because it is safe.
The following option is specific to ntfs-3g only:
- prevents files, directories and extended attributes to be created with a name not allowed by windows.
Allowing user to mount
By default, ntfs-3g requires root rights to mount the filesystem if it is a block device, even with the
user option in
/etc/fstab. See ntfs-3g-faq for details. The
user option in the fstab is still required.
- The ABS, or install AUR.
package does not have internal FUSE support. Rebuild the package using
- The full explanation is that "user" and "users" work via a setuid
mountnot dropping its setuid privillage so that the block device can be used without root. However, ntfs-3g has a hard-coded restriction in ntfs-3g that bails on setuid if an external libfuse is used.
- There is no good technical reason for not allowing setuid for external FUSE besides a mistrust of the library. This patch removes the said restriction.
- The full explanation is that "user" and "users" work via a setuid
- There seems to be an issue with unmounting rights, so you will still need root rights if you need to unmount the filesystem. You can also use
fusermount -u /mnt/mountpointto unmount the filesystem without root rights. Also, if you use the
usersoption (plural) in
/etc/fstabinstead of the
useroption, you will be able to both mount and unmount the filesystem using the
For non-blockfiles like normal images, ntfs-3g on the command-line should work out-of-the-box with normal user privillages as the underlying FUSE calls are redirected to the setuid-root fusermount when direct kernel interaction is unavailable. If it does not work for you, run
ls -l /usr/bin/fusermount; if the first field is not
-rwsr-xr-x, it means the setuid bit is gone and has to be reset by
chmod u+s /usr/bin/fusermount.
Resizing NTFS partition
Most systems that are purchased already have Windows installed on it, and some people would prefer not wipe it off completely when doing an Arch Linux installation. For this reason, among others, it is useful to resize the existing Windows partition to make room for a Linux partition or two. This is often accomplished with a Live CD or bootable USB thumb drive.
For Live CDs the typical procedure is to download an ISO file, burn it to a CD, and then boot from it. InfraRecorder is a free (as in GPL3) CD/DVD burning application for Windows which fits the bill nicely. If you would rather use a bootable USB media instead, see USB flash installation media for methods to create bootable USB stick.
There are a number of bootable CD/USB images avaliable. This list is not exhaustive, but is a good place to start:
- GParted — Small bootable GNU/Linux distribution for x86 based computers. It enables you to use all the features of the latest versions of the GParted application. Does not include additional packages System Rescue CD may incorporate, and disk encryption schemes may not be supported.
- Parted Magic — Very good complete hard disk management solution. With the Partition Editor you can re-size, copy, and move partitions. You can grow or shrink your C: drive. Create space for new operating systems. Attempt data rescue from lost partitions.
- SystemRescueCD — Good tool to have, and works seamlessly in most cases. Once booted, run GParted and the rest should be fairly obvious.
- http://www.sysresccd.org/ || AUR
Note that the important programs for resizing NTFS partitions include ntfs-3g and a utility like (G)parted or fdisk, provided by thepackage. Unless you are an "advanced" user it is advisable to use a tool like GParted to perform any resize operations to minimize the chance of data loss due to user error.
If you already have Arch Linux installed on your system and simply want to resize an existing NTFS partition, you can use the parted and ntfs-3g packages to do it. Optionally, you can use the GParted GUI after installing the GParted package. At the core of the resizing is the command.
When mounting an NTFS filesystem for Windows 10, and reading files or directories, you may
- see broken symbolic links to 'unsupported reparse point', or
- see the error message "cannot access <filename>: Input/output error" (in this case you see in /var/log/messages "Could not load plugin /usr/lib64/ntfs-3g/ntfs-plugin-80000017.so: Success").
The reason for this are NTFS reparse points, and that NTFS-3G does not support some types of reparse points by default. NTFS-3G plugins may be used to provide compatibility with a part of the features defined by the following reparse points
- System compression
- Deduplicated files
- OneDrive files
See this page for further details.
System compression a.k.a. "Compact OS" compresses certain files. There are two possible workarounds for System compression.
You may install the NTFS-3G pluginAUR. Currently only reading is supported by this plugin, but not writing, i.e. creating or updating files is not supported.
Alternatively, disable the System compression feature in Windows 10
C:\WINDOWS\system32> compact.exe /CompactOS:never
Damaged NTFS filesystems
If an NTFS filesystem has errors on it, NTFS-3G will mount it as read-only. To fix an NTFS filesystem, load Windows and run its disk checking program, chkdsk. Take in account that ntfsfix can only repair some errors. If it fails, chkdsk will probably succeed.
To fix the NTFS file system, the device must already be unmounted. For example, to fix an NTFS partition residing in
# umount /dev/sda2 # ntfsfix /dev/sda2 Mounting volume... OK Processing of $MFT and $MFTMirr completed successfully. NTFS volume version is 3.1. NTFS partition /dev/sda2 was processed successfully. # mount /dev/sda2
If all went well, the volume will now be writable.
Metadata kept in Windows cache, refused to mount
When dual booting with Windows 8 or 10, trying to mount a partition that is visible to Windows may yield the following error:
The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdc1': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.
The problem is due to a feature introduced in Windows 8 called "fast startup". When fast startup is enabled, part of the metadata of all mounted partitions are restored to the state they were at the previous closing down. As a consequence, changes made on Linux may be lost. This can happen to any NTFS partition when selecting "Shut down" or "Hibernate" under Windows 8 or 10. Leaving Windows by selecting "Restart", however, is apparently safe.
To enable writing to the partitions on other operating systems, be sure fast startup is disabled. This can be achieved by issuing as an administrator the command:
powercfg /h off
You can check the current settings on Control Panel > Hardware and Sound > Power Options > System Setting > Choose what the power buttons do. The box Turn on fast startup should either be disabled or missing.
Deleting Windows hibernate metadata
As an alternative to above clean shutdown method, there is a way to completely destroy NTFS metadata that was saved after hibernating. This method is only feasible if you are not able or unwilling to boot into Windows and shut it down completely. This is by placing remove_hiberfile option when you are mounting your NTFS file system using ntfs-3g.
# mount -t ntfs-3g -o remove_hiberfile /dev/your_NTFS_partition /mount/point
Windows mount failure
Windows will not recognize a NTFS partition that does not have a corresponding partition type. A common pitfall when creating an NTFS partition to work with Windows is forgetting to set the partition type as NTFS. See fdisk or one of the partitioning tools.
Beta features and releases
There is a web page on "advanced features", maintained by Jean-Pierre André, one of the NTFS-3G authors. It provides:
- Documentation on handling of NTFS features in NTFS-3G, including:
- Symlinks, junctions, and other reparse points
- Extended attributes (xattrs) as an interface for ADS streams and special NTFS attributes
- Security and permission, including POSIX mapping and ACL mapping
- Advanced releases containing features not yet cleared for release by Tuxera, but table enough to pass the full test suite. Available as AUR.
- Plugins for parsing special reparse points.
Information provided in the documentation apply to the Tuxera version (2017.3.23) too. The system-compression and dedupe plugins work with the Tuxera version, but the onedrive plugin requires a tweak of the plugin-loading system only available in advanced releases.