From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 11 Aug 2011 17:30:20 +0200
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Message-ID: <20110811173020.4c5b2d5a@wks-ddc.exosec.local>
In-Reply-To: <3024dec4bf02b67a94b6fffa791be9bf@quintile.net>
References: <20110811101127.52627669@wks-ddc.exosec.local>
	<3024dec4bf02b67a94b6fffa791be9bf@quintile.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Fossil fs recovery
Topicbox-Message-UUID: 0e97f6d8-ead7-11e9-9d60-3106f5b1d025

> > fsys main snaptime -s 60 -a 0530 -t 2880
>
> Beware: there is currently a bug in fossil which can cause
> it to deadlock under load if ephemerial snapshots are enabled.
>
> This I reccomend you use a configuration more like:
>
> 	fsys main snaptime -s none -a 0530 -t none

As far as know and like Geoff Collyer wrote to the fossilcons(8)
manual recently, this bug happens when both archival and
temporary snapshots happen at the same time.

This is not the case here, because the archival snapshot is
taken at 05:30, while the temporary snapshot happens on the hour.

Thus, it should be safe to use temporary snapshots here.

--
David du Colombier