From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8292db0551c925534bf42b40d3729661@voidness.de>
To: 9fans@cse.psu.edu
From: Heiko Dudzus <heiko.dudzus@gmx.de>
Date: Mon, 28 Feb 2005 10:56:58 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] spurious index entries
Topicbox-Message-UUID: 57b39d12-eace-11e9-9e20-41e7f4b1d025

Sometimes in the last weeks I get log messages on the venti+fossil
fileserver saying:

could not write super block; waiting 10 seconds
blistAlloc: called on clean block

However, the system stays operational.

My first idea was to do a checkindex.  Then I get a lot of these
messages:

spurious entry in index for score=<score>; found 6 entries expected 5
bad bucket found=396084: unknown error
spurious entry in index for score=<score> type=13
bad bucket found=396959: unknown error
spurious entry in index for score=<score> type=13

This sounds alarming.  What does that mean, in fact?  Are archived
data corrupted?  Is it likely to be just a hard disk error?

Heiko