From 5a7e76d5c1aee4281a81903c459d778e80bb5e75 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 26 Jul 2021 11:13:12 -0400 Subject: [PATCH] comment --- ..._16_6ef33d110d709e46768549c59b02841a._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_16_6ef33d110d709e46768549c59b02841a._comment diff --git a/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_16_6ef33d110d709e46768549c59b02841a._comment b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_16_6ef33d110d709e46768549c59b02841a._comment new file mode 100644 index 0000000000..60ca23050b --- /dev/null +++ b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_16_6ef33d110d709e46768549c59b02841a._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 16""" + date="2021-07-26T14:21:17Z" + content=""" +You grepped for stats of a file in `tmp` directory but those stats are not +relevant to this problem. Since you ran git-annex get, it should be statting +the annex object file in the remote repository, which I assume is another git +repo on the same computer. (Otherwise it would not be able to fail this way +AFAICS.) It's the stat of that file that's relevant. + +I've added some debugging now, so --debug with a fresh git-annex build +should explain what's going on with the stats. +Use -c annex.debugfilter=Annex.InodeSentinal +to limit debug output to the relevant ones. +"""]]