From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Fossil fs recovery
Date: Sun, 14 Aug 2011 07:21:13 +0100 [thread overview]
Message-ID: <7c79006a18cf3062d910d62a9e0eb893@quintile.net> (raw)
In-Reply-To: <069a199a73e794095891a4254e7b765d@orthanc.ca>
I certinaly had problems a few years ago with fossil deadlocking,
since I disabled ephemeral snapshots it has been quite reliable.
My feeling (nothing more than that) was that the deadlocks seemed to
occur when I receved email just at the time of the snapshot.
the problem seemed to occur at a rate of once per month or two
for my lightly loaded home server.
I did try to run two file servers for a while, exporting
/proc from the test machine with snapshots enabled to a seccond one.
The hope was that I would be able to use acid to debug the test machine's
fossil when the problem occured. Sadly I never caught the problem and
had to decomission the old machine (house repairs).
-Steve
next prev parent reply other threads:[~2011-08-14 6:21 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
2011-08-13 19:12 ` geoff
2011-08-13 23:44 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-14 6:21 ` Steve Simon [this message]
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=7c79006a18cf3062d910d62a9e0eb893@quintile.net \
--to=steve@quintile.net \
--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).