9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Fossil fs recovery
Date: Thu, 11 Aug 2011 17:30:20 +0200	[thread overview]
Message-ID: <20110811173020.4c5b2d5a@wks-ddc.exosec.local> (raw)
In-Reply-To: <3024dec4bf02b67a94b6fffa791be9bf@quintile.net>

> > 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



  reply	other threads:[~2011-08-11 15:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 16:21 Bernd Maier
2011-08-10 17:46 ` David du Colombier
2011-08-10 21:58 ` Steve Simon
2011-08-10 22:12   ` ron minnich
2011-08-11  8:11     ` David du Colombier
2011-08-11 13:46       ` David Leimbach
2011-08-11 13:56         ` Jack Norton
2011-08-11 15:37           ` David du Colombier
2011-08-11 15:15       ` Steve Simon
2011-08-11 15:30         ` David du Colombier [this message]
2011-08-13 19:12           ` geoff
2011-08-13 23:44             ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-14  6:21               ` Steve Simon
2011-08-14 11:48                 ` Francisco J Ballesteros
2011-08-14 17:55                 ` David du Colombier
  -- strict thread matches above, loose matches on Subject: below --
2011-08-14 14:49 Bernd Maier
2011-08-12  9:53 Bernd Maier
2011-08-12 12:03 ` David du Colombier
2011-08-10 12:35 Bernd Maier
2011-08-10 15:25 ` Steve Simon

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=20110811173020.4c5b2d5a@wks-ddc.exosec.local \
    --to=0intro@gmail.com \
    --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).