From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>,
helmut@hullen.de, Helmut Hullen <Hullen@t-online.de>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs balancing start - and stop?
Date: Fri, 01 Apr 2011 17:24:32 +0300 [thread overview]
Message-ID: <4D95E020.7030905@gmail.com> (raw)
In-Reply-To: <20110401133736.GB2984@carfax.org.uk>
On 1/4/2011 4:37 =CE=BC=CE=BC, Hugo Mills wrote:
> On Fri, Apr 01, 2011 at 04:22:39PM +0300, Konstantinos Skarlatos wrot=
e:
>> On 1/4/2011 3:12 =CE=BC=CE=BC, Helmut Hullen wrote:
>>> Du meintest am 01.04.11:
>>>
>>> "dmesg" counts down the number of remaining "jobs".
>> are you sure? here is a snippet of dmesg from a balance i did
>> yesterday (2.6.38.1)
>>
>> btrfs: relocating block group 15338569728 flags 9
>> btrfs: found 17296 extents
>> btrfs: found 17296 extents
>> btrfs: relocating block group 13191086080 flags 9
>> btrfs: found 21029 extents
>> btrfs: found 21029 extents
>> btrfs: relocating block group 11043602432 flags 9
>> btrfs: found 4728 extents
>> btrfs: found 4728 extents
> Count the number of block groups in the system (1GiB for data,
> 256MiB for metdata on a typical filesystem), and subtract the number
> of "relocating block group" messages... Not ideal, but it's possible.
>
> The balance cancel patch I mentioned earlier also supplies an
> additional patch for monitoring progress, which does show up in the
> dmesg output (as well as user-space support for prettier output).
Great, I think it is very important to have a human-readable progress=20
monitor for operations like that.
> Hugo.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-01 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 11:14 btrfs balancing start - and stop? Struan Bartlett
2011-04-01 11:59 ` Hugo Mills
2011-04-05 16:06 ` Struan Bartlett
2011-04-01 12:12 ` Helmut Hullen
2011-04-01 13:22 ` Konstantinos Skarlatos
2011-04-01 13:36 ` Helmut Hullen
2011-04-01 13:52 ` Hugo Mills
[not found] ` <20110401133736.GB2984@carfax.org.uk>
2011-04-01 14:24 ` Konstantinos Skarlatos [this message]
2011-04-01 18:33 ` Stephane Chazelas
2011-04-01 19:26 ` Helmut Hullen
2011-04-03 18:53 ` Stephane Chazelas
2011-04-03 19:35 ` Helmut Hullen
2011-04-04 19:07 ` Stephane Chazelas
2011-04-06 11:43 ` Stephane Chazelas
2011-04-11 8:42 ` Stephane Chazelas
2011-04-11 9:14 ` Helmut Hullen
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=4D95E020.7030905@gmail.com \
--to=k.skarlatos@gmail.com \
--cc=Hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=hugo-lkml@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 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.