Re: Bad objects error since upgrading GitHub servers to 1.6.1

From: Björn Steinbrink <b.steinbrink@gmx.de>
Date: Jan 28, 2009, 01:15 UTC
Message-ID: <20090128011551.GB7503@atjola.homenet>
In-Reply-To: <alpine.LFD.2.00.0901271655090.3123@localhost.localdomain>

On 2009.01.27 17:00:54 -0800, Linus Torvalds wrote:

Show 17 quoted lines

> 
> 
> On Tue, 27 Jan 2009, PJ Hyett wrote:
> > 
> > ~/Development/github(jetty)$ git fsck --full
> > warning in tree 0d640d99b492b0c7db034e92d0460a7f84b22356: contains zero-padded file modes
> > ..
> 
> Ouch. This is unrelated to your issue, but I'm wondering what project 
> contains these invalid trees, and how they were created.
> 
> Zero-padded tree entries can cause "object aliases", ie two trees that 
> have logically the same contents end up with different data (due to 
> different amounts of padding) and thus different SHA1's. It shouldn't be 
> serious per se, but it's somethign that really shouldn't happen.
> 
> What project does it come from, and how did such a tree get generated?

I guess that's still from their webinterface that allows to edit file directly, without having a clone ofthe repo. The initial(?) version used to create such broken objects. It also got the order of entries in a tree object wrong IIRC. Back then, Scott and myself tracked that down on #git, to their ruby(?) stuff that creates the objects. But maybe the breakage is back?

Björn