^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) .. SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) ================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) The Linux NTFS filesystem driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) ================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) .. Table of contents
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) - Overview
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) - Web site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) - Features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) - Supported mount options
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) - Known bugs and (mis-)features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) - Using NTFS volume and stripe sets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) - The Device-Mapper driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) - The Software RAID / MD driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) - Limitations when using the MD driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) Overview
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) Linux-NTFS comes with a number of user-space programs known as ntfsprogs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) These include mkntfs, a full-featured ntfs filesystem format utility,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) ntfsundelete used for recovering files that were unintentionally deleted
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) from an NTFS volume and ntfsresize which is used to resize an NTFS partition.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) See the web site for more information.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) To mount an NTFS 1.2/3.x (Windows NT4/2000/XP/2003) volume, use the file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) system type 'ntfs'. The driver currently supports read-only mode (with no
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) fault-tolerance, encryption or journalling) and very limited, but safe, write
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) support.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) For fault tolerance and raid support (i.e. volume and stripe sets), you can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) use the kernel's Software RAID / MD driver. See section "Using Software RAID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) with NTFS" for details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) Web site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) There is plenty of additional information on the linux-ntfs web site
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) at http://www.linux-ntfs.org/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) The web site has a lot of additional information, such as a comprehensive
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) FAQ, documentation on the NTFS on-disk format, information on the Linux-NTFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) userspace utilities, etc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) Features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) - This is a complete rewrite of the NTFS driver that used to be in the 2.4 and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) earlier kernels. This new driver implements NTFS read support and is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) functionally equivalent to the old ntfs driver and it also implements limited
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) write support. The biggest limitation at present is that files/directories
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) cannot be created or deleted. See below for the list of write features that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) are so far supported. Another limitation is that writing to compressed files
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) is not implemented at all. Also, neither read nor write access to encrypted
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) files is so far implemented.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) - The new driver has full support for sparse files on NTFS 3.x volumes which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) the old driver isn't happy with.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) - The new driver supports execution of binaries due to mmap() now being
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) supported.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) - The new driver supports loopback mounting of files on NTFS which is used by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) some Linux distributions to enable the user to run Linux from an NTFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) partition by creating a large file while in Windows and then loopback
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) mounting the file while in Linux and creating a Linux filesystem on it that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) is used to install Linux on it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) - A comparison of the two drivers using::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) time find . -type f -exec md5sum "{}" \;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) run three times in sequence with each driver (after a reboot) on a 1.4GiB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) NTFS partition, showed the new driver to be 20% faster in total time elapsed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) (from 9:43 minutes on average down to 7:53). The time spent in user space
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) was unchanged but the time spent in the kernel was decreased by a factor of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) 2.5 (from 85 CPU seconds down to 33).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) - The driver does not support short file names in general. For backwards
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) compatibility, we implement access to files using their short file names if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) they exist. The driver will not create short file names however, and a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) rename will discard any existing short file name.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) - The new driver supports exporting of mounted NTFS volumes via NFS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) - The new driver supports async io (aio).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) - The new driver supports fsync(2), fdatasync(2), and msync(2).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) - The new driver supports readv(2) and writev(2).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) - The new driver supports access time updates (including mtime and ctime).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) - The new driver supports truncate(2) and open(2) with O_TRUNC. But at present
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) only very limited support for highly fragmented files, i.e. ones which have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) their data attribute split across multiple extents, is included. Another
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) limitation is that at present truncate(2) will never create sparse files,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) since to mark a file sparse we need to modify the directory entry for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) file and we do not implement directory modifications yet.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) - The new driver supports write(2) which can both overwrite existing data and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) extend the file size so that you can write beyond the existing data. Also,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) writing into sparse regions is supported and the holes are filled in with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) clusters. But at present only limited support for highly fragmented files,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) i.e. ones which have their data attribute split across multiple extents, is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) included. Another limitation is that write(2) will never create sparse
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) files, since to mark a file sparse we need to modify the directory entry for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) the file and we do not implement directory modifications yet.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) Supported mount options
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) =======================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) In addition to the generic mount options described by the manual page for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) mount command (man 8 mount, also see man 5 fstab), the NTFS driver supports the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) following mount options:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) ======================= =======================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) iocharset=name Deprecated option. Still supported but please use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) nls=name in the future. See description for nls=name.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) nls=name Character set to use when returning file names.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) Unlike VFAT, NTFS suppresses names that contain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) unconvertible characters. Note that most character
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) sets contain insufficient characters to represent all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) possible Unicode characters that can exist on NTFS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) To be sure you are not missing any files, you are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) advised to use nls=utf8 which is capable of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) representing all Unicode characters.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) utf8=<bool> Option no longer supported. Currently mapped to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) nls=utf8 but please use nls=utf8 in the future and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) make sure utf8 is compiled either as module or into
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) the kernel. See description for nls=name.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) uid=
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) gid=
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) umask= Provide default owner, group, and access mode mask.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) These options work as documented in mount(8). By
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) default, the files/directories are owned by root and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) he/she has read and write permissions, as well as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) browse permission for directories. No one else has any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) access permissions. I.e. the mode on all files is by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) default rw------- and for directories rwx------, a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) consequence of the default fmask=0177 and dmask=0077.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) Using a umask of zero will grant all permissions to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) everyone, i.e. all files and directories will have mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) rwxrwxrwx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) fmask=
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) dmask= Instead of specifying umask which applies both to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) files and directories, fmask applies only to files and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) dmask only to directories.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) sloppy=<BOOL> If sloppy is specified, ignore unknown mount options.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) Otherwise the default behaviour is to abort mount if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) any unknown options are found.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) show_sys_files=<BOOL> If show_sys_files is specified, show the system files
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) in directory listings. Otherwise the default behaviour
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) is to hide the system files.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) Note that even when show_sys_files is specified, "$MFT"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) will not be visible due to bugs/mis-features in glibc.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) Further, note that irrespective of show_sys_files, all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) files are accessible by name, i.e. you can always do
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) "ls -l \$UpCase" for example to specifically show the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) system file containing the Unicode upcase table.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) case_sensitive=<BOOL> If case_sensitive is specified, treat all file names as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) case sensitive and create file names in the POSIX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) namespace. Otherwise the default behaviour is to treat
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) file names as case insensitive and to create file names
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) in the WIN32/LONG name space. Note, the Linux NTFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) driver will never create short file names and will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) remove them on rename/delete of the corresponding long
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) file name.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) Note that files remain accessible via their short file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) name, if it exists. If case_sensitive, you will need
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) to provide the correct case of the short file name.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) disable_sparse=<BOOL> If disable_sparse is specified, creation of sparse
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) regions, i.e. holes, inside files is disabled for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) volume (for the duration of this mount only). By
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) default, creation of sparse regions is enabled, which
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) is consistent with the behaviour of traditional Unix
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) filesystems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) errors=opt What to do when critical filesystem errors are found.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) Following values can be used for "opt":
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) ======== =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) continue DEFAULT, try to clean-up as much as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) possible, e.g. marking a corrupt inode as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) bad so it is no longer accessed, and then
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) continue.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) recover At present only supported is recovery of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) the boot sector from the backup copy.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) If read-only mount, the recovery is done
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) in memory only and not written to disk.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) ======== =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) Note that the options are additive, i.e. specifying::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) errors=continue,errors=recover
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) means the driver will attempt to recover and if that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) fails it will clean-up as much as possible and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) continue.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) mft_zone_multiplier= Set the MFT zone multiplier for the volume (this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) setting is not persistent across mounts and can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) changed from mount to mount but cannot be changed on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) remount). Values of 1 to 4 are allowed, 1 being the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) default. The MFT zone multiplier determines how much
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) space is reserved for the MFT on the volume. If all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) other space is used up, then the MFT zone will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) shrunk dynamically, so this has no impact on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) amount of free space. However, it can have an impact
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) on performance by affecting fragmentation of the MFT.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) In general use the default. If you have a lot of small
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) files then use a higher value. The values have the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) following meaning:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) ===== =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) Value MFT zone size (% of volume size)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) ===== =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) 1 12.5%
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) 2 25%
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) 3 37.5%
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) 4 50%
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) ===== =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) Note this option is irrelevant for read-only mounts.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) ======================= =======================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) Known bugs and (mis-)features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) =============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) - The link count on each directory inode entry is set to 1, due to Linux not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) supporting directory hard links. This may well confuse some user space
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) applications, since the directory names will have the same inode numbers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) This also speeds up ntfs_read_inode() immensely. And we haven't found any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) problems with this approach so far. If you find a problem with this, please
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) let us know.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) Please send bug reports/comments/feedback/abuse to the Linux-NTFS development
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) list at sourceforge: linux-ntfs-dev@lists.sourceforge.net
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) Using NTFS volume and stripe sets
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) For support of volume and stripe sets, you can either use the kernel's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) Device-Mapper driver or the kernel's Software RAID / MD driver. The former is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) the recommended one to use for linear raid. But the latter is required for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251) raid level 5. For striping and mirroring, either driver should work fine.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) The Device-Mapper driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) You will need to create a table of the components of the volume/stripe set and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) how they fit together and load this into the kernel using the dmsetup utility
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) (see man 8 dmsetup).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) Linear volume sets, i.e. linear raid, has been tested and works fine. Even
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) though untested, there is no reason why stripe sets, i.e. raid level 0, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) mirrors, i.e. raid level 1 should not work, too. Stripes with parity, i.e.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) raid level 5, unfortunately cannot work yet because the current version of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) Device-Mapper driver does not support raid level 5. You may be able to use the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) Software RAID / MD driver for raid level 5, see the next section for details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) To create the table describing your volume you will need to know each of its
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269) components and their sizes in sectors, i.e. multiples of 512-byte blocks.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) For NT4 fault tolerant volumes you can obtain the sizes using fdisk. So for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) example if one of your partitions is /dev/hda2 you would do::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) $ fdisk -ul /dev/hda
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) Disk /dev/hda: 81.9 GB, 81964302336 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) 255 heads, 63 sectors/track, 9964 cylinders, total 160086528 sectors
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) Units = sectors of 1 * 512 = 512 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) Device Boot Start End Blocks Id System
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) /dev/hda1 * 63 4209029 2104483+ 83 Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) /dev/hda2 4209030 37768814 16779892+ 86 NTFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) /dev/hda3 37768815 46170809 4200997+ 83 Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) And you would know that /dev/hda2 has a size of 37768814 - 4209030 + 1 =
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) 33559785 sectors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) For Win2k and later dynamic disks, you can for example use the ldminfo utility
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289) which is part of the Linux LDM tools (the latest version at the time of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) writing is linux-ldm-0.0.8.tar.bz2). You can download it from:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) http://www.linux-ntfs.org/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) Simply extract the downloaded archive (tar xvjf linux-ldm-0.0.8.tar.bz2), go
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) into it (cd linux-ldm-0.0.8) and change to the test directory (cd test). You
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) will find the precompiled (i386) ldminfo utility there. NOTE: You will not be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) able to compile this yourself easily so use the binary version!
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299) Then you would use ldminfo in dump mode to obtain the necessary information::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) $ ./ldminfo --dump /dev/hda
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303) This would dump the LDM database found on /dev/hda which describes all of your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) dynamic disks and all the volumes on them. At the bottom you will see the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) VOLUME DEFINITIONS section which is all you really need. You may need to look
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306) further above to determine which of the disks in the volume definitions is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307) which device in Linux. Hint: Run ldminfo on each of your dynamic disks and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) look at the Disk Id close to the top of the output for each (the PRIVATE HEADER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309) section). You can then find these Disk Ids in the VBLK DATABASE section in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310) <Disk> components where you will get the LDM Name for the disk that is found in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) the VOLUME DEFINITIONS section.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) Note you will also need to enable the LDM driver in the Linux kernel. If your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) distribution did not enable it, you will need to recompile the kernel with it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) enabled. This will create the LDM partitions on each device at boot time. You
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) would then use those devices (for /dev/hda they would be /dev/hda1, 2, 3, etc)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317) in the Device-Mapper table.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) You can also bypass using the LDM driver by using the main device (e.g.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) /dev/hda) and then using the offsets of the LDM partitions into this device as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) the "Start sector of device" when creating the table. Once again ldminfo would
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) give you the correct information to do this.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) Assuming you know all your devices and their sizes things are easy.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326) For a linear raid the table would look like this (note all values are in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) 512-byte sectors)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) # Offset into Size of this Raid type Device Start sector
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) # volume device of device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) 0 1028161 linear /dev/hda1 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332) 1028161 3903762 linear /dev/hdb2 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) 4931923 2103211 linear /dev/hdc1 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335) For a striped volume, i.e. raid level 0, you will need to know the chunk size
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) you used when creating the volume. Windows uses 64kiB as the default, so it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) will probably be this unless you changes the defaults when creating the array.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) For a raid level 0 the table would look like this (note all values are in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340) 512-byte sectors)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) # Offset Size Raid Number Chunk 1st Start 2nd Start
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343) # into of the type of size Device in Device in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) # volume volume stripes device device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) 0 2056320 striped 2 128 /dev/hda1 0 /dev/hdb1 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347) If there are more than two devices, just add each of them to the end of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350) Finally, for a mirrored volume, i.e. raid level 1, the table would look like
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) this (note all values are in 512-byte sectors)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353) # Ofs Size Raid Log Number Region Should Number Source Start Target Start
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) # in of the type type of log size sync? of Device in Device in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355) # vol volume params mirrors Device Device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) 0 2056320 mirror core 2 16 nosync 2 /dev/hda1 0 /dev/hdb1 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358) If you are mirroring to multiple devices you can specify further targets at the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) end of the line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) Note the "Should sync?" parameter "nosync" means that the two mirrors are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) already in sync which will be the case on a clean shutdown of Windows. If the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) mirrors are not clean, you can specify the "sync" option instead of "nosync"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364) and the Device-Mapper driver will then copy the entirety of the "Source Device"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365) to the "Target Device" or if you specified multiple target devices to all of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366) them.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) Once you have your table, save it in a file somewhere (e.g. /etc/ntfsvolume1),
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) and hand it over to dmsetup to work with, like so::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) $ dmsetup create myvolume1 /etc/ntfsvolume1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) You can obviously replace "myvolume1" with whatever name you like.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375) If it all worked, you will now have the device /dev/device-mapper/myvolume1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) which you can then just use as an argument to the mount command as usual to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377) mount the ntfs volume. For example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) $ mount -t ntfs -o ro /dev/device-mapper/myvolume1 /mnt/myvol1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) (You need to create the directory /mnt/myvol1 first and of course you can use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) anything you like instead of /mnt/myvol1 as long as it is an existing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383) directory.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385) It is advisable to do the mount read-only to see if the volume has been setup
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386) correctly to avoid the possibility of causing damage to the data on the ntfs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) volume.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) The Software RAID / MD driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) -----------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) An alternative to using the Device-Mapper driver is to use the kernel's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394) Software RAID / MD driver. For which you need to set up your /etc/raidtab
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) appropriately (see man 5 raidtab).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) Linear volume sets, i.e. linear raid, as well as stripe sets, i.e. raid level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) 0, have been tested and work fine (though see section "Limitations when using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) the MD driver with NTFS volumes" especially if you want to use linear raid).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) Even though untested, there is no reason why mirrors, i.e. raid level 1, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) stripes with parity, i.e. raid level 5, should not work, too.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) You have to use the "persistent-superblock 0" option for each raid-disk in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) NTFS volume/stripe you are configuring in /etc/raidtab as the persistent
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) superblock used by the MD driver would damage the NTFS volume.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) Windows by default uses a stripe chunk size of 64k, so you probably want the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408) "chunk-size 64k" option for each raid-disk, too.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410) For example, if you have a stripe set consisting of two partitions /dev/hda5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411) and /dev/hdb1 your /etc/raidtab would look like this::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) raiddev /dev/md0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414) raid-level 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) nr-raid-disks 2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416) nr-spare-disks 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) persistent-superblock 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418) chunk-size 64k
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) device /dev/hda5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420) raid-disk 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421) device /dev/hdb1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422) raid-disk 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424) For linear raid, just change the raid-level above to "raid-level linear", for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) mirrors, change it to "raid-level 1", and for stripe sets with parity, change
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) it to "raid-level 5".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) Note for stripe sets with parity you will also need to tell the MD driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429) which parity algorithm to use by specifying the option "parity-algorithm
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430) which", where you need to replace "which" with the name of the algorithm to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431) use (see man 5 raidtab for available algorithms) and you will have to try the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) different available algorithms until you find one that works. Make sure you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433) are working read-only when playing with this as you may damage your data
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) otherwise. If you find which algorithm works please let us know (email the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435) linux-ntfs developers list linux-ntfs-dev@lists.sourceforge.net or drop in on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) IRC in channel #ntfs on the irc.freenode.net network) so we can update this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) documentation.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439) Once the raidtab is setup, run for example raid0run -a to start all devices or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440) raid0run /dev/md0 to start a particular md device, in this case /dev/md0.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442) Then just use the mount command as usual to mount the ntfs volume using for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443) example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445) mount -t ntfs -o ro /dev/md0 /mnt/myntfsvolume
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447) It is advisable to do the mount read-only to see if the md volume has been
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448) setup correctly to avoid the possibility of causing damage to the data on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) ntfs volume.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452) Limitations when using the Software RAID / MD driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453) -----------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) Using the md driver will not work properly if any of your NTFS partitions have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456) an odd number of sectors. This is especially important for linear raid as all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457) data after the first partition with an odd number of sectors will be offset by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458) one or more sectors so if you mount such a partition with write support you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) will cause massive damage to the data on the volume which will only become
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460) apparent when you try to use the volume again under Windows.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) So when using linear raid, make sure that all your partitions have an even
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463) number of sectors BEFORE attempting to use it. You have been warned!
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465) Even better is to simply use the Device-Mapper for linear raid and then you do
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466) not have this problem with odd numbers of sectors.
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags