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