linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Chunk fullness distribution
Date: Fri, 21 Aug 2015 18:18:20 +0000 (UTC)	[thread overview]
Message-ID: <pan$3cda0$8efee9f8$3720f4b$2571ee17@cox.net> (raw)
In-Reply-To: CAEp_DRAR5yjYNm-26jfVmajGqoSt3C9P1L5kS+C9s6g=zZhynQ@mail.gmail.com

Bostjan Skufca posted on Fri, 21 Aug 2015 17:49:01 +0200 as excerpted:

> is there a way to get information about how much space is occupied in
> each chunk?
> 
> In the end, a simple ascii chart of usage distribution should be
> preferable, but I can work towards that if there is a way to get
> information about individual chunks.
> 
> I know that "btrfs fi show" displays aggregate info, but having
> distribution chart enables one to predict how much time "btrfs
> rebalance" operation will take for various X values in "dusage=X"
> filter.

AFAIK, no admin-level-user tool to get that information, no.  But doing a 
successive balances while incrementing the -dusage= -musage= counts 
should get you a rough idea (tho it looks like that's what you're trying 
to avoid by asking for the report in the first place), and I believe it's 
findable with the lower-level developer tools, I'd guess btrfs-debug-tree.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-08-21 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 15:49 Chunk fullness distribution Bostjan Skufca
2015-08-21 18:18 ` Duncan [this message]
2015-08-21 21:18   ` Bostjan Skufca
2015-08-25 17:52     ` Bostjan Skufca
2015-08-25 22:41       ` Duncan

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='pan$3cda0$8efee9f8$3720f4b$2571ee17@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).