Error:non-monotonic index after failed recursive "sed" command
- From
- George Karpenkov <george@metaworld.ru>
- Date
- Jan 14, 2013, 11:40 UTC
- Message-ID
- <CAMoGvRKkSZqcoGtiebu6tuPndzOjQ1=JgQHb+iusAHpUbA2HbA@mail.gmail.com>
Hi All,
I've managed to corrupt my very valuable repository with a recursive sed which went wrong. I wanted to convert all tabs to spaces with the following command:
find ./ -name '*.*' -exec sed -i 's/\t/ /g' {} \;I think that has changed not only the files in the repo, but the data files in .git directory itself. As a result, my index became corrupted, and almost every single command dies:
> git log
error: non-monotonic index .git/objects/pack/pack-314b1944adebea645526b6724b2044c1313241f5.idx error: non-monotonic index .git/objects/pack/pack-75c95b0defe1968b61e4f4e1ab7040d35110bfdc.idx ... error: non-monotonic index .git/objects/pack/pack-3da0da48d05140b55f4af1cf87c55a2d7898bdd5.idx fatal: bad object HEAD
Output for git fsck is even worse:
> git fsck
error: non-monotonic index .git/objects/pack/pack-434f8445672a92f123accffce651bdb693bd8fcb.idx ... error: non-monotonic index .git/objects/pack/pack-0c9d5ae4e2b46dd78dace7533adf6cdfe10326ef.idx error: non-monotonic index .git/objects/pack/pack-e8bd5c7f85e96e7e548a62954a8f7c7f223ba9e0.idx Segmentation fault (core dumped)
Any advice? I've lost about 2 weeks worth of work. Is there anything better I can try to do other then trying to reconstruct the data manually from git blobs?