Comment 11 for bug 24063

During tag update mount.ntfs-3g consumes CPU nearly 100% for some amount of time, though, this amount of time seems reasonable to me - like ntfs-3g does it's job like it should. Then for some period CPU load is low - amarok is doing something, and sometimes these periods are really large - like four minutes in my second screenshot. After the tag update process finishes, amarok starts to behave unstable - doesn't respond, hangs for some time, then unhangs, does database updates a few times in a row (last time all these processes ended 10 minutes after the last file was updated, and amarok still has the tendency to hang from time to time on few seconds) - but CPU usage stays low.

In my opinion, it's not ntfs-3g problem, but amarok (and/or maybe underlying libs - libflac, whatever) one. I had amarok/mp3/ntfs-3g triplet working ok for quite a long time now, but today as I tried flac for the first time, I encountered the whole bunch of problems.

I will test more on ext3, and if I would be able to reproduce this behaviour on ntfs-3g only, I'll go for ntfs-3g debug.