From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Fri, 9 Jan 2009 12:18:35 +0000 In-Reply-To: <10bfefea89ce073c1640dd187f77ec79@plan9.cs.bell-labs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] venti Topicbox-Message-UUID: 7ddb47c8-ead4-11e9-9d60-3106f5b1d025 > Hmm. Running two ventis on the same data is, of course, bad. It's also > something I haven't seen happen before. I think it may have happened to me. Recently I had a "missing score" error when I was looking for something in my dump fs. To assess the damage I did a 'venti/copy -r' to a spare server, which told me 13 pointers had to be rewritten. I do sometimes get errors like this from my fossil server: could not write super block; waiting 10 seconds blistAlloc: called on clean block but I've been assuming they are benign. Am I wrong? My understanding of fossil is that venti writes are ordered such that the store should not be left in an inconsistent state even after a sudden shutdown. If that's the case, I'm guessing the most likely cause of corruption was a careless experiment with venti when there was already one running.