diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-22 15:08:27 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-22 15:08:27 -0400 |
| commit | f997fada7c4f2ec2cf37c02fbc46c9efc40fe6a2 (patch) | |
| tree | 8ddc652c8ce141c4ed5132ed46ed3a597631f527 | |
| parent | 58da8089e614ad73b8e2b69a701b2cea620af56b (diff) | |
| parent | 27ec4c23a7aa657a7df6b27d29d9675bcf0e9f9a (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/bugs/Continual_space_exhaustion_from_syncing_metadata.mdwn | 26 | ||||
| -rw-r--r-- | doc/devblog/day_392__v6_fixes/comment_3_74e696f147f80162a941a5a5435327ce._comment | 7 |
2 files changed, 33 insertions, 0 deletions
diff --git a/doc/bugs/Continual_space_exhaustion_from_syncing_metadata.mdwn b/doc/bugs/Continual_space_exhaustion_from_syncing_metadata.mdwn new file mode 100644 index 000000000..ca826fb7f --- /dev/null +++ b/doc/bugs/Continual_space_exhaustion_from_syncing_metadata.mdwn @@ -0,0 +1,26 @@ +### Please describe the problem. +When the preferred content for a repo is greater than the free space on the drive for me, the space becomes exhausted due to upload that occurs during syncing -- the git history ends up exhausting the space. The result for me has been corrupted repos with broken refs and heads. + +I think it would be better if the git syncing process respected the same space limitations that the content syncing does, and did not push if space was exhausted on the destination, nor pull if space exhausted locally. + +### What steps will reproduce the problem? +Make enough git commits that it exhausts the free space on some repo. + +### What version of git-annex are you using? On what operating system? +I've been using a few different versions; right now I am using 6.2016-0511 and 6.2016-0517-g766728c +but I have not tested this issue with these most recent versions. I am still trying to get my smaller repos back together. + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +Yes !!! I'm moving all my files into my annex. It is very robust; whenever something is wrong there is always some other copy somewhere that can be used. + diff --git a/doc/devblog/day_392__v6_fixes/comment_3_74e696f147f80162a941a5a5435327ce._comment b/doc/devblog/day_392__v6_fixes/comment_3_74e696f147f80162a941a5a5435327ce._comment new file mode 100644 index 000000000..e331dd879 --- /dev/null +++ b/doc/devblog/day_392__v6_fixes/comment_3_74e696f147f80162a941a5a5435327ce._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="xloem" + subject="comment 3" + date="2016-05-22T15:58:22Z" + content=""" +Thanks. +"""]] |