Re: rsync busy non-bare git repo 'source' to quiet

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

 



On Tue, Mar 08, 2011 at 04:20:33PM -0600, Neal Kreitzinger wrote:

> Rsync seems like a simpler solution and more accurate solution for
> creating a copy of an ecosystem of interrelated git repos colocated on
> the same box.

Sure. It is simpler, but not atomic unless you do a multi-stage rsync.

> A previous post in the newsgroup states:
> > If you want your rsync backup to be fine, you need to follow some
> >ordering.  You need to copy the refs first (.git/packed-refs and
> >.git/refs/), then the loose objects (.git/objects/??/*), and then all
> >the rest.  If files are copied in a different order while some write
> >operations are performed on the source repository then you may end up
> >with an incoherent repository."
> 
> Would that work?

If you do it in that order, the end result will be a consistent repo.
But during the copy, the refs at the destination will point to objects
you don't have. I don't know if that matters for your case.

-Peff
--
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]