git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git status core dump with bad sector!

From
ECEric Chamberland <eric.chamberland@giref.ulaval.ca>
Date
Apr 14, 2016, 14:59 UTC
Message-ID
<570FB06D.5060308@giref.ulaval.ca>
Hi,

just cloned a repo and it checked-out wihtout any error (with git 2.2.0) but got come corrupted files (because I got some sdd failures).

Then, I get a git core dump when trying to "git status" into the repo which have a "bad sector" on sdd drive (crypted partition).

I tried with git 2.2.0 AND git version 2.8.1.185.gdc0db2c.dirty (just modified the Makefile to remove STRIP part)

In both cases, I have a  Bus error (core dumped)
Tried to make it more verbose:

GIT_TRACE=2 GIT_CURL_VERBOSE=2 GIT_TRACE_PERFORMANCE=2 GIT_TRACE_PACK_ACCESS=2 GIT_TRACE_PACKET=2 GIT_TRACE_PACKFILE=2 GIT_TRACE_SETUP=2 GIT_TRACE_SHALLOW=2 /opt/gitgit/bin/git status 10:54:30.644999 trace.c:318 setup: git_dir: .git 10:54:30.645094 trace.c:319 setup: git_common_dir: .git 10:54:30.645102 trace.c:320 setup: worktree: /pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit/TestValidation_avec_erreur_disque_git_core_dump_dans_dev_Test.ExportationVTK_Avion 10:54:30.645112 trace.c:321 setup: cwd: /pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit/TestValidation_avec_erreur_disque_git_core_dump_dans_dev_Test.ExportationVTK_Avion 10:54:30.645151 trace.c:322 setup: prefix: Ressources/dev/Test.ExportationVTK/ 10:54:30.645181 git.c:350 trace: built-in: git 'status' Bus error (core dumped)

started in gdb:
Program received signal SIGBUS, Bus error.
0x00007ffff7866d58 in ?? () from /lib64/libcrypto.so.1.0.0
(gdb) bt
#0  0x00007ffff7866d58 in ?? () from /lib64/libcrypto.so.1.0.0
#1  0x3334d90d8c20f3f0 in ?? ()
#2  0xe59b5a6cd844a601 in ?? ()
#3  0xc587a53f67985ae7 in ?? ()
#4  0x3ce81893e5541777 in ?? ()
#5  0xdeb18349a4b042ea in ?? ()
#6  0x8254de489067ec4b in ?? ()
#7  0x6fbef2439704c81b in ?? ()
#8  0xe0eee2bb385a96da in ?? ()
#9  0x00007ffff6e19ab3 in ?? ()
#10 0x00007fffffffc4d0 in ?? ()
#11 0x000000000000001d in ?? ()
#12 0x00007ffff7863f80 in SHA1_Update () from /lib64/libcrypto.so.1.0.0
#13 0x00000000005102c0 in write_sha1_file_prepare 
(buf=buf@entry=0x7ffff6c81000, len=1673936, type=<optimized out>, 
sha1=sha1@entry=0x7fffffffc750 "\340_~", hdr=hdr@entry=0x7fffffffc570 
"blob 1673936",
     hdrlen=hdrlen@entry=0x7fffffffc56c) at sha1_file.c:2951
#14 0x000000000051567b in hash_sha1_file (buf=buf@entry=0x7ffff6c81000, 
len=<optimized out>, type=<optimized out>, 
sha1=sha1@entry=0x7fffffffc750 "\340_~") at sha1_file.c:3010
#15 0x00000000005159f8 in index_mem (sha1=sha1@entry=0x7fffffffc750 
"\340_~", buf=buf@entry=0x7ffff6c81000, size=1673936, 
type=type@entry=OBJ_BLOB,
     path=path@entry=0x80a818 
"Ressources/dev/Test.ExportationVTK/Ressources.Avion/Avion.Quadratique.cont.vtu.etalon", 
flags=flags@entry=0) at sha1_file.c:3305
#16 0x00000000005160ee in index_core (flags=0, path=0x80a818 
"Ressources/dev/Test.ExportationVTK/Ressources.Avion/Avion.Quadratique.cont.vtu.etalon", 
type=OBJ_BLOB, size=<optimized out>, fd=7,
     sha1=0x7fffffffc750 "\340_~") at sha1_file.c:3367
#17 index_fd (sha1=sha1@entry=0x7fffffffc750 "\340_~", fd=7, 
st=st@entry=0x7fffffffc7c0, type=type@entry=OBJ_BLOB,
     path=path@entry=0x80a818 
"Ressources/dev/Test.ExportationVTK/Ressources.Avion/Avion.Quadratique.cont.vtu.etalon", 
flags=flags@entry=0) at sha1_file.c:3410
#18 0x00000000004eac66 in ce_compare_data (st=0x7fffffffc7c0, 
ce=0x80a7c0) at read-cache.c:166
#19 ce_modified_check_fs (ce=0x80a7c0, st=0x7fffffffc7c0) at 
read-cache.c:215
#20 0x00000000004ebb6d in ie_modified (istate=istate@entry=0x7e5fe0 
<the_index>, ce=ce@entry=0x80a7c0, st=st@entry=0x7fffffffc7c0, 
options=options@entry=16) at read-cache.c:395
#21 0x00000000004ebcfe in refresh_cache_ent 
(istate=istate@entry=0x7e5fe0 <the_index>, ce=ce@entry=0x80a7c0, 
options=options@entry=16, err=err@entry=0x7fffffffc908,
     changed_ret=changed_ret@entry=0x7fffffffc90c) at read-cache.c:1130
#22 0x00000000004ed59c in refresh_index (istate=0x7e5fe0 <the_index>, 
flags=flags@entry=6, pathspec=pathspec@entry=0x7bb738 <s.25876+24>, 
seen=seen@entry=0x0, header_msg=header_msg@entry=0x0)
     at read-cache.c:1221
#23 0x0000000000429e3b in cmd_status (argc=<optimized out>, 
argv=0x7fffffffcca0, prefix=0x7e950f 
"Ressources/dev/Test.ExportationVTK/") at builtin/commit.c:1376
#24 0x00000000004063b3 in run_builtin (argv=0x7fffffffcca0, argc=1, 
p=0x7b4030 <commands+2352>) at git.c:352
#25 handle_builtin (argc=1, argv=0x7fffffffcca0) at git.c:539
#26 0x00000000004054a1 in run_argv (argv=0x7fffffffca80, 
argcp=0x7fffffffca6c) at git.c:593
#27 main (argc=1, av=<optimized out>) at git.c:698

Ii would have expected git to first gave me an error when checking out the files!!! Here is the log:

Checking out files:  99% (28645/28934)
Checking out files: 100% (28934/28934)
Checking out files: 100% (28934/28934), done.
Already on 'master'
Your branch is up-to-date with 'origin/master'.
     On valide le dépôt TestValidation avec la référence: 
9b4a485202b2b52922377842c15bfd605d240667
HEAD is now at 9b4a485 BUG: On spécifie bash comme shell...
But at least 1 file is corrupted!

I keep preciously this faulty repo to further investigation with someone who can help dig into the coredump and correct it...

I am available to recompile a new git to help...
Thanks,
Eric
Next: Jeff King
Message 1 of 3 in “git status core dump with bad sector!”
  1. Eric ChamberlandApr 14, 2016
  2. Jeff KingApr 22, 2016
  3. Eric ChamberlandMay 4, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.