Re: [Tracker] error no reply within specified time

[Matt Klessig <matt ozbb net>]

On Sun, 2006-08-06 at 15:35 +0100, Jamie McCracken wrote:
> Gergan Penkov wrote:
>
> > > I would delete ~/.Tracker/data folder and restart over. It looks like 
> > > you killed with -9 trackerd at some point and damaged the DB (I take
> > > it you are not using ext3 for your home directory?)
> > Hi 
> > I have had such situations, one could repair the tables with 
> > myisamchk -r -q *.MYI in .Tracker/data/mysql and .Tracker/data/tracker.
> > is there some way to add checks for this and REPAIR TABLE statements
> > somewhere on tracker's start.
>
> we have auto repair enabled (tables that are not marked as closed are 
> checked and then auto repaired on startup if necessary). If corruption 
> is really bad then you might have to delete tracker's DB as the repair 
> is not guaranteed
>
>
> > Out of curiosity, what's the problem with ext3 and the home directory?
>
> its totally safe on ext3 and you should never get corruption on any file 
> let alone tracker's db.
>
> the problem is other FS which are not as reliable as Ext3 like Reiser, 
> JFS and other dubious ones. Unlike ext3, they do not have ordered mode 
> by default and so are more vulnerable to corruption if you kill -9 
> trackerd whilst its writing to the database.

I checked on the namesys website and it appears that ordered mode is the
default for reiserfs. According to my tracker log file db repair had
been attempted but failed. I guess if I add a data partition it'll be
ext3.