diff --git a/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_10_a80eccce0bdb33748ab1ccba9b88a65f._comment b/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_10_a80eccce0bdb33748ab1ccba9b88a65f._comment
new file mode 100644
index 0000000000..1275a1d25a
--- /dev/null
+++ b/doc/forum/__34__du__34___equivalent_on_an_annex__63__/comment_10_a80eccce0bdb33748ab1ccba9b88a65f._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="anarcat"
+ avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7"
+ subject="comment 10"
+ date="2020-06-26T20:29:26Z"
+ content="""
+... or even, more fancy:
+
+    git annex info --fast * --json | jq -j '.\"local annex size\", \"\t\", .directory, \"\t\", \"\n\"' | sort -h
+
+Downside: the json output doesn't give us something `sort` can really work with (it expects `M`, `G`, not `mebibytes`, `gibibytes`, which is arguably a bug...). But precision fanatics can also work around that with:
+
+    git annex info --fast * --json --bytes | jq -j '.\"local annex size\", \"\t\", .directory, \"\t\", \"\n\"' | sort -h
+
+Then you can go crazy trying to convert those numbers [back to something readable](https://unix.stackexchange.com/questions/346902/need-to-convert-bytes-to-gb-mb-kb-in-normal-decimal-format) in your own spare time... ;)
+"""]]