linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: linux-btrfs@vger.kernel.org, Hugo Mills <hugo@carfax.org.uk>
Subject: [PATCH 0/3] Show Chunks by position
Date: Tue, 22 Nov 2011 20:12:43 -0500	[thread overview]
Message-ID: <4ECC488B.7010406@cfl.rr.com> (raw)
In-Reply-To: <4EC67EAE.2090602@cfl.rr.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/18/2011 10:50 AM, Phillip Susi wrote:
> This is a nice little tool.  The one suggestion that I have is that
> it display the actual chunks and where they are located.  It seems
> that right now it uses the same ioctl that btrfs fi df uses, and that
> just gets the total combined size for all chunks of a given type.  It
> would be nice if the gui actually parsed the chunk tree and showed
> each individual chunk with lines showing how they are mapped to the
> physical disks.

I managed to cobble together the following patches to implement this.
The one thing that I still don't like is that the radio knob is in the
data replication and allocation box, instead of the volumes box.  My
python and tkinter skills are too lacking to figure out how to move it
down there.


Phillip Susi (3):
  Changed volume_df() to return all chunks with their offsets
  Update UsageDisplay to be capable of displaying all chunks by
    position
  Add radio knob to show space by position or combined

 btrfsgui/gui/usagedisplay.py |   98
++++++++++++++++++++++++++++--------------
 btrfsgui/hlp/size.py         |   18 +++----
 2 files changed, 73 insertions(+), 43 deletions(-)

- -- 
1.7.5.4

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7MSIoACgkQJ4UciIs+XuLyjQCeI4m7+u75R863B2RY3hkFELbP
iJ8AoJwzVdiYZqgE1tXvHEOHz+gciDgj
=dfd1
-----END PGP SIGNATURE-----

  reply	other threads:[~2011-11-23  1:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 23:20 Announcing btrfs-gui Hugo Mills
2011-06-02  8:31 ` Fajar A. Nugraha
2011-06-02  8:41   ` Hugo Mills
2011-06-03 21:48     ` Hugo Mills
2011-06-06 15:40 ` Chris Mason
2011-11-12  0:24 ` Amedee Van Gasse
2011-11-23 12:33   ` Hugo Mills
2011-11-23 17:39     ` cwillu
2011-11-18 15:50 ` Phillip Susi
2011-11-23  1:12   ` Phillip Susi [this message]
2011-11-23 12:34     ` [PATCH 0/3] Show Chunks by position Hugo Mills
2011-11-23  1:12   ` [PATCH 1/3] Changed volume_df() to return all chunks with their offsets Phillip Susi
2011-11-23  1:12   ` [PATCH 2/3] Update UsageDisplay to be capable of displaying all chunks by position Phillip Susi
2011-11-23  1:13   ` [PATCH 3/3] Add radio knob to show space by position or combined Phillip Susi

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=4ECC488B.7010406@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=hugo@carfax.org.uk \
    --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).