Page 1 of 1

ntfs3g high cpu usage with deluge

Posted: Thu Jul 24, 2008 9:17 am
by weltall
I've been using deluge fine for a long time with ntfs3g but last week I've encountered a certain special case were deluge makes ntfs3g use 100% of CPU constantly till it's closed (as it's a dual core CPU it uses entirely one core), additionally the same torrent while reporting for example now 79% completed if i look in the file tab i get the file was only completed for 6,28% :shock: . Additionally the torrent is extremely slow and other with the same torrent says it isn't... (things like 2-20KB/s max)
The torrent has only one file which is an mkv of 4,4gb and the configuration for allocation is full allocation (i can see the file as being 4,4gb from nautilus).
Other torrents on the same disk with the same drivers distribution etc but with less big files (splitted rars) doesn't give this problem at all and works fine.
I've already tried rebooting and launching only deluge and the CPU usage of ntfs3g went to 100% immediately

Ubuntu 8.04.1
Linux 2.6.26-custom #1 SMP Tue Jul 15 12:52:42 CEST 2008 i686 GNU/Linux
ntfs-3g 1.2216 external FUSE 27
Deluge 0.5.9.3

does anyone have any idea about how to fix this problem? if you need any other information just ask.
Thanks in advance :)

Re: ntfs3g high cpu usage with deluge

Posted: Wed Apr 15, 2009 9:53 am
by mummu
I have the same problem with 9.04 and intel quad core.

Re: ntfs3g high cpu usage with deluge

Posted: Thu Apr 16, 2009 4:27 am
by Ux64
It would be nice if you could pause all torrents. And check if that 4 gb barrier is causing some problems.

Try downloading anything less that 4 gb and then file over 4 gb and check if that's the thing causing problems.

Problem might also be ntfs3g related because people aren't suffering from that problem when using ext3/4.

Some times it's hard to say what is really causing the problem. But after that you'll have nice start.

Just to confirm it, move that download (over 4gb) to ext3 drive and check that problem disappears.

Then problem lies between ntfs3g and deluge. Then you can try if general random access to files largen than 4gb causes problems on ntfs drive and there you got it. Then problem is ntfs3g related. Then you'l need to contact them to get if fixed.

Let me know what happened.