ntfs.txt 31 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714
  1. The Linux NTFS filesystem driver
  2. ================================
  3. Table of contents
  4. =================
  5. - Overview
  6. - Web site
  7. - Features
  8. - Supported mount options
  9. - Known bugs and (mis-)features
  10. - Using NTFS volume and stripe sets
  11. - The Device-Mapper driver
  12. - The Software RAID / MD driver
  13. - Limitations when using the MD driver
  14. - ChangeLog
  15. Overview
  16. ========
  17. Linux-NTFS comes with a number of user-space programs known as ntfsprogs.
  18. These include mkntfs, a full-featured ntfs filesystem format utility,
  19. ntfsundelete used for recovering files that were unintentionally deleted
  20. from an NTFS volume and ntfsresize which is used to resize an NTFS partition.
  21. See the web site for more information.
  22. To mount an NTFS 1.2/3.x (Windows NT4/2000/XP/2003) volume, use the file
  23. system type 'ntfs'. The driver currently supports read-only mode (with no
  24. fault-tolerance, encryption or journalling) and very limited, but safe, write
  25. support.
  26. For fault tolerance and raid support (i.e. volume and stripe sets), you can
  27. use the kernel's Software RAID / MD driver. See section "Using Software RAID
  28. with NTFS" for details.
  29. Web site
  30. ========
  31. There is plenty of additional information on the linux-ntfs web site
  32. at http://linux-ntfs.sourceforge.net/
  33. The web site has a lot of additional information, such as a comprehensive
  34. FAQ, documentation on the NTFS on-disk format, information on the Linux-NTFS
  35. userspace utilities, etc.
  36. Features
  37. ========
  38. - This is a complete rewrite of the NTFS driver that used to be in the 2.4 and
  39. earlier kernels. This new driver implements NTFS read support and is
  40. functionally equivalent to the old ntfs driver and it also implements limited
  41. write support. The biggest limitation at present is that files/directories
  42. cannot be created or deleted. See below for the list of write features that
  43. are so far supported. Another limitation is that writing to compressed files
  44. is not implemented at all. Also, neither read nor write access to encrypted
  45. files is so far implemented.
  46. - The new driver has full support for sparse files on NTFS 3.x volumes which
  47. the old driver isn't happy with.
  48. - The new driver supports execution of binaries due to mmap() now being
  49. supported.
  50. - The new driver supports loopback mounting of files on NTFS which is used by
  51. some Linux distributions to enable the user to run Linux from an NTFS
  52. partition by creating a large file while in Windows and then loopback
  53. mounting the file while in Linux and creating a Linux filesystem on it that
  54. is used to install Linux on it.
  55. - A comparison of the two drivers using:
  56. time find . -type f -exec md5sum "{}" \;
  57. run three times in sequence with each driver (after a reboot) on a 1.4GiB
  58. NTFS partition, showed the new driver to be 20% faster in total time elapsed
  59. (from 9:43 minutes on average down to 7:53). The time spent in user space
  60. was unchanged but the time spent in the kernel was decreased by a factor of
  61. 2.5 (from 85 CPU seconds down to 33).
  62. - The driver does not support short file names in general. For backwards
  63. compatibility, we implement access to files using their short file names if
  64. they exist. The driver will not create short file names however, and a
  65. rename will discard any existing short file name.
  66. - The new driver supports exporting of mounted NTFS volumes via NFS.
  67. - The new driver supports async io (aio).
  68. - The new driver supports fsync(2), fdatasync(2), and msync(2).
  69. - The new driver supports readv(2) and writev(2).
  70. - The new driver supports access time updates (including mtime and ctime).
  71. - The new driver supports truncate(2) and open(2) with O_TRUNC. But at present
  72. only very limited support for highly fragmented files, i.e. ones which have
  73. their data attribute split across multiple extents, is included. Another
  74. limitation is that at present truncate(2) will never create sparse files,
  75. since to mark a file sparse we need to modify the directory entry for the
  76. file and we do not implement directory modifications yet.
  77. - The new driver supports write(2) which can both overwrite existing data and
  78. extend the file size so that you can write beyond the existing data. Also,
  79. writing into sparse regions is supported and the holes are filled in with
  80. clusters. But at present only limited support for highly fragmented files,
  81. i.e. ones which have their data attribute split across multiple extents, is
  82. included. Another limitation is that write(2) will never create sparse
  83. files, since to mark a file sparse we need to modify the directory entry for
  84. the file and we do not implement directory modifications yet.
  85. Supported mount options
  86. =======================
  87. In addition to the generic mount options described by the manual page for the
  88. mount command (man 8 mount, also see man 5 fstab), the NTFS driver supports the
  89. following mount options:
  90. iocharset=name Deprecated option. Still supported but please use
  91. nls=name in the future. See description for nls=name.
  92. nls=name Character set to use when returning file names.
  93. Unlike VFAT, NTFS suppresses names that contain
  94. unconvertible characters. Note that most character
  95. sets contain insufficient characters to represent all
  96. possible Unicode characters that can exist on NTFS.
  97. To be sure you are not missing any files, you are
  98. advised to use nls=utf8 which is capable of
  99. representing all Unicode characters.
  100. utf8=<bool> Option no longer supported. Currently mapped to
  101. nls=utf8 but please use nls=utf8 in the future and
  102. make sure utf8 is compiled either as module or into
  103. the kernel. See description for nls=name.
  104. uid=
  105. gid=
  106. umask= Provide default owner, group, and access mode mask.
  107. These options work as documented in mount(8). By
  108. default, the files/directories are owned by root and
  109. he/she has read and write permissions, as well as
  110. browse permission for directories. No one else has any
  111. access permissions. I.e. the mode on all files is by
  112. default rw------- and for directories rwx------, a
  113. consequence of the default fmask=0177 and dmask=0077.
  114. Using a umask of zero will grant all permissions to
  115. everyone, i.e. all files and directories will have mode
  116. rwxrwxrwx.
  117. fmask=
  118. dmask= Instead of specifying umask which applies both to
  119. files and directories, fmask applies only to files and
  120. dmask only to directories.
  121. sloppy=<BOOL> If sloppy is specified, ignore unknown mount options.
  122. Otherwise the default behaviour is to abort mount if
  123. any unknown options are found.
  124. show_sys_files=<BOOL> If show_sys_files is specified, show the system files
  125. in directory listings. Otherwise the default behaviour
  126. is to hide the system files.
  127. Note that even when show_sys_files is specified, "$MFT"
  128. will not be visible due to bugs/mis-features in glibc.
  129. Further, note that irrespective of show_sys_files, all
  130. files are accessible by name, i.e. you can always do
  131. "ls -l \$UpCase" for example to specifically show the
  132. system file containing the Unicode upcase table.
  133. case_sensitive=<BOOL> If case_sensitive is specified, treat all file names as
  134. case sensitive and create file names in the POSIX
  135. namespace. Otherwise the default behaviour is to treat
  136. file names as case insensitive and to create file names
  137. in the WIN32/LONG name space. Note, the Linux NTFS
  138. driver will never create short file names and will
  139. remove them on rename/delete of the corresponding long
  140. file name.
  141. Note that files remain accessible via their short file
  142. name, if it exists. If case_sensitive, you will need
  143. to provide the correct case of the short file name.
  144. disable_sparse=<BOOL> If disable_sparse is specified, creation of sparse
  145. regions, i.e. holes, inside files is disabled for the
  146. volume (for the duration of this mount only). By
  147. default, creation of sparse regions is enabled, which
  148. is consistent with the behaviour of traditional Unix
  149. filesystems.
  150. errors=opt What to do when critical filesystem errors are found.
  151. Following values can be used for "opt":
  152. continue: DEFAULT, try to clean-up as much as
  153. possible, e.g. marking a corrupt inode as
  154. bad so it is no longer accessed, and then
  155. continue.
  156. recover: At present only supported is recovery of
  157. the boot sector from the backup copy.
  158. If read-only mount, the recovery is done
  159. in memory only and not written to disk.
  160. Note that the options are additive, i.e. specifying:
  161. errors=continue,errors=recover
  162. means the driver will attempt to recover and if that
  163. fails it will clean-up as much as possible and
  164. continue.
  165. mft_zone_multiplier= Set the MFT zone multiplier for the volume (this
  166. setting is not persistent across mounts and can be
  167. changed from mount to mount but cannot be changed on
  168. remount). Values of 1 to 4 are allowed, 1 being the
  169. default. The MFT zone multiplier determines how much
  170. space is reserved for the MFT on the volume. If all
  171. other space is used up, then the MFT zone will be
  172. shrunk dynamically, so this has no impact on the
  173. amount of free space. However, it can have an impact
  174. on performance by affecting fragmentation of the MFT.
  175. In general use the default. If you have a lot of small
  176. files then use a higher value. The values have the
  177. following meaning:
  178. Value MFT zone size (% of volume size)
  179. 1 12.5%
  180. 2 25%
  181. 3 37.5%
  182. 4 50%
  183. Note this option is irrelevant for read-only mounts.
  184. Known bugs and (mis-)features
  185. =============================
  186. - The link count on each directory inode entry is set to 1, due to Linux not
  187. supporting directory hard links. This may well confuse some user space
  188. applications, since the directory names will have the same inode numbers.
  189. This also speeds up ntfs_read_inode() immensely. And we haven't found any
  190. problems with this approach so far. If you find a problem with this, please
  191. let us know.
  192. Please send bug reports/comments/feedback/abuse to the Linux-NTFS development
  193. list at sourceforge: linux-ntfs-dev@lists.sourceforge.net
  194. Using NTFS volume and stripe sets
  195. =================================
  196. For support of volume and stripe sets, you can either use the kernel's
  197. Device-Mapper driver or the kernel's Software RAID / MD driver. The former is
  198. the recommended one to use for linear raid. But the latter is required for
  199. raid level 5. For striping and mirroring, either driver should work fine.
  200. The Device-Mapper driver
  201. ------------------------
  202. You will need to create a table of the components of the volume/stripe set and
  203. how they fit together and load this into the kernel using the dmsetup utility
  204. (see man 8 dmsetup).
  205. Linear volume sets, i.e. linear raid, has been tested and works fine. Even
  206. though untested, there is no reason why stripe sets, i.e. raid level 0, and
  207. mirrors, i.e. raid level 1 should not work, too. Stripes with parity, i.e.
  208. raid level 5, unfortunately cannot work yet because the current version of the
  209. Device-Mapper driver does not support raid level 5. You may be able to use the
  210. Software RAID / MD driver for raid level 5, see the next section for details.
  211. To create the table describing your volume you will need to know each of its
  212. components and their sizes in sectors, i.e. multiples of 512-byte blocks.
  213. For NT4 fault tolerant volumes you can obtain the sizes using fdisk. So for
  214. example if one of your partitions is /dev/hda2 you would do:
  215. $ fdisk -ul /dev/hda
  216. Disk /dev/hda: 81.9 GB, 81964302336 bytes
  217. 255 heads, 63 sectors/track, 9964 cylinders, total 160086528 sectors
  218. Units = sectors of 1 * 512 = 512 bytes
  219. Device Boot Start End Blocks Id System
  220. /dev/hda1 * 63 4209029 2104483+ 83 Linux
  221. /dev/hda2 4209030 37768814 16779892+ 86 NTFS
  222. /dev/hda3 37768815 46170809 4200997+ 83 Linux
  223. And you would know that /dev/hda2 has a size of 37768814 - 4209030 + 1 =
  224. 33559785 sectors.
  225. For Win2k and later dynamic disks, you can for example use the ldminfo utility
  226. which is part of the Linux LDM tools (the latest version at the time of
  227. writing is linux-ldm-0.0.8.tar.bz2). You can download it from:
  228. http://linux-ntfs.sourceforge.net/downloads.html
  229. Simply extract the downloaded archive (tar xvjf linux-ldm-0.0.8.tar.bz2), go
  230. into it (cd linux-ldm-0.0.8) and change to the test directory (cd test). You
  231. will find the precompiled (i386) ldminfo utility there. NOTE: You will not be
  232. able to compile this yourself easily so use the binary version!
  233. Then you would use ldminfo in dump mode to obtain the necessary information:
  234. $ ./ldminfo --dump /dev/hda
  235. This would dump the LDM database found on /dev/hda which describes all of your
  236. dynamic disks and all the volumes on them. At the bottom you will see the
  237. VOLUME DEFINITIONS section which is all you really need. You may need to look
  238. further above to determine which of the disks in the volume definitions is
  239. which device in Linux. Hint: Run ldminfo on each of your dynamic disks and
  240. look at the Disk Id close to the top of the output for each (the PRIVATE HEADER
  241. section). You can then find these Disk Ids in the VBLK DATABASE section in the
  242. <Disk> components where you will get the LDM Name for the disk that is found in
  243. the VOLUME DEFINITIONS section.
  244. Note you will also need to enable the LDM driver in the Linux kernel. If your
  245. distribution did not enable it, you will need to recompile the kernel with it
  246. enabled. This will create the LDM partitions on each device at boot time. You
  247. would then use those devices (for /dev/hda they would be /dev/hda1, 2, 3, etc)
  248. in the Device-Mapper table.
  249. You can also bypass using the LDM driver by using the main device (e.g.
  250. /dev/hda) and then using the offsets of the LDM partitions into this device as
  251. the "Start sector of device" when creating the table. Once again ldminfo would
  252. give you the correct information to do this.
  253. Assuming you know all your devices and their sizes things are easy.
  254. For a linear raid the table would look like this (note all values are in
  255. 512-byte sectors):
  256. --- cut here ---
  257. # Offset into Size of this Raid type Device Start sector
  258. # volume device of device
  259. 0 1028161 linear /dev/hda1 0
  260. 1028161 3903762 linear /dev/hdb2 0
  261. 4931923 2103211 linear /dev/hdc1 0
  262. --- cut here ---
  263. For a striped volume, i.e. raid level 0, you will need to know the chunk size
  264. you used when creating the volume. Windows uses 64kiB as the default, so it
  265. will probably be this unless you changes the defaults when creating the array.
  266. For a raid level 0 the table would look like this (note all values are in
  267. 512-byte sectors):
  268. --- cut here ---
  269. # Offset Size Raid Number Chunk 1st Start 2nd Start
  270. # into of the type of size Device in Device in
  271. # volume volume stripes device device
  272. 0 2056320 striped 2 128 /dev/hda1 0 /dev/hdb1 0
  273. --- cut here ---
  274. If there are more than two devices, just add each of them to the end of the
  275. line.
  276. Finally, for a mirrored volume, i.e. raid level 1, the table would look like
  277. this (note all values are in 512-byte sectors):
  278. --- cut here ---
  279. # Ofs Size Raid Log Number Region Should Number Source Start Target Start
  280. # in of the type type of log size sync? of Device in Device in
  281. # vol volume params mirrors Device Device
  282. 0 2056320 mirror core 2 16 nosync 2 /dev/hda1 0 /dev/hdb1 0
  283. --- cut here ---
  284. If you are mirroring to multiple devices you can specify further targets at the
  285. end of the line.
  286. Note the "Should sync?" parameter "nosync" means that the two mirrors are
  287. already in sync which will be the case on a clean shutdown of Windows. If the
  288. mirrors are not clean, you can specify the "sync" option instead of "nosync"
  289. and the Device-Mapper driver will then copy the entirey of the "Source Device"
  290. to the "Target Device" or if you specified multipled target devices to all of
  291. them.
  292. Once you have your table, save it in a file somewhere (e.g. /etc/ntfsvolume1),
  293. and hand it over to dmsetup to work with, like so:
  294. $ dmsetup create myvolume1 /etc/ntfsvolume1
  295. You can obviously replace "myvolume1" with whatever name you like.
  296. If it all worked, you will now have the device /dev/device-mapper/myvolume1
  297. which you can then just use as an argument to the mount command as usual to
  298. mount the ntfs volume. For example:
  299. $ mount -t ntfs -o ro /dev/device-mapper/myvolume1 /mnt/myvol1
  300. (You need to create the directory /mnt/myvol1 first and of course you can use
  301. anything you like instead of /mnt/myvol1 as long as it is an existing
  302. directory.)
  303. It is advisable to do the mount read-only to see if the volume has been setup
  304. correctly to avoid the possibility of causing damage to the data on the ntfs
  305. volume.
  306. The Software RAID / MD driver
  307. -----------------------------
  308. An alternative to using the Device-Mapper driver is to use the kernel's
  309. Software RAID / MD driver. For which you need to set up your /etc/raidtab
  310. appropriately (see man 5 raidtab).
  311. Linear volume sets, i.e. linear raid, as well as stripe sets, i.e. raid level
  312. 0, have been tested and work fine (though see section "Limitations when using
  313. the MD driver with NTFS volumes" especially if you want to use linear raid).
  314. Even though untested, there is no reason why mirrors, i.e. raid level 1, and
  315. stripes with parity, i.e. raid level 5, should not work, too.
  316. You have to use the "persistent-superblock 0" option for each raid-disk in the
  317. NTFS volume/stripe you are configuring in /etc/raidtab as the persistent
  318. superblock used by the MD driver would damage the NTFS volume.
  319. Windows by default uses a stripe chunk size of 64k, so you probably want the
  320. "chunk-size 64k" option for each raid-disk, too.
  321. For example, if you have a stripe set consisting of two partitions /dev/hda5
  322. and /dev/hdb1 your /etc/raidtab would look like this:
  323. raiddev /dev/md0
  324. raid-level 0
  325. nr-raid-disks 2
  326. nr-spare-disks 0
  327. persistent-superblock 0
  328. chunk-size 64k
  329. device /dev/hda5
  330. raid-disk 0
  331. device /dev/hdb1
  332. raid-disl 1
  333. For linear raid, just change the raid-level above to "raid-level linear", for
  334. mirrors, change it to "raid-level 1", and for stripe sets with parity, change
  335. it to "raid-level 5".
  336. Note for stripe sets with parity you will also need to tell the MD driver
  337. which parity algorithm to use by specifying the option "parity-algorithm
  338. which", where you need to replace "which" with the name of the algorithm to
  339. use (see man 5 raidtab for available algorithms) and you will have to try the
  340. different available algorithms until you find one that works. Make sure you
  341. are working read-only when playing with this as you may damage your data
  342. otherwise. If you find which algorithm works please let us know (email the
  343. linux-ntfs developers list linux-ntfs-dev@lists.sourceforge.net or drop in on
  344. IRC in channel #ntfs on the irc.freenode.net network) so we can update this
  345. documentation.
  346. Once the raidtab is setup, run for example raid0run -a to start all devices or
  347. raid0run /dev/md0 to start a particular md device, in this case /dev/md0.
  348. Then just use the mount command as usual to mount the ntfs volume using for
  349. example: mount -t ntfs -o ro /dev/md0 /mnt/myntfsvolume
  350. It is advisable to do the mount read-only to see if the md volume has been
  351. setup correctly to avoid the possibility of causing damage to the data on the
  352. ntfs volume.
  353. Limitations when using the Software RAID / MD driver
  354. -----------------------------------------------------
  355. Using the md driver will not work properly if any of your NTFS partitions have
  356. an odd number of sectors. This is especially important for linear raid as all
  357. data after the first partition with an odd number of sectors will be offset by
  358. one or more sectors so if you mount such a partition with write support you
  359. will cause massive damage to the data on the volume which will only become
  360. apparent when you try to use the volume again under Windows.
  361. So when using linear raid, make sure that all your partitions have an even
  362. number of sectors BEFORE attempting to use it. You have been warned!
  363. Even better is to simply use the Device-Mapper for linear raid and then you do
  364. not have this problem with odd numbers of sectors.
  365. ChangeLog
  366. =========
  367. Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog.
  368. 2.1.28:
  369. - Fix a deadlock.
  370. 2.1.27:
  371. - Implement page migration support so the kernel can move memory used
  372. by NTFS files and directories around for management purposes.
  373. - Add support for writing to sparse files created with Windows XP SP2.
  374. - Many minor improvements and bug fixes.
  375. 2.1.26:
  376. - Implement support for sector sizes above 512 bytes (up to the maximum
  377. supported by NTFS which is 4096 bytes).
  378. - Enhance support for NTFS volumes which were supported by Windows but
  379. not by Linux due to invalid attribute list attribute flags.
  380. - A few minor updates and bug fixes.
  381. 2.1.25:
  382. - Write support is now extended with write(2) being able to both
  383. overwrite existing file data and to extend files. Also, if a write
  384. to a sparse region occurs, write(2) will fill in the hole. Note,
  385. mmap(2) based writes still do not support writing into holes or
  386. writing beyond the initialized size.
  387. - Write support has a new feature and that is that truncate(2) and
  388. open(2) with O_TRUNC are now implemented thus files can be both made
  389. smaller and larger.
  390. - Note: Both write(2) and truncate(2)/open(2) with O_TRUNC still have
  391. limitations in that they
  392. - only provide limited support for highly fragmented files.
  393. - only work on regular, i.e. uncompressed and unencrypted files.
  394. - never create sparse files although this will change once directory
  395. operations are implemented.
  396. - Lots of bug fixes and enhancements across the board.
  397. 2.1.24:
  398. - Support journals ($LogFile) which have been modified by chkdsk. This
  399. means users can boot into Windows after we marked the volume dirty.
  400. The Windows boot will run chkdsk and then reboot. The user can then
  401. immediately boot into Linux rather than having to do a full Windows
  402. boot first before rebooting into Linux and we will recognize such a
  403. journal and empty it as it is clean by definition.
  404. - Support journals ($LogFile) with only one restart page as well as
  405. journals with two different restart pages. We sanity check both and
  406. either use the only sane one or the more recent one of the two in the
  407. case that both are valid.
  408. - Lots of bug fixes and enhancements across the board.
  409. 2.1.23:
  410. - Stamp the user space journal, aka transaction log, aka $UsnJrnl, if
  411. it is present and active thus telling Windows and applications using
  412. the transaction log that changes can have happened on the volume
  413. which are not recorded in $UsnJrnl.
  414. - Detect the case when Windows has been hibernated (suspended to disk)
  415. and if this is the case do not allow (re)mounting read-write to
  416. prevent data corruption when you boot back into the suspended
  417. Windows session.
  418. - Implement extension of resident files using the normal file write
  419. code paths, i.e. most very small files can be extended to be a little
  420. bit bigger but not by much.
  421. - Add new mount option "disable_sparse". (See list of mount options
  422. above for details.)
  423. - Improve handling of ntfs volumes with errors and strange boot sectors
  424. in particular.
  425. - Fix various bugs including a nasty deadlock that appeared in recent
  426. kernels (around 2.6.11-2.6.12 timeframe).
  427. 2.1.22:
  428. - Improve handling of ntfs volumes with errors.
  429. - Fix various bugs and race conditions.
  430. 2.1.21:
  431. - Fix several race conditions and various other bugs.
  432. - Many internal cleanups, code reorganization, optimizations, and mft
  433. and index record writing code rewritten to fit in with the changes.
  434. - Update Documentation/filesystems/ntfs.txt with instructions on how to
  435. use the Device-Mapper driver with NTFS ftdisk/LDM raid.
  436. 2.1.20:
  437. - Fix two stupid bugs introduced in 2.1.18 release.
  438. 2.1.19:
  439. - Minor bugfix in handling of the default upcase table.
  440. - Many internal cleanups and improvements. Many thanks to Linus
  441. Torvalds and Al Viro for the help and advice with the sparse
  442. annotations and cleanups.
  443. 2.1.18:
  444. - Fix scheduling latencies at mount time. (Ingo Molnar)
  445. - Fix endianness bug in a little traversed portion of the attribute
  446. lookup code.
  447. 2.1.17:
  448. - Fix bugs in mount time error code paths.
  449. 2.1.16:
  450. - Implement access time updates (including mtime and ctime).
  451. - Implement fsync(2), fdatasync(2), and msync(2) system calls.
  452. - Enable the readv(2) and writev(2) system calls.
  453. - Enable access via the asynchronous io (aio) API by adding support for
  454. the aio_read(3) and aio_write(3) functions.
  455. 2.1.15:
  456. - Invalidate quotas when (re)mounting read-write.
  457. NOTE: This now only leave user space journalling on the side. (See
  458. note for version 2.1.13, below.)
  459. 2.1.14:
  460. - Fix an NFSd caused deadlock reported by several users.
  461. 2.1.13:
  462. - Implement writing of inodes (access time updates are not implemented
  463. yet so mounting with -o noatime,nodiratime is enforced).
  464. - Enable writing out of resident files so you can now overwrite any
  465. uncompressed, unencrypted, nonsparse file as long as you do not
  466. change the file size.
  467. - Add housekeeping of ntfs system files so that ntfsfix no longer needs
  468. to be run after writing to an NTFS volume.
  469. NOTE: This still leaves quota tracking and user space journalling on
  470. the side but they should not cause data corruption. In the worst
  471. case the charged quotas will be out of date ($Quota) and some
  472. userspace applications might get confused due to the out of date
  473. userspace journal ($UsnJrnl).
  474. 2.1.12:
  475. - Fix the second fix to the decompression engine from the 2.1.9 release
  476. and some further internals cleanups.
  477. 2.1.11:
  478. - Driver internal cleanups.
  479. 2.1.10:
  480. - Force read-only (re)mounting of volumes with unsupported volume
  481. flags and various cleanups.
  482. 2.1.9:
  483. - Fix two bugs in handling of corner cases in the decompression engine.
  484. 2.1.8:
  485. - Read the $MFT mirror and compare it to the $MFT and if the two do not
  486. match, force a read-only mount and do not allow read-write remounts.
  487. - Read and parse the $LogFile journal and if it indicates that the
  488. volume was not shutdown cleanly, force a read-only mount and do not
  489. allow read-write remounts. If the $LogFile indicates a clean
  490. shutdown and a read-write (re)mount is requested, empty $LogFile to
  491. ensure that Windows cannot cause data corruption by replaying a stale
  492. journal after Linux has written to the volume.
  493. - Improve time handling so that the NTFS time is fully preserved when
  494. converted to kernel time and only up to 99 nano-seconds are lost when
  495. kernel time is converted to NTFS time.
  496. 2.1.7:
  497. - Enable NFS exporting of mounted NTFS volumes.
  498. 2.1.6:
  499. - Fix minor bug in handling of compressed directories that fixes the
  500. erroneous "du" and "stat" output people reported.
  501. 2.1.5:
  502. - Minor bug fix in attribute list attribute handling that fixes the
  503. I/O errors on "ls" of certain fragmented files found by at least two
  504. people running Windows XP.
  505. 2.1.4:
  506. - Minor update allowing compilation with all gcc versions (well, the
  507. ones the kernel can be compiled with anyway).
  508. 2.1.3:
  509. - Major bug fixes for reading files and volumes in corner cases which
  510. were being hit by Windows 2k/XP users.
  511. 2.1.2:
  512. - Major bug fixes alleviating the hangs in statfs experienced by some
  513. users.
  514. 2.1.1:
  515. - Update handling of compressed files so people no longer get the
  516. frequently reported warning messages about initialized_size !=
  517. data_size.
  518. 2.1.0:
  519. - Add configuration option for developmental write support.
  520. - Initial implementation of file overwriting. (Writes to resident files
  521. are not written out to disk yet, so avoid writing to files smaller
  522. than about 1kiB.)
  523. - Intercept/abort changes in file size as they are not implemented yet.
  524. 2.0.25:
  525. - Minor bugfixes in error code paths and small cleanups.
  526. 2.0.24:
  527. - Small internal cleanups.
  528. - Support for sendfile system call. (Christoph Hellwig)
  529. 2.0.23:
  530. - Massive internal locking changes to mft record locking. Fixes
  531. various race conditions and deadlocks.
  532. - Fix ntfs over loopback for compressed files by adding an
  533. optimization barrier. (gcc was screwing up otherwise ?)
  534. Thanks go to Christoph Hellwig for pointing these two out:
  535. - Remove now unused function fs/ntfs/malloc.h::vmalloc_nofs().
  536. - Fix ntfs_free() for ia64 and parisc.
  537. 2.0.22:
  538. - Small internal cleanups.
  539. 2.0.21:
  540. These only affect 32-bit architectures:
  541. - Check for, and refuse to mount too large volumes (maximum is 2TiB).
  542. - Check for, and refuse to open too large files and directories
  543. (maximum is 16TiB).
  544. 2.0.20:
  545. - Support non-resident directory index bitmaps. This means we now cope
  546. with huge directories without problems.
  547. - Fix a page leak that manifested itself in some cases when reading
  548. directory contents.
  549. - Internal cleanups.
  550. 2.0.19:
  551. - Fix race condition and improvements in block i/o interface.
  552. - Optimization when reading compressed files.
  553. 2.0.18:
  554. - Fix race condition in reading of compressed files.
  555. 2.0.17:
  556. - Cleanups and optimizations.
  557. 2.0.16:
  558. - Fix stupid bug introduced in 2.0.15 in new attribute inode API.
  559. - Big internal cleanup replacing the mftbmp access hacks by using the
  560. new attribute inode API instead.
  561. 2.0.15:
  562. - Bug fix in parsing of remount options.
  563. - Internal changes implementing attribute (fake) inodes allowing all
  564. attribute i/o to go via the page cache and to use all the normal
  565. vfs/mm functionality.
  566. 2.0.14:
  567. - Internal changes improving run list merging code and minor locking
  568. change to not rely on BKL in ntfs_statfs().
  569. 2.0.13:
  570. - Internal changes towards using iget5_locked() in preparation for
  571. fake inodes and small cleanups to ntfs_volume structure.
  572. 2.0.12:
  573. - Internal cleanups in address space operations made possible by the
  574. changes introduced in the previous release.
  575. 2.0.11:
  576. - Internal updates and cleanups introducing the first step towards
  577. fake inode based attribute i/o.
  578. 2.0.10:
  579. - Microsoft says that the maximum number of inodes is 2^32 - 1. Update
  580. the driver accordingly to only use 32-bits to store inode numbers on
  581. 32-bit architectures. This improves the speed of the driver a little.
  582. 2.0.9:
  583. - Change decompression engine to use a single buffer. This should not
  584. affect performance except perhaps on the most heavy i/o on SMP
  585. systems when accessing multiple compressed files from multiple
  586. devices simultaneously.
  587. - Minor updates and cleanups.
  588. 2.0.8:
  589. - Remove now obsolete show_inodes and posix mount option(s).
  590. - Restore show_sys_files mount option.
  591. - Add new mount option case_sensitive, to determine if the driver
  592. treats file names as case sensitive or not.
  593. - Mostly drop support for short file names (for backwards compatibility
  594. we only support accessing files via their short file name if one
  595. exists).
  596. - Fix dcache aliasing issues wrt short/long file names.
  597. - Cleanups and minor fixes.
  598. 2.0.7:
  599. - Just cleanups.
  600. 2.0.6:
  601. - Major bugfix to make compatible with other kernel changes. This fixes
  602. the hangs/oopses on umount.
  603. - Locking cleanup in directory operations (remove BKL usage).
  604. 2.0.5:
  605. - Major buffer overflow bug fix.
  606. - Minor cleanups and updates for kernel 2.5.12.
  607. 2.0.4:
  608. - Cleanups and updates for kernel 2.5.11.
  609. 2.0.3:
  610. - Small bug fixes, cleanups, and performance improvements.
  611. 2.0.2:
  612. - Use default fmask of 0177 so that files are no executable by default.
  613. If you want owner executable files, just use fmask=0077.
  614. - Update for kernel 2.5.9 but preserve backwards compatibility with
  615. kernel 2.5.7.
  616. - Minor bug fixes, cleanups, and updates.
  617. 2.0.1:
  618. - Minor updates, primarily set the executable bit by default on files
  619. so they can be executed.
  620. 2.0.0:
  621. - Started ChangeLog.