I am seeing this issue too. I'm using a laptop with a fully crypted hard
disk, including swap. Typing in this report is actually quite annoying
with the occassional freezes happening.

The tracker logs files trackerd.log and tracker-extract.log are empty
for me.

The log file tracker-indexer.log has this kind of lines repeating (about
30-40 so far, the empty lines between messages are verbatim from the log
file):

28 May 2009, 13:53:00: Tracker-Warning **: Invalid byte sequence in
conversion input

28 May 2009, 13:58:11: Tracker-Warning **: Invalid byte sequence in
conversion input

28 May 2009, 13:58:24: Tracker-Warning **: Invalid byte sequence in
conversion input

28 May 2009, 13:58:41: Tracker-Warning **: Invalid byte sequence in
conversion input

28 May 2009, 13:59:18: Tracker-Warning **: Invalid byte sequence in
conversion input

28 May 2009, 13:59:30: Tracker-Warning **: Invalid byte sequence in
conversion input

....

Nothing else in the log file than those. First message timestamp 28 May
2009, 13:32:45, last message timestamp 28 May 2009, 13:59:30 - then the
problem seems to have gone away.


Here's some example vmstat 5 output during the problem happening:

procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
 2  5  31772  61980  52816 1091324    0    0     6    69 1547 4823 13  9  0 79
 0  3  31772  60236  52844 1092776    0    0    54  1747 1889 3812 26 10  6 59
 1  0  31772  58048  53068 1097516    0    0   567    66 2159 5687 37 11 25 26
 2  0  31856  60760  51692 1095632    0   17   713   867 1875 5774 50 10 29 11
 1  0  31856  55448  51864 1101752    0    0   881   614 1900 5431 49 11 29 11
 2  0  31868  52564  51568 1105264    0    2   938   496 1815 4424 46  9 37  8
 3  0  32040  52724  51328 1105608    0   34  1058   617 1979 4839 43 10 39  8
 1  0  32168  53588  51204 1104140    0   26  1039   631 1988 4884 45  9 38  9
 0  2  32400  53880  51148 1102076    0   46   127  4414 1978 3828 23 19 25 34
 1  3  32592  56484  51040 1096148    0   38    50  7881 1952 4213 21 11 30 38
 0  6  32592  57016  51044 1096072    0    0     8     0 1924 4081 24  9  3 64
 1  7  32592  57884  51044 1096072    0    0     0     1 1642 4603  7  7  0 86
 0  7  32592  58480  51044 1096072    0    0     0     0 1705 5137  8  7  0 85
 1  7  32592  59444  51044 1096072    0    0     0     0 1641 4688  7  8  0 84
 2  0  32592  57656  51212 1100876    0    0   685    70 1941 4879 39  9 27 25
 1  0  32592  54016  51648 1103456    0    0   762   462 1969 4499 40  9 38 13
 2  0  32592  53448  52472 1104204    0    0   429   709 1858 3993 34  8 40 18
 5  1  32784  53152  53608 1102884    0   38   234   776 1942 3964 29 10 37 24
 4  0  32804  53460  53820 1102248    0    4   884   634 2063 5030 41 10 39 10

The bi/bo values go to 0 whenever the system freezes, so I would think it's 
some kind of io-issue. The CPU IO-wait time jumps then.
CPU doesn't seem to go to 100% usage at all, so not a CPU-bound issue.

I was playing some music at the time, the playing would stop whenever
the freeze occurred.

-- 
tracker IO activity slows down ubuntu 9.04
https://bugs.launchpad.net/bugs/373158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to