All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] git packfile
Date: Mon, 25 Mar 2019 04:50:58 +0000	[thread overview]
Message-ID: <61FFBC77-CF2E-4EDC-9060-BF9EBF7B27D0@whamcloud.com> (raw)
In-Reply-To: <30534141-20CF-43C3-BA49-0149AF7CEFE6@cray.com>

On Mar 22, 2019, at 09:59, Cory Spitz <spitzcor@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

  reply	other threads:[~2019-03-25  4:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 15:59 [lustre-devel] git packfile Cory Spitz
2019-03-25  4:50 ` Andreas Dilger [this message]
2019-03-25  9:47   ` Degremont, Aurelien
2019-03-25 10:02     ` Andreas Dilger
2019-03-25 17:22       ` Degremont, Aurelien
2019-03-26  3:17         ` Cory Spitz
2019-03-26 11:23           ` Andreas Dilger
2019-03-26 12:48             ` Degremont, Aurelien
2019-03-26 21:32               ` Andreas Dilger
2020-07-24 21:47           ` Spitz, Cory James
2020-08-21  4:22             ` Spitz, Cory James
2020-08-21 21:51               ` Shaun Tancheff
2020-08-29 11:23                 ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61FFBC77-CF2E-4EDC-9060-BF9EBF7B27D0@whamcloud.com \
    --to=adilger@whamcloud.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.