index inode mismatch

Marco d'Itri md at Linux.IT
Mon Jan 27 09:29:56 UTC 2003


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


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
ctlinnd: Cannot read input file
Expire messages:
expire begin Mon Jan 27 04:15:52 CET 2003: (-v1 -z/var/log/news/expire.rm)
    expire: cannot reserve server
    Article lines processed        0
    Articles retained              0
    Entries expired                0
    Articles dropped               0
expire end Mon Jan 27 04:15:52 CET 2003
        all done Mon Jan 27 04:15:52 CET 2003
        expireover start Mon Jan 27 04:15:52 CET 2003
        expireover end Mon Jan 27 04:16:17 CET 2003
lowmarkrenumber begin Mon Jan 27 04:16:17 CET 2003: (/var/log/news/expire.lowmark)
lowmarkrenumber end Mon Jan 27 04:16:17 CET 2003

-- 
ciao,
Marco


More information about the inn-workers mailing list