[lustre-devel] git packfile

[Andreas Dilger]

On Mar 25, 2019, at 03:47, Degremont, Aurelien <degremoa at amazon.com> wrote:
> 
> I'm facing similar problem than Cory, times to times.
> I did not track the detailed error messages but, for example, here are the errors I got when running 'git fetch' on a directory where only git://git.whamcloud.com/fs/lustre-release.git is declared. I did not update the repo for few days/weeks.
> 
> remote: warning: packfile ./objects/pack/pack-2b5d1356632dfdbfd86c2d36e529a0a8af47f9af.pack cannot be accessed
> remote: error: refs/changes/47/33547/4 does not point to a valid object!
> remote: warning: packfile ./objects/pack/pack-d2307b0367688a7b6599e36453a20e02d6a0302e.pack cannot be accessed
> remote: error: refs/changes/47/33547/5 does not point to a valid object!
> remote: warning: packfile ./objects/pack/pack-69f40cb9d10db9a97f6df59c80a6279f808b9d5d.pack cannot be accessed
> remote: error: refs/changes/47/33547/6 does not point to a valid object!
> remote: warning: packfile ./objects/pack/pack-090b03d5723083bb4a1e7b524bc83dc9de504f17.pack cannot be accessed
> remote: error: refs/changes/47/33547/7 does not point to a valid object!
> remote: warning: packfile ./objects/pack/pack-0397e40c8813c5601975c99c94afed5ddfbbf1dc.pack cannot be accessed
> remote: error: refs/changes/47/33547/8 does not point to a valid object!
> remote: warning: packfile ./objects/pack/pack-a20995b7160fa2708c42f05111b39126a96b9bd4.pack cannot be accessed
> remote: warning: packfile ./objects/pack/pack-765a1f16499228e6910765c218733cfb8852e953.pack cannot be accessed
> 
> This problem started few months ago.

If you do a fetch on the same tree again right away does the error persist or go away?

Cheers, Andreas

> Le 25/03/2019 07:05, « lustre-devel au nom de Andreas Dilger » <lustre-devel-bounces at lists.lustre.org au nom de adilger at whamcloud.com> a écrit :
> 
>    On Mar 22, 2019, at 09:59, Cory Spitz <spitzcor at cray.com> wrote:
>> 
>> Hello.
>> 
>> I’ve occasionally seen errors like the following when pulling upstream master:
>> 
>> remote: warning: packfile ./objects/pack/pack-8a0ac446942c02bf656a79a2d7fa79d33f1fa4e2.pack cannot be accessed        
>> remote: error: refs/changes/47/5347/9 does not point to a valid object!        
>> remote: warning: packfile ./objects/pack/pack-8a0ac446942c02bf656a79a2d7fa79d33f1fa4e2.pack cannot be accessed        
>> remote: error: refs/changes/47/7247/23 does not point to a valid object!        
>> remote: warning: packfile ./objects/pack/pack-8a0ac446942c02bf656a79a2d7fa79d33f1fa4e2.pack cannot be accessed        
>> remote: error: refs/changes/47/7747/14 does not point to a valid object!        
>> remote: warning: packfile ./objects/pack/pack-8a0ac446942c02bf656a79a2d7fa79d33f1fa4e2.pack cannot be accessed     
>> 
>> Other clones/checkouts seem to be OK.  Has anyone else seen this?  It seems that this has something to do with Gerrit changes.  I just did a clone of master and I never set things up to my knowledge to pull all of these refs.  Anyone have a workaround (besides a fresh clone) or any tips?
> 
>    Cory, does this happen repeatedly, or just one time?  There are definitely errors that are generated because the master-next branch is "rewound" every time that Oleg lands those patches to master.
> 
>    It is a bit strange about the changes that are referenced above.  https://review.whamcloud.com/7247 and https://review.whamcloud.com/5347 were landed 5 years ago, so it is unlikely that anything related to them was changed recently.  Looking at the changes in Gerrit they appear to be OK.
> 
>    Cheers, Andreas
>    ---
>    Andreas Dilger
>    Principal Lustre Architect
>    Whamcloud
> 
> 
> 
> 
> 
> 
> 
>    _______________________________________________
>    lustre-devel mailing list
>    lustre-devel at lists.lustre.org
>    http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
> 
> 

Cheers, Andreas
---
Andreas Dilger
Principal Lustre Architect
Whamcloud