[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Read error from 'delta' in Git for staging

From: James
Subject: Read error from 'delta' in Git for staging
Date: Sun, 15 Apr 2012 22:31:33 +0100


I've noticed an problem on my git when I tried to checkout staging and
then git pull -r.

address@hidden:~/lilypond-git$ git status
# On branch master
nothing to commit (working directory clean)
address@hidden:~/lilypond-git$ git checkout staging
error: failed to read object d3eee73c6d278425bcf694c7bf221dc334bd2a5f
at offset 434935 from
Switched to branch 'staging'
Your branch is behind 'origin/staging' by 9 commits, and can be fast-forwarded.
address@hidden:~/lilypond-git$ git pull -r
First, rewinding head to replay your work on top of it...
error: failed to read delta base object
d3eee73c6d278425bcf694c7bf221dc334bd2a5f at offset 434935 from
Fast-forwarded staging to f1defa51a982cf769172cfcdd6b2612608ba2746.
address@hidden:~/lilypond-git$ gitk
address@hidden:~/lilypond-git$ lily-git.tcl
address@hidden:~/lilypond-git$ git branch
* staging
address@hidden:~/lilypond-git$ git pull -r
Current branch staging is up to date.

As you can see if I keep doing a git pull -r the error 'goes away'.

This is my patchy VM but I get no physical device (disk read errors)
either on the VM or the underlying host.

As Master and Staging are both on the same commit and because read
errors are always worrying (especially to someone who works in the
Storage Industry),

Perhaps this is overkill, but there isn't anything urgent on, and I
have backups of this VM - if anyone wants me to do 'stuff' on this
install - I'm going to blow my complete VM away, reinstall LilyDev and
download $LILYPOND_GIT from scratch.

This will take an hour or so on my connection, so Patchy merge won't
run until I get up tomorrow morning.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]