mount.ntfs high cpu ubuntu

My computer suffers from sudden and continous hard drive load strokes. Sometimes it lasts for a few minutes and hence work is impossible because everything goes very slow.I’m trying to locate the cause because it makes me nervous :)Today I found one of…

My computer suffers from sudden and continous hard drive load strokes. Sometimes it lasts for a few minutes and hence work is impossible because everything goes very slow.
I’m trying to locate the cause because it makes me nervous :)

Today I found one of the causes. It’s updatedb.mlocate script which is responsible for scanning hard drives and build locate (a location of files) database. But due to some NTFS driver limitations that poor thing thinks that NTFS share is always new and needs to be rescan at every scheduled scan.

How to make sure that you have the same problem? When hard drive starts to choke check all IO processes with

sudo iotop

and look for updatedb.mlocate or mount.ntfs processes with high IO load. If this is the case try to fix it.
The solution is to point NTFS shares as non-scannable. To do this edit

/etc/updatedb.conf

and add your NTFS mount paths to PRUNEPATHS list. Although NTFS is listed in PRUNEFS entry that dummy mlocate script still would scan NTFS shares.

All that I found on Ubuntu forum.

You May Also Like

Distributed scans with HBase

HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?