Just a guess ... ntfs-3g is the 3rd generation ntfs driver for the windows partitions. When used (filesystem access), it uses quite some CPU. No idea why some people say it is efficient ... I treat it as tool to write ntfs, when necessary.
So, for your problem ... if some background process searches the ntfs partition(s), the cpu load of the process goes up ... I'd suspect updatedb/(s)locate first, then beagled ... When this happens, run a "ps fax" to find out which jobs are running; usually, there is a large tree of cron-started processes, if it is updatedb. If the windows partitions are not mounted in /mnt, have a look at /etc/sysconfig/locate and add the partitions/paths to UPDATEDB_PRUNEPATHS Then, locate should not search the ntfs-folders. Alternatively, if you don't need/want to write into the ntfs folders, use the old kernel ntfs driver, which is r/o. Hope this helps, Sebastian Alexey Eremenko wrote: > On 10/26/07, David C. Rankin J.D. P.E. <[EMAIL PROTECTED]> wrote: >> Listmates, >> >> What is it that causes mount.ntfs-3g to run at what seems like random >> times. When this occurs, it will eat 17-30% pf the CPU running for >> several minutes also creating a lot of hard drive activity. Is this >> something like beagle that I can just shoot in the head? >> > > I experienced similar problem, but it's gone now. (I don't know why it > happened) > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
