From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs Heatmap - v4 ... colors!!
Date: Sat, 14 Jan 2017 20:53:49 +0100 [thread overview]
Message-ID: <33090601-0b56-7360-a256-aa5c27339d99@mendix.com> (raw)
Hi,
I just tagged v4 of the Btrfs Heatmap utility, which visualizes the
usage of your btrfs filesystem:
https://github.com/knorrie/btrfs-heatmap
It needs at least python-btrfs v5 to run, because of the fixed backref
handling.
The main changes are:
* Colors! colors! colors!!!
* Colors!
* Improved documentation, thanks to user feedback. The first README
page does focus on quick satisfaction, while there are two extra
subpages about the extent-level details pictures and a scripting HOWTO
which explains how to do everything that the command line options cannot do.
* The external 2k8 loc png library dependency is dropped, in favour of
a 34 line single purpose png writer implementation directly in the
script itself. This makes it even easier to get the thing going quickly,
and it makes the thing go more quickly as well.
And now, no more text to read. Go and create a bunch of beautiful
pictures and timelapses of your filesystem!
Have fun!
P.S. Here's where it all started... :D
http://logs.tvrrug.org.uk/logs/%23btrfs/2015-12-09.html#2015-12-09T20:54:04
--
Hans van Kranenburg
next reply other threads:[~2017-01-14 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 19:53 Hans van Kranenburg [this message]
[not found] ` <20170118003838.GA4136@comcast.net>
2017-01-19 0:08 ` Btrfs Heatmap - v4 ... colors!! Hans van Kranenburg
2017-02-03 11:25 ` Timofey Titovets
2017-02-03 12:57 ` Hans van Kranenburg
2017-02-03 14:18 ` Timofey Titovets
2017-02-03 14:27 ` Hans van Kranenburg
2017-02-03 14:36 ` Timofey Titovets
2017-02-03 14:46 ` 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=33090601-0b56-7360-a256-aa5c27339d99@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).