English: This is a side view of the read head ...

Yesterday I had to boot a Windowds virtual machine NTFS my share. To my great surprise, the machine started dragging an awful lot when virtualbox started creating its virtual HDD. WFT ??? Immediately a quick top and the problem shone. ntfs-3g was crashed on 100% cpu usage 3 of my 6 cores. Hmmm foreign. After a contemplation in the following line, the problem shone through

/sbin/mount.ntfs-3g /dev/sda4 /media/disk1part4 -o rw

Obviously / dev / sda4 is mounted with default options only. In general, the ntfs driver has dirt with intensive writing and reading on the partition if it is not provided with some miraculous settings.

  1. big_writes – the most important option to drop the load intensity of your system using large block recording.
  2. noatime – speeds up the system by disabling inode updates access time if we don't need it. Personally, I don't need it at all
  3. windows_names – there is no acceleration here but on the other hand the file names are treated according to the MS conventions in which the file names, regardless of whether they are uppercase and lowercase, are the same.

After I fixed the options with which my partition is installed fstab the record looked like this

UUID=2213f519-f980-42bf-9e25-9201db38c458  /media/disk1part4  ntfs-3g  defaults,big_writes,windows_names,noatime 0 0

Enhanced by Zemanta