Re: fatal: unable to read <hash>

From: Bjoern A. Zeeb <bzeeb-lists_at_lists.zabbadoz.net>
Date: Wed, 09 Aug 2023 00:31:53 UTC 
On Mon, 7 Aug 2023, Marc Branchaud wrote:

>
> On 2023-08-07 01:18, Bjoern A. Zeeb wrote:
>> 
>> %  git fsck --name-objects --connectivity-only --no-dangling
>> error: b9cdc058e6eb1b3d8b5e29ad9b911d3da98f65a7: invalid sha1 pointer in 
>> resolve-undo of .git/worktrees/bz_maxmodname_D32383/index
>> Checking connectivity: 4743571, done.
>> Verifying commits in commit graph: 100% (384308/384308), done.
>> 
>> The good news upfront;  I could ditch that worktree and branch if that
>> will fix things.  It has follow-up work to the 2021 things but I have
>> a copy of that outside that git tree (I love patch files in port trees :)
>
> If you no longer need the bz_maxmodname_D32383 worktree, then it sounds like 
> the easiest solution would be deleting it -- by running
> 	git worktree remove bz_maxmodname_D32383
> in your "main" repo (which you created with "git clone").
>
> (The bz_maxmodname_D32383 branch seems to be OK, according to fsck.)

And how would one gotten rid of the invalid sha1 pointer in that case?

I removed the worktree and gc now finishes.

% git gc
Enumerating objects: 4743571, done.
Counting objects: 100% (4743571/4743571), done.
Delta compression using up to 40 threads
Compressing objects: 100% (913291/913291), done.
Writing objects: 100% (4743571/4743571), done.
Total 4743571 (delta 3423475), reused 4721415 (delta 3402164), pack-reused 0
Enumerating cruft objects: 38, done.
Traversing cruft objects: 84, done.
Counting objects: 100% (38/38), done.
Delta compression using up to 40 threads
Compressing objects: 100% (28/28), done.
Writing objects: 100% (38/38), done.
Total 38 (delta 10), reused 25 (delta 9), pack-reused 0
Checking connectivity: 4743609, done.
Expanding reachable commits in commit graph: 397393, done.


Thanks a lot for all the support (also Warner).   Much appreciated!

/bz

-- 
Bjoern A. Zeeb                                                     r15:7