From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <069a199a73e794095891a4254e7b765d@orthanc.ca>
To: 9fans@9fans.net
From: "Lyndon Nerenberg (VE6BBM/VE7TFX)"  <lyndon@orthanc.ca>
Date: Sat, 13 Aug 2011 16:44:05 -0700
In-Reply-To: <8ae9a625c55508d5f1ac7dc193e9b274@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Fossil fs recovery
Topicbox-Message-UUID: 12b25524-ead7-11e9-9d60-3106f5b1d025

> Actually we have since found that even scheduling archival
> and temporary snapshots at different times isn't always
> enough to prevent fossil from hanging during archival
> snapshots.

What size of fossil and venti?  Can you post details of how
the servers are set up?  I.e. fossil/conf and venti/conf plus
the output from 'hget http://venti/storage'?  Maybe we can
find a pattern in the configuration of these setups that's
provoking the hangs.

Any idea how long it's taking your archive dumps to run out?
And how much data is being flushed?

For that matter, can anyone explain the use of those
undecipherable venti graph/... urls?  Maybe at least
the victims can start logging some performance numbers
for more pattern matching?

--lyndon