summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar xloem <xloem@web>2016-05-18 09:43:13 +0000
committerGravatar admin <admin@branchable.com>2016-05-18 09:43:13 +0000
commit87cf42624a9ae9c0e1a2c5a619ba4bbcfc361230 (patch)
tree7dab62c4925f17f5e3be85b4f13a84c939a235c9
parent428768dcdea9fa5da0a5cba68ee52bcfd0616c37 (diff)
Added a comment
-rw-r--r--doc/bugs/broken_repo_when_inodes_exhausted/comment_2_4c6ced0d3163735c7f4bd5a4a7053159._comment9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/bugs/broken_repo_when_inodes_exhausted/comment_2_4c6ced0d3163735c7f4bd5a4a7053159._comment b/doc/bugs/broken_repo_when_inodes_exhausted/comment_2_4c6ced0d3163735c7f4bd5a4a7053159._comment
new file mode 100644
index 000000000..270968bbc
--- /dev/null
+++ b/doc/bugs/broken_repo_when_inodes_exhausted/comment_2_4c6ced0d3163735c7f4bd5a4a7053159._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="xloem"
+ subject="comment 2"
+ date="2016-05-18T09:43:13Z"
+ content="""
+Thanks. It turns out I'd deleted that repo in order to free the inodes up. Next time I will see if I can repair.
+
+But it would be nice if git-annex tracked inodes the way it tracks free space, so that it could refrain from causing the inode exhaustion. This also would have alerted me to how few inodes I had remaining.
+"""]]