support .git/annex on a different disk than the rest of the repo

The only fully supported thing is to have the main repository on one disk,
and .git/annex on another. Only commands that move data in/out of the annex
will need to copy it across devices.

There is only partial support for putting arbitrary subdirectories of
.git/annex on different devices. For one thing, but this can require more
copies to be done. For example, when .git/annex/tmp is on one device, and
.git/annex/journal on another, every journal write involves a call to
mv(1). Also, there are a few places that make hard links between various
subdirectories of .git/annex with createLink, that are not handled.

In the common case without cross-device, the new moveFile is actually
faster than renameFile, avoiding an unncessary stat to check that a file
(not a directory) is being moved. Of course if a cross-device move is
needed, it is as slow as mv(1) of the data.
This commit is contained in:
Joey Hess 2011-11-28 15:26:27 -04:00
parent ff2d9c8283
commit 6869e6023e
9 changed files with 81 additions and 11 deletions

2
debian/changelog vendored
View file

@ -6,6 +6,8 @@ git-annex (3.20111123) UNRELEASED; urgency=low
doubled output.
* Avoid needing haskell98 and other fixes for new ghc. Thanks, Mark Wright.
* Bugfix: dropunused did not drop keys with two spaces in their name.
* Support for storing .git/annex on a different device than the rest of the
git repository.
-- Joey Hess <joeyh@debian.org> Tue, 22 Nov 2011 17:53:42 -0400