From: Josef Bacik <josef@toxicpanda.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Balance vs device add fixes
Date: Tue, 2 Nov 2021 10:30:44 -0400 [thread overview]
Message-ID: <YYFLlL4NTF4L+PmE@localhost.localdomain> (raw)
In-Reply-To: <20211101115324.374076-1-nborisov@suse.com>
On Mon, Nov 01, 2021 at 01:53:21PM +0200, Nikolay Borisov wrote:
> This series enables adding of a device when balance is paused (i.e an fs is mounted
> with skip_balance options). This is needed to give users a chance to gracefully
> handle an ENOSPC situation in the face of running balance. To achieve this introduce
> a new exclop - BALANCE_PAUSED which is made compatible with device add. More
> details in each patche.
>
> I've tested this with an fstests which I will be posting in a bit.
>
> Nikolay Borisov (3):
> btrfs: introduce BTRFS_EXCLOP_BALANCE_PAUSED exclusive state
> btrfs: make device add compatible with paused balance in
> btrfs_exclop_start_try_lock
> btrfs: allow device add if balance is paused
>
> fs/btrfs/ctree.h | 1 +
> fs/btrfs/ioctl.c | 49 +++++++++++++++++++++++++++++++++++++++-------
> fs/btrfs/volumes.c | 23 ++++++++++++++++++----
> fs/btrfs/volumes.h | 2 +-
> 4 files changed, 63 insertions(+), 12 deletions(-)
>
A few things
1) Can we integrate the flipping into helpers? Something like
btrfs_exclop_change_state(PAUSED);
So the locking and stuff is all with the code that messes with the exclop?
2) The existing helpers do WRITE_ONCE(), is that needed here? I assume not
because we're not actually exiting our exclop state, but still seems wonky.
3) Maybe have an __btrfs_exclop_finish(type), so instead of
if (paused) {
do thing;
} else {
btrfs_exclop_finish();
}
you can instead do
type = BTRFS_EXCLOP_NONE;
if (pause stuff) {
do things;
type = BTRFS_EXCLOP_BALANCE_PAUSED;
}
/* other stuff. */
__btrfs_exclop_finish(type);
then btrfs_exclop_finish just does __btrfs_exclop_finish(NONE);
Thanks,
Josef
next prev parent reply other threads:[~2021-11-02 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 11:53 [PATCH 0/3] Balance vs device add fixes Nikolay Borisov
2021-11-01 11:53 ` [PATCH 1/3] btrfs: introduce BTRFS_EXCLOP_BALANCE_PAUSED exclusive state Nikolay Borisov
2021-11-01 11:53 ` [PATCH 2/3] btrfs: make device add compatible with paused balance in btrfs_exclop_start_try_lock Nikolay Borisov
2021-11-01 11:53 ` [PATCH 3/3] btrfs: allow device add if balance is paused Nikolay Borisov
2021-11-02 4:52 ` [PATCH 0/3] Balance vs device add fixes Anand Jain
2021-11-02 13:12 ` Josef Bacik
2021-11-02 14:30 ` Josef Bacik [this message]
2021-11-02 15:25 ` Nikolay Borisov
2021-11-02 16:10 ` Josef Bacik
2021-11-02 17:25 ` Goldwyn Rodrigues
2021-11-02 17:39 ` Nikolay Borisov
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=YYFLlL4NTF4L+PmE@localhost.localdomain \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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