From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13964] ext4: panic causes lost data in git
Date: Sat, 29 Aug 2009 02:47:24 GMT [thread overview]
Message-ID: <200908290247.n7T2lO7t030695@demeter.kernel.org> (raw)
In-Reply-To: <bug-13964-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13964
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #3 from Theodore Tso <tytso@mit.edu> 2009-08-29 02:47:23 ---
The alloc_on_commit patch had a number of deadlock problems, and I've never had
time to try to work them out.
For now, the recommended solution for git is to put the following in your
.gitconfig file:
[core]
fsyncobjectfiles = yes
This will cause git to force an fsync() when writing object files, which is the
only portable way of guaranteeing the object files will be written after a
crash. This is needed for safety reasons for ext4, xfs, and btrfs filesystems.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-08-29 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 18:58 [Bug 13964] New: ext4: panic causes lost data in git bugzilla-daemon
2009-08-11 19:02 ` [Bug 13964] " bugzilla-daemon
2009-08-28 19:34 ` bugzilla-daemon
2009-08-29 2:47 ` bugzilla-daemon [this message]
2009-08-29 13:06 ` bugzilla-daemon
[not found] <bug-13964-13602@https.bugzilla.kernel.org/>
2010-05-25 17:57 ` bugzilla-daemon
2010-05-25 18:02 ` bugzilla-daemon
2012-06-13 14:48 ` bugzilla-daemon
2012-06-13 14:49 ` bugzilla-daemon
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=200908290247.n7T2lO7t030695@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.