Documentation/filesystems/ntfs.rst

1 .. SPDX-License-Identifier: GPL-2.0
10    - Overview
11    - Web site
12    - Features
13    - Supported mount options
14    - Known bugs and (mis-)features
15    - Using NTFS volume and stripe sets
16      - The Device-Mapper driver
17      - The Software RAID / MD driver
18      - Limitations when using the MD driver
24 Linux-NTFS comes with a number of user-space programs known as ntfsprogs.
25 These include mkntfs, a full-featured ntfs filesystem format utility,
31 system type 'ntfs'.  The driver currently supports read-only mode (with no
32 fault-tolerance, encryption or journalling) and very limited, but safe, write
43 There is plenty of additional information on the linux-ntfs web site
44 at http://www.linux-ntfs.org/
47 FAQ, documentation on the NTFS on-disk format, information on the Linux-NTFS
54 - This is a complete rewrite of the NTFS driver that used to be in the 2.4 and
62 - The new driver has full support for sparse files on NTFS 3.x volumes which
64 - The new driver supports execution of binaries due to mmap() now being
66 - The new driver supports loopback mounting of files on NTFS which is used by
71 - A comparison of the two drivers using::
73 	time find . -type f -exec md5sum "{}" \;
80 - The driver does not support short file names in general.  For backwards
84 - The new driver supports exporting of mounted NTFS volumes via NFS.
85 - The new driver supports async io (aio).
86 - The new driver supports fsync(2), fdatasync(2), and msync(2).
87 - The new driver supports readv(2) and writev(2).
88 - The new driver supports access time updates (including mtime and ctime).
89 - The new driver supports truncate(2) and open(2) with O_TRUNC.  But at present
95 - The new driver supports write(2) which can both overwrite existing data and
137 			default rw------- and for directories rwx------, a
156 			will not be visible due to bugs/mis-features in glibc.
159 			"ls -l \$UpCase" for example to specifically show the
185 			  continue  DEFAULT, try to clean-up as much as
191 				    If read-only mount, the recovery is done
200 			fails it will clean-up as much as possible and
226 			Note this option is irrelevant for read-only mounts.
230 Known bugs and (mis-)features
233 - The link count on each directory inode entry is set to 1, due to Linux not
241 Please send bug reports/comments/feedback/abuse to the Linux-NTFS development
242 list at sourceforge: linux-ntfs-dev@lists.sourceforge.net
249 Device-Mapper driver or the kernel's Software RAID / MD driver.  The former is
254 The Device-Mapper driver
255 ------------------------
263 mirrors, i.e. raid level 1 should not work, too.  Stripes with parity, i.e.
265 Device-Mapper driver does not support raid level 5.  You may be able to use the
269 components and their sizes in sectors, i.e. multiples of 512-byte blocks.
274     $ fdisk -ul /dev/hda
285 And you would know that /dev/hda2 has a size of 37768814 - 4209030 + 1 =
290 writing is linux-ldm-0.0.8.tar.bz2).  You can download it from:
292 	http://www.linux-ntfs.org/
294 Simply extract the downloaded archive (tar xvjf linux-ldm-0.0.8.tar.bz2), go
295 into it (cd linux-ldm-0.0.8) and change to the test directory (cd test).  You
301     $ ./ldminfo --dump /dev/hda
317 in the Device-Mapper table.
327 512-byte sectors)::
340 512-byte sectors)::
351 this (note all values are in 512-byte sectors)::
364 and the Device-Mapper driver will then copy the entirety of the "Source Device"
375 If it all worked, you will now have the device /dev/device-mapper/myvolume1
379     $ mount -t ntfs -o ro /dev/device-mapper/myvolume1 /mnt/myvol1
385 It is advisable to do the mount read-only to see if the volume has been setup
391 -----------------------------
393 An alternative to using the Device-Mapper driver is to use the kernel's
401 stripes with parity, i.e. raid level 5, should not work, too.
403 You have to use the "persistent-superblock 0" option for each raid-disk in the
408 "chunk-size 64k" option for each raid-disk, too.
414 	    raid-level	0
415 	    nr-raid-disks	2
416 	    nr-spare-disks	0
417 	    persistent-superblock	0
418 	    chunk-size	64k
420 	    raid-disk	0
422 	    raid-disk	1
424 For linear raid, just change the raid-level above to "raid-level linear", for
425 mirrors, change it to "raid-level 1", and for stripe sets with parity, change
426 it to "raid-level 5".
428 Note for stripe sets with parity you will also need to tell the MD driver
429 which parity algorithm to use by specifying the option "parity-algorithm
433 are working read-only when playing with this as you may damage your data
435 linux-ntfs developers list linux-ntfs-dev@lists.sourceforge.net or drop in on
439 Once the raidtab is setup, run for example raid0run -a to start all devices or
445     mount -t ntfs -o ro /dev/md0 /mnt/myntfsvolume
447 It is advisable to do the mount read-only to see if the md volume has been
453 -----------------------------------------------------
456 an odd number of sectors.  This is especially important for linear raid as all
457 data after the first partition with an odd number of sectors will be offset by
465 Even better is to simply use the Device-Mapper for linear raid and then you do
466 not have this problem with odd numbers of sectors.