From: Dmitry Katsubo <dma_k@mail.ru>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is "btrfs balance start" truly asynchronous?
Date: Wed, 22 Jun 2016 01:30:54 +0200 [thread overview]
Message-ID: <5769CE2E.2000306@mail.ru> (raw)
In-Reply-To: <57693E72.1090706@cobb.uk.net>
On 2016-06-21 15:17, Graham Cobb wrote:
> On 21/06/16 12:51, Austin S. Hemmelgarn wrote:
>> The scrub design works, but the whole state file thing has some rather
>> irritating side effects and other implications, and developed out of
>> requirements that aren't present for balance (it might be nice to check
>> how many chunks actually got balanced after the fact, but it's not
>> absolutely necessary).
>
> Actually, that would be **really** useful. I have been experimenting
> with cancelling balances after a certain time (as part of my
> "balance-slowly" script). I have got it working, just using bash
> scripting, but it means my script does not know whether any work has
> actually been done by the balance run which was cancelled (if no work
> was done, but it timed out anyway, there is probably no point trying
> again with the same timeout later!).
Additionally it would be nice if balance/scrub reports the status via
/proc in human readable manner (similar to /proc/mdstat).
--
With best regards,
Dmitry
next prev parent reply other threads:[~2016-06-21 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 16:33 Is "btrfs balance start" truly asynchronous? Dmitry Katsubo
2016-06-21 8:55 ` Duncan
2016-06-21 11:24 ` Austin S. Hemmelgarn
2016-06-21 11:33 ` Hugo Mills
2016-06-21 11:51 ` Austin S. Hemmelgarn
2016-06-21 13:17 ` Graham Cobb
2016-06-21 13:44 ` Lionel Bouton
2016-06-21 23:30 ` Dmitry Katsubo [this message]
2016-06-21 12:19 ` Zygo Blaxell
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=5769CE2E.2000306@mail.ru \
--to=dma_k@mail.ru \
--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).