From: Hugo Mills <hugo@carfax.org.uk>
To: linux-btrfs@vger.kernel.org
Subject: [patch 0/2] Control filesystem balances (userspace)
Date: Sat, 30 Oct 2010 01:10:22 +0100 [thread overview]
Message-ID: <20101030001022.247934404@carfax.org.uk> (raw)
These two patches complement the previous two kernel-side
patches. The first implements a way of displaying the current progress
of any running balance process. The second patch allows a running
balance to be cancelled.
I'm a bit uncertain about the best name for these commands. Several
options:
1)
# btrfs filesystem progress <path>
# btrfs filesystem cancel <path>
Way too vague (cancel *what*?)
2)
# btrfs filesystem balance-progress <path>
# btrfs filesystem balance-cancel <path>
Clashes horribly with "filesystem balance" -- no abbreviations
possible.
3)
btrfs filesystem balance -p <path>
btrfs filesystem balance -c <path>
Changes behaviour significantly on a switch, in contrast to the
behaviour of the rest of the btrfs tool.
4)
btrfs balance progress <path>
btrfs balance cancel <path>
My current favourite, although we introduce a new namespace
("balance") for commands. We could add "btrfs balance start <path>" as
a synonym for "btrfs filesystem balance <path>", for some degree of
consistency.
At some point, I'll add a "monitor" function, which will poll at 1s
intervals for progress updates, and print out progress when it changes.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- "No! My collection of rare, incurable diseases! Violated!" ---
next reply other threads:[~2010-10-30 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 0:10 Hugo Mills [this message]
2010-10-30 0:10 ` [patch 1/2] Balance progress monitoring Hugo Mills
2010-10-30 0:10 ` [patch 2/2] User-space tool for cancelling balance operations Hugo Mills
2010-10-30 0:30 ` [patch 0/2] Control filesystem balances (userspace) Jérôme Poulin
2010-10-30 17:49 ` Goffredo Baroncelli
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=20101030001022.247934404@carfax.org.uk \
--to=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).