summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c <Justin@web>2014-03-05 06:34:28 +0000
committerGravatar admin <admin@branchable.com>2014-03-05 06:34:28 +0000
commit92baf256c6c20b9f6c7009bfb329cf7095235c7a (patch)
tree078701f479f41d1c11fe5c56d3bd5e5f104fc47a
parente4e4ad89031623cbc33e5e30e9f55b315dcbc28e (diff)
-rw-r--r--doc/forum/copy_fails_for_some_fails_without_explanation.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/copy_fails_for_some_fails_without_explanation.mdwn b/doc/forum/copy_fails_for_some_fails_without_explanation.mdwn
new file mode 100644
index 000000000..d4bcbf08c
--- /dev/null
+++ b/doc/forum/copy_fails_for_some_fails_without_explanation.mdwn
@@ -0,0 +1,5 @@
+I have a large direct-mode repository whose files I'm trying to copy to a non-direct-mode repository. Both repositories live on an HDD attached to an rpi.
+
+When I do $ git annex copy --to pi dirs/to/copy, the copy starts out OK, but eventually many files fail to copy. The only diagnostic I get is "failed". Judging from the backscroll, I don't see a strong pattern to the files which fail to copy; they're kind of interspersed amongst files which were successfully copied. If I try to copy one of these failed files explicitly (git annex copy --to pi file/which/failed), this succeeds. I have plenty of free space on the disk.
+
+Is there a way to get more diagnostics out of git annex so I can see why these files are failing to copy?