Is buffindexed overview corruption problem fixed in -STABLE?

Katsuhiro Kondou kondou at nec.co.jp
Thu Sep 28 16:19:01 UTC 2000


In article <20000928105837.F536 at ksu.edu>,
	Tim Ramsey <tar at ksu.edu> wrote;

} Doh, sorry.  This is a SS10 running Solaris 2.6 with all current
} recommended patches applied.  inn-2.3.0 was configured with these
} options:

Hm, I'm also running on 2.6.  But the difference is you and Anders
creates buffer on block device.  Oh, I just remembered I once did,
but stopped to use it, since I'd had the same messages;

Jul 12 02:33:31 server expireover[5109]: buffindexed: ovgroupmmap ovbuff is null(ovindex is 13112, ovblock is 842019127
Jul 12 02:33:31 server expireover[5109]: buffindexed: could not open overview for 'control.cancel'
Jul 12 02:33:31 server expireover[5109]: buffindexed: ovgroupmmap ovbuff is null(ovindex is 2353, ovblock is 875575352
Jul 12 02:33:31 server expireover[5109]: buffindexed: could not open overview for 'junk'
Jul 12 02:33:31 server expireover[5109]: buffindexed: ovgroupmmap ovbuff is null(ovindex is 13616, ovblock is 825242424
Jul 12 02:33:31 server expireover[5109]: buffindexed: could not open overview for '1.beginners.sex'

After creating buffers as regular files, those are gone.  I'm not
sure but regional lock on block device may not work.  Are still
someone there who get those messages on regular files?

} >That would be.  And it should not be done, since overview
} >data could be duplicated and this leads to incorrect number
} >of articles in responding to 'GRUOP'.
} 
} I'm sorry, I don't understand what you are saying.  Are you saying that
} innd should not be running while makehistory is rebuilding the overview
} database?

Yes.
-- 
Katsuhiro Kondou



More information about the inn-workers mailing list