index inode mismatch

[Russ Allbery]

Marco d'Itri <md at Linux.IT> writes:

> What does this mean? My log has about 200 of these messages after
> upgrading from CURRENT-20020922 to CURRENT-20030125.

> innd: tradindexed: index inode mismatch for linux.debian.maint.kde
> innd: tradindexed: index inode mismatch for 4167DFE566EF5C4CFEA7BA3DFF7BCCA9
> innd: tradindexed: index inode mismatch for it.cultura.religioni.buddhismo
> innd: tradindexed: index inode mismatch for 2FAC225606BFECEDE2671342BE8D1081
> innd: tradindexed: index inode mismatch for linux.debian.maint.kde
> innd: tradindexed: index inode mismatch for 4167DFE566EF5C4CFEA7BA3DFF7BCCA9

It means that the inode of the newsgroup stored in the index file for
tradindexed doesn't match the inode of the actual .IDX file.

> This is just the test and I have not checked what broke, but I hope this
> does not eat data as I used this snapshot for the new debian package. :-)

> This log entry is not recognized by inndstart, BTW.

> I do not know if it's related, but expire did not work:

> [...]
> expireover: tradindexed: index inode mismatch for linux.debian.user.polish

This should just be a warning.

> ctlinnd: Cannot read input file

This would be the real problem.  At a guess, you're experiencing the
ctlinnd bug that was reported earlier and is fixed in CVS, but isn't in
the snapshots.

For the tradindexed stuff, tdx-util -A should tell you what's going on,
and tdx-util -F will probably clean up whatever is wrong.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.