From: Nemo <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil archive corruption - solved
Date: Thu, 22 Mar 2012 20:54:36 +0100 [thread overview]
Message-ID: <CFECE7F9-5F96-4511-9861-CFCC5DBFF2B1@lsub.org> (raw)
In-Reply-To: <d8567b09bf095c62ee4fc68d6c1ec873@hamnavoe.com>
impressive. hats off.
--
iphone kbd. excuse typos :)
On Mar 22, 2012, at 8:24 PM, Richard Miller <9fans@hamnavoe.com> wrote:
>> 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.
>
prev parent reply other threads:[~2012-03-22 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 16:30 Richard Miller
2012-03-22 16:48 ` cinap_lenrek
2012-03-22 17:57 ` Steve Simon
2012-03-22 20:06 ` steve
2012-03-22 18:32 ` David du Colombier
2012-03-22 19:24 ` Richard Miller
2012-03-22 19:54 ` Nemo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CFECE7F9-5F96-4511-9861-CFCC5DBFF2B1@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).