[Bug 13964] ext4: panic causes lost data in git

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=13964





--- Comment #1 from Jesse Brandeburg <jesse.brandeburg@intel.com>  2009-08-11 19:02:48 ---
related info, I'll try the alloc_on_commit option
http://www.h-online.com/open/Ext4-data-loss-explanations-and-workarounds--/news/112892

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=13964


Roland Kletzing <devzero@web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |devzero@web.de




--- Comment #2 from Roland Kletzing <devzero@web.de>  2009-08-28 19:34:16 ---
i also have seen this issue, but i can`t find alloc_on_commit option in latest
.git kernel.  hasn`t the appropriate patch been merged?

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

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.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=13964





--- Comment #4 from Roland Kletzing <devzero@web.de>  2009-08-29 13:06:46 ---
ok, but what is the solution for all the apps which don`t have issues with ext3
but start having issues with ext4? fix all the apps? that would take a long
time...   alloc_on_commit really sounds like a good compatibility switch....

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=13964





--- Comment #5 from Jesse Brandeburg <jesse.brandeburg@intel.com>  2010-05-25 17:56:58 ---
I was unable to continue using ext4 for development since it was not reliable
through panic.  Was there ever any progress on this issue?  Due to this bug I
have been telling everyone I work with to not use ext4.

It is a pretty easy bug to reproduce, isn't there something we can do about it?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=13964


Eric Sandeen <sandeen@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@redhat.com




--- Comment #6 from Eric Sandeen <sandeen@redhat.com>  2010-05-25 18:02:53 ---
Jesse, are you still running with data=writeback (as comment nr. 1 seemed to
indicate, since you said you would -try- data=ordered...) - data=writeback is
just not safe at all for anybody, anywhere, any time, unless you plan to
recreate all data post-crash.

With default mount options (which includes data=ordered) do you still see this
problem on upstream kernels?

In the end, though, you have to realize that buffered data which is not synced
to disk -will- be lost on a crash.  This is true for all filesystems, though
the window of "opportunity" may differ....

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=13964


Alan <alan@lxorguk.ukuu.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |alan@lxorguk.ukuu.org.uk
         Resolution|                            |WILL_NOT_FIX




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13964] ext4: panic causes lost data in git

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=13964


Alan <alan@lxorguk.ukuu.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.