From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs Heatmap - visualize your filesystem
Date: Sun, 13 Nov 2016 00:19:21 +0100 [thread overview]
Message-ID: <e69c35cc-d693-da18-5aba-e78ae42262cd@mendix.com> (raw)
Hi,
It seems I never mailed the list yet about a fun little tool to
visualize the space usage of a btrfs filesystem:
https://github.com/knorrie/btrfs-heatmap
It needs python-btrfs to query a btrfs filesystem for block group usage
and pypng to generate an image showing disk space usage as some kind of
heatmap.
More info is in the README inside the project.
The Hilbert curve might seem a little weird at first, but I haven't seen
a better way of visualization that keeps providing useful information
about locality for larger filesystems.
Today on IRC naptastic shared a timelapse video of using btrfs balance
after adding 2 disks to a filesystem:
20:30 < naptastic> https://youtu.be/AA5gvsRtLgI
20:30 < naptastic> Enjoy!
Oh, and if someone is bored... What about creating an ncurses frontend
for fun, that looks like this, while you're waiting on btrfs balance to
complete... https://hblok.net/blog_pics/nsd.png
Quote of the day:
01:09 < kdave> watching speeddisk was a computer game substitute of my youth
P.S. This program also shows how convenient it is to build something
else on top of python-btrfs... The lines that are really needed to get
all information about the filesystem can be counted on two hands. :)
Moo!
Knorrie
next reply other threads:[~2016-11-12 23:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 23:19 Hans van Kranenburg [this message]
2016-11-16 20:30 ` Btrfs Heatmap - v2 - block group internals! Hans van Kranenburg
2016-11-17 1:27 ` Qu Wenruo
2016-11-17 18:51 ` Hans van Kranenburg
2016-11-17 19:27 ` Austin S. Hemmelgarn
2016-11-17 21:08 ` Hans van Kranenburg
2016-11-18 12:36 ` Austin S. Hemmelgarn
2016-11-18 14:37 ` Hans van Kranenburg
2016-11-18 15:33 ` Austin S. Hemmelgarn
2016-11-18 2:08 ` Qu Wenruo
2016-11-18 15:08 ` Hans van Kranenburg
2016-11-18 15:30 ` Austin S. Hemmelgarn
2016-11-18 16:18 ` Hans van Kranenburg
2016-11-19 0:57 ` Qu Wenruo
2016-11-19 1:38 ` Hans van Kranenburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e69c35cc-d693-da18-5aba-e78ae42262cd@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.