Lines Matching +full:performance +full:- +full:affecting
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 - Limitations when using the MD driver
22 Linux-NTFS comes with a number of user-space programs known as ntfsprogs.
23 These include mkntfs, a full-featured ntfs filesystem format utility,
29 system type 'ntfs'. The driver currently supports read-only mode (with no
30 fault-tolerance, encryption or journalling) and very limited, but safe, write
41 There is plenty of additional information on the linux-ntfs web site
42 at http://www.linux-ntfs.org/
45 FAQ, documentation on the NTFS on-disk format, information on the Linux-NTFS
52 - This is a complete rewrite of the NTFS driver that used to be in the 2.4 and
60 - The new driver has full support for sparse files on NTFS 3.x volumes which
62 - The new driver supports execution of binaries due to mmap() now being
64 - The new driver supports loopback mounting of files on NTFS which is used by
69 - A comparison of the two drivers using:
70 time find . -type f -exec md5sum "{}" \;
76 - The driver does not support short file names in general. For backwards
80 - The new driver supports exporting of mounted NTFS volumes via NFS.
81 - The new driver supports async io (aio).
82 - The new driver supports fsync(2), fdatasync(2), and msync(2).
83 - The new driver supports readv(2) and writev(2).
84 - The new driver supports access time updates (including mtime and ctime).
85 - The new driver supports truncate(2) and open(2) with O_TRUNC. But at present
91 - The new driver supports write(2) which can both overwrite existing data and
132 default rw------- and for directories rwx------, a
151 will not be visible due to bugs/mis-features in glibc.
154 "ls -l \$UpCase" for example to specifically show the
178 continue: DEFAULT, try to clean-up as much as
184 If read-only mount, the recovery is done
189 fails it will clean-up as much as possible and
201 on performance by affecting fragmentation of the MFT.
210 Note this option is irrelevant for read-only mounts.
213 Known bugs and (mis-)features
216 - The link count on each directory inode entry is set to 1, due to Linux not
224 Please send bug reports/comments/feedback/abuse to the Linux-NTFS development
225 list at sourceforge: linux-ntfs-dev@lists.sourceforge.net
232 Device-Mapper driver or the kernel's Software RAID / MD driver. The former is
237 The Device-Mapper driver
238 ------------------------
248 Device-Mapper driver does not support raid level 5. You may be able to use the
252 components and their sizes in sectors, i.e. multiples of 512-byte blocks.
257 $ fdisk -ul /dev/hda
268 And you would know that /dev/hda2 has a size of 37768814 - 4209030 + 1 =
273 writing is linux-ldm-0.0.8.tar.bz2). You can download it from:
274 http://www.linux-ntfs.org/
275 Simply extract the downloaded archive (tar xvjf linux-ldm-0.0.8.tar.bz2), go
276 into it (cd linux-ldm-0.0.8) and change to the test directory (cd test). You
282 $ ./ldminfo --dump /dev/hda
298 in the Device-Mapper table.
308 512-byte sectors):
310 --- cut here ---
316 --- cut here ---
323 512-byte sectors):
325 --- cut here ---
330 --- cut here ---
336 this (note all values are in 512-byte sectors):
338 --- cut here ---
343 --- cut here ---
351 and the Device-Mapper driver will then copy the entirety of the "Source Device"
362 If it all worked, you will now have the device /dev/device-mapper/myvolume1
366 $ mount -t ntfs -o ro /dev/device-mapper/myvolume1 /mnt/myvol1
372 It is advisable to do the mount read-only to see if the volume has been setup
378 -----------------------------
380 An alternative to using the Device-Mapper driver is to use the kernel's
390 You have to use the "persistent-superblock 0" option for each raid-disk in the
395 "chunk-size 64k" option for each raid-disk, too.
401 raid-level 0
402 nr-raid-disks 2
403 nr-spare-disks 0
404 persistent-superblock 0
405 chunk-size 64k
407 raid-disk 0
409 raid-disk 1
411 For linear raid, just change the raid-level above to "raid-level linear", for
412 mirrors, change it to "raid-level 1", and for stripe sets with parity, change
413 it to "raid-level 5".
416 which parity algorithm to use by specifying the option "parity-algorithm
420 are working read-only when playing with this as you may damage your data
422 linux-ntfs developers list linux-ntfs-dev@lists.sourceforge.net or drop in on
426 Once the raidtab is setup, run for example raid0run -a to start all devices or
430 example: mount -t ntfs -o ro /dev/md0 /mnt/myntfsvolume
432 It is advisable to do the mount read-only to see if the md volume has been
438 -----------------------------------------------------
450 Even better is to simply use the Device-Mapper for linear raid and then you do