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.
2011-11-28 19:26:27 +00:00
|
|
|
{- directory manipulation
|
|
|
|
-
|
|
|
|
- Copyright 2011 Joey Hess <joey@kitenet.net>
|
|
|
|
-
|
|
|
|
- Licensed under the GNU GPL version 3 or higher.
|
|
|
|
-}
|
|
|
|
|
|
|
|
module Utility.Directory where
|
|
|
|
|
|
|
|
import System.IO.Error
|
|
|
|
import System.Posix.Files
|
|
|
|
import System.Directory
|
|
|
|
import Control.Exception (throw)
|
2011-12-09 05:57:13 +00:00
|
|
|
import Control.Monad
|
2012-01-24 19:28:13 +00:00
|
|
|
import Control.Monad.IfElse
|
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.
2011-11-28 19:26:27 +00:00
|
|
|
|
|
|
|
import Utility.SafeCommand
|
|
|
|
import Utility.TempFile
|
2012-02-03 20:47:24 +00:00
|
|
|
import Utility.Exception
|
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.
2011-11-28 19:26:27 +00:00
|
|
|
|
|
|
|
{- Moves one filename to another.
|
|
|
|
- First tries a rename, but falls back to moving across devices if needed. -}
|
|
|
|
moveFile :: FilePath -> FilePath -> IO ()
|
2012-02-03 20:47:24 +00:00
|
|
|
moveFile src dest = tryIO (rename src dest) >>= onrename
|
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.
2011-11-28 19:26:27 +00:00
|
|
|
where
|
|
|
|
onrename (Right _) = return ()
|
|
|
|
onrename (Left e)
|
|
|
|
| isPermissionError e = rethrow
|
|
|
|
| isDoesNotExistError e = rethrow
|
|
|
|
| otherwise = do
|
|
|
|
-- copyFile is likely not as optimised as
|
|
|
|
-- the mv command, so we'll use the latter.
|
|
|
|
-- But, mv will move into a directory if
|
|
|
|
-- dest is one, which is not desired.
|
|
|
|
whenM (isdir dest) rethrow
|
|
|
|
viaTmp mv dest undefined
|
|
|
|
where
|
|
|
|
rethrow = throw e
|
|
|
|
mv tmp _ = do
|
|
|
|
ok <- boolSystem "mv" [Param "-f",
|
|
|
|
Param src, Param tmp]
|
2011-12-09 05:57:13 +00:00
|
|
|
unless ok $ do
|
|
|
|
-- delete any partial
|
2012-02-03 20:47:24 +00:00
|
|
|
_ <- tryIO $ removeFile tmp
|
2011-12-09 05:57:13 +00:00
|
|
|
rethrow
|
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.
2011-11-28 19:26:27 +00:00
|
|
|
isdir f = do
|
2012-02-03 20:47:24 +00:00
|
|
|
r <- tryIO $ getFileStatus f
|
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.
2011-11-28 19:26:27 +00:00
|
|
|
case r of
|
|
|
|
(Left _) -> return False
|
|
|
|
(Right s) -> return $ isDirectory s
|