From: Johannes Sixt <j.sixt@viscovery.net>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: git@vger.kernel.org
Subject: Re: repo consistency under crashes and power failures?
Date: Tue, 16 Jul 2013 08:17:20 +0200 [thread overview]
Message-ID: <51E4E570.1060403@viscovery.net> (raw)
In-Reply-To: <rmiy597iujc.fsf@fnord.ir.bbn.com>
Am 7/15/2013 19:48, schrieb Greg Troxel:
> Clearly there is the possibility of creating a corrupt repository when
> receiving objects and updating refs, if a crash or power failure causes
> data not to get written to disk but that data is pointed to. Journaling
> mitigates this, but I'd argue that programs should function safely with
> only the guarantees from POSIX.
Even under POSIX, "guarantees" and "crash/power failure" do not mesh well.
This has been under dispute recently, for example:
http://thread.gmane.org/gmane.comp.standards.posix.austin.general/7456/focus=7487
The best we can achieve with POSIX alone is "to make bad consequences less
likely".
Jonathan already mentioned the knob that allows you to trade performance
for more safety.
-- Hannes
next prev parent reply other threads:[~2013-07-16 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 17:48 repo consistency under crashes and power failures? Greg Troxel
2013-07-15 17:51 ` Jonathan Nieder
2013-07-16 6:17 ` Johannes Sixt [this message]
2013-07-27 3:10 ` Jeff King
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=51E4E570.1060403@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=gdt@ir.bbn.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.