New: ext4: panic causes lost data in git
http://bugzilla.kernel.org/show_bug.cgi?id=13964
Summary: ext4: panic causes lost data in git
Product: File System
Version: 2.5
Kernel Version: 2.6.31-rc5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: [email protected]
ReportedBy: [email protected]
Regression: No
When working within a local git tree, I committed a change, compiled and reloaded my driver, which caused a panic.
After reboot my .git/objects/xx/xxxx (latest commit) had empty files. This doesn't seem to be an acceptable loss of data. I've since started mounting /home with data=ordered in the hope it would help.
I've mounted my LVM / and /home partitions with the default options
here is the output of tune2fs on /home
[root@jbrandeb-hc jbrandeb]# tune2fs -l /dev/mapper/vg_jbrandebhc-HomeVol tune2fs 1.41.4 (27-Jan-2009)
Filesystem volume name: <none> Last mounted on: /home Filesystem UUID: 696e2e7d-467d-47b3-992e-a28dcf9b1ef8 Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetypeneeds_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 8454144 Block count: 33792000 Reserved block count: 1689600 Free blocks: 32742879 Free inodes: 8386475 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1015 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Tue Jun 23 09:50:14 2009 Last mount time: Tue Aug 11 11:55:14 2009 Last write time: Tue Aug 11 11:55:14 2009 Mount count: 1 Maximum mount count: -1 Last checked: Tue Aug 11 11:55:06 2009 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 25ca440e-1707-4084-ac05-3addd26ad952 Journal backup: inode blocks
Any other information will be gladly provided.
Signature · 3 lines
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
http://bugzilla.kernel.org/show_bug.cgi?id=13964
--- Comment #1 from Jesse Brandeburg <[email protected]> 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
Signature · 3 lines
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
In reply to [email protected]http://bugzilla.kernel.org/show_bug.cgi?id=13964
Roland Kletzing <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #2 from Roland Kletzing <[email protected]> 2009-08-28 19:34:16 --- i also have seen this issue, but i cant find alloc_on_commit option in latest .git kernel. hasnt the appropriate patch been merged?
Signature · 3 lines
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
In reply to [email protected]http://bugzilla.kernel.org/show_bug.cgi?id=13964
Theodore Tso <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #3 from Theodore Tso <[email protected]> 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.
Signature · 3 lines
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
In reply to [email protected]http://bugzilla.kernel.org/show_bug.cgi?id=13964
--- Comment #4 from Roland Kletzing <[email protected]> 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....
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.