From d4fc506f2704f7db61fb8d291a7b2e4f35a4ec58 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 29 Jul 2021 13:33:11 -0400 Subject: [PATCH] comment --- ..._503d0507c55412ca8c625b32feb7f80e._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_23_503d0507c55412ca8c625b32feb7f80e._comment diff --git a/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_23_503d0507c55412ca8c625b32feb7f80e._comment b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_23_503d0507c55412ca8c625b32feb7f80e._comment new file mode 100644 index 0000000000..c612752e1b --- /dev/null +++ b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_23_503d0507c55412ca8c625b32feb7f80e._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 23""" + date="2021-07-29T16:30:46Z" + content=""" +There are probably multiple causes. v8 upgrade does seem likely to be the +main one, but I see that adswa seems to have found a way to reproduce it from +scratch: + +It's looking like perhaps inode instability in their case, due to use +of a networked filesystem in a cluster. + +I have done some detailed auditing, and I'm pretty sure git-annex doesn't +just forget to record the inode in some case. Well, except for potentially +one case involving git-annex lock and annex.thin, which I fixed but was not +able to actually quite get to reproduce the problem. + +(I did find a some potential races, that would cause other problems but not +this one, so the auditing was good for something..) +"""]]