Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Aug 2023 00:31:53 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        Marc Branchaud <marcnarc@gmail.com>
Cc:        git@freebsd.org
Subject:   Re: fatal: unable to read <hash>
Message-ID:  <p98062q2-o266-rp78-52oo-97p8254673q2@yvfgf.mnoonqbm.arg>
In-Reply-To: <ddc5e4c5-a11f-52c8-5347-949f12787a6a@gmail.com>
References:  <orqq0n25-14pq-nn97-o85p-1p6r107s20ns@yvfgf.mnoonqbm.arg> <80c39b3e-9013-22c0-286d-a0ccd05dc21a@gmail.com> <r5oq8n6o-82o7-0q0o-on18-1nso4r35q24r@yvfgf.mnoonqbm.arg> <22663d4f-df74-e343-c182-64705ec59f5b@gmail.com> <qo552875-521o-5364-3sor-3qn06p48op49@yvfgf.mnoonqbm.arg> <ddc5e4c5-a11f-52c8-5347-949f12787a6a@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1098556516-1788126082-1691541115=:24776
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

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
--1098556516-1788126082-1691541115=:24776--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p98062q2-o266-rp78-52oo-97p8254673q2>