From c31b6c01eed83feafa8b6525b32d9e08083e5dcd Mon Sep 17 00:00:00 2001 From: xloem Date: Sun, 22 May 2016 15:58:22 +0000 Subject: [PATCH 1/4] Added a comment --- .../comment_3_74e696f147f80162a941a5a5435327ce._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/devblog/day_392__v6_fixes/comment_3_74e696f147f80162a941a5a5435327ce._comment 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 0000000000..e331dd8792 --- /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. +"""]] From 79d335c8069bccfac39fb080b6a0bca3ee9ea9ab Mon Sep 17 00:00:00 2001 From: xloem Date: Sun, 22 May 2016 16:26:30 +0000 Subject: [PATCH 2/4] Added a comment: This could be detected --- .../comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment diff --git a/doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment b/doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment new file mode 100644 index 0000000000..eed705fc5a --- /dev/null +++ b/doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="xloem" + subject="This could be detected" + date="2016-05-22T16:26:29Z" + content=""" +Git-annex could detect this by attempting to write a 1-byte file. +"""]] From 8a95bb14bcb28898f855d8496c1a8c28210444e8 Mon Sep 17 00:00:00 2001 From: xloem Date: Sun, 22 May 2016 16:26:56 +0000 Subject: [PATCH 3/4] removed --- .../comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment | 7 ------- 1 file changed, 7 deletions(-) delete mode 100644 doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment diff --git a/doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment b/doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment deleted file mode 100644 index eed705fc5a..0000000000 --- a/doc/bugs/Low_disk_space_corrupts_state/comment_3_d31841c77aef8ef7c9cd8a061c66eca8._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="xloem" - subject="This could be detected" - date="2016-05-22T16:26:29Z" - content=""" -Git-annex could detect this by attempting to write a 1-byte file. -"""]] From a207886237f3558004fe798a059644a495e13a4e Mon Sep 17 00:00:00 2001 From: xloem Date: Sun, 22 May 2016 17:09:49 +0000 Subject: [PATCH 4/4] --- ...pace_exhaustion_from_syncing_metadata.mdwn | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/bugs/Continual_space_exhaustion_from_syncing_metadata.mdwn 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 0000000000..ca826fb7fb --- /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. +