git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: rsync a *bunch* of git repos

From
SRSeth Robertson <in-gitvger@baka.org>
Date
Jan 10, 2012, 21:24 UTC
Message-ID
<201201102124.q0ALOowL026941@no.baka.org>
In-Reply-To
<20120110211548.GD10255@titan.lakedaemon.net>
In message <20120110211548.GD10255@titan.lakedaemon.net>, Jason writes:
    The nuts and bolts of this aren't difficult, the problem is I don't have
    a complete understanding of how git stores data.  I've heard in the
    past that it uses a lot of hardlinks and softlinks.  I need to make
    sure, that once I transfer the data, and reboot the machine with the new
    partition mounted under /home, that all my git repos will be okay.

Under most circumstances, git will do the right thing. Only if you use specific flags on clone (like --shared or --reference) might something go wrong, and as the manual page explains, you can use git-repack to undo these.

The real solution is, after you rsync, to:
for f in */.git; do (cd $f; git fsck >&/dev/null || echo "$f is BAD!!"); done

If you get no output, you should be golden. If you get output, check to make sure the repo you are copying from is good as well.

					-Seth Robertson
Previous: JasonNext: Philip Oakley
Message 2 of 8 in “rsync a *bunch* of git repos”
  1. JasonJan 10, 2012
  2. Seth RobertsonJan 10, 2012
  3. Philip OakleyJan 10, 2012
  4. Junio C HamanoJan 10, 2012
  5. SergioJan 11, 2012
  6. Neal KreitzingerJan 11, 2012
  7. JasonJan 24, 2012
  8. Andreas T.AuerJan 11, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.