From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d8567b09bf095c62ee4fc68d6c1ec873@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Thu, 22 Mar 2012 19:24:16 +0000
In-Reply-To: <CANUoZoFygdgrpeFEu+f5j--YtMJS-pmw_MLaPQL_V_ESm9LMtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] fossil archive corruption - solved
Topicbox-Message-UUID: 6e69917a-ead7-11e9-9d60-3106f5b1d025

> I've not been able to easily reproduce this problem.
> How did you proceed?

Not very reproducible, but I found it could be encouraged to happen
(on a sacrificial secondary fossil+venti) with this:
	tar c /n/xfossil/sys/src >/dev/null &
	while (sleep 60) echo snap -a >>/srv/xfscons

An easily recognisable consequence when it fails is a BtDir block with
invalid contents.  So I peppered the source with diagnostics checking
for that, until I was able to spot exactly where it happened.