Re: Recovering from repository corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 10 Jun 2008, Denis Bueno wrote:

> However:
> 
> identity.fb[173] > git fsck --full
>     error: 320bd6e82267b71dd2ca7043ea3f61dbbca16109: object corrupt or missing
>     error: 4d0be2816d5eea5ae2b40990235e2225c1715927: object corrupt or missing
>     missing blob 320bd6e82267b71dd2ca7043ea3f61dbbca16109
>     missing blob 4d0be2816d5eea5ae2b40990235e2225c1715927
> 
> Shouldn't these be unreferenced now that I've run filter-branch?

Try to clone this repository (using file:/// pseudo-protocol to force
transfer of objects instead of hardlinking them), and chek if the
problem persists in the clone too.  If not, error/missing might be
in "garbage".

But I'm not sure...
-- 
Jakub Narebski
Poland
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux