From 9bed63c237e35fae2708e6d0b9d3c00de4b46bf6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 29 Sep 2015 11:40:14 -0400 Subject: comment --- .../comment_1_04718e5f87a7e0521a3165bc9fc951a8._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/monitoring_disk_usage_by_different_repos_on_same_drive/comment_1_04718e5f87a7e0521a3165bc9fc951a8._comment diff --git a/doc/forum/monitoring_disk_usage_by_different_repos_on_same_drive/comment_1_04718e5f87a7e0521a3165bc9fc951a8._comment b/doc/forum/monitoring_disk_usage_by_different_repos_on_same_drive/comment_1_04718e5f87a7e0521a3165bc9fc951a8._comment new file mode 100644 index 000000000..17ad19403 --- /dev/null +++ b/doc/forum/monitoring_disk_usage_by_different_repos_on_same_drive/comment_1_04718e5f87a7e0521a3165bc9fc951a8._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-09-29T15:34:08Z" + content=""" +If you go to one of the repos and run `git annex info --json --bytes` +you'll get a json object that has keys including "local annex size". +You can extract that value, and feed it into a graphing engine, such +as graphite, or whatever to generate graphs of the repo sizes over time. + +(Of course, you could do the same thing with `du`) +"""]] -- cgit v1.2.3