From 87cf42624a9ae9c0e1a2c5a619ba4bbcfc361230 Mon Sep 17 00:00:00 2001 From: xloem Date: Wed, 18 May 2016 09:43:13 +0000 Subject: Added a comment --- .../comment_2_4c6ced0d3163735c7f4bd5a4a7053159._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/broken_repo_when_inodes_exhausted/comment_2_4c6ced0d3163735c7f4bd5a4a7053159._comment 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. +"""]] -- cgit v1.2.3