linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
	David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix a bogus warning when converting only data or metadata
Date: Tue, 7 Mar 2017 12:34:07 -0800	[thread overview]
Message-ID: <20170307203406.GC12408@lim.localdomain> (raw)
In-Reply-To: <20170307054251.4361-1-kilobyte@angband.pl>

On Tue, Mar 07, 2017 at 06:42:51AM +0100, Adam Borowski wrote:
> If your filesystem has, eg, data:raid0 metadata:raid1, and you run "btrfs
> balance -dconvert=raid1", the meta.target field will be uninitialized.
> That's otherwise ok, as it's unused except for this warning.
> 
> Thus, let's use the existing set of raid levels for the comparison.
> 
> As a side effect, non-convert balances will now nag about data>metadata.
> 
> Signed-off-by: Adam Borowski <kilobyte@angband.pl>
> ---
> To reproduce:
> dd if=/dev/zero bs=1048576 count=1 seek=4095 of=ra
> dd if=/dev/zero bs=1048576 count=1 seek=4095 of=rb
> mkfs.btrfs ra rb     # defaults to -draid0 -mraid1
> losetup -f ra
> losetup -f rb
> mount /dev/loop0 /mnt/vol1
> btrfs balance start -dconvert=raid1 /mnt/vol1
> 
>  fs/btrfs/volumes.c | 5 +++++
>  1 file changed, 5 insertions(+)
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 3645af2749f8..c016db81ba43 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -3846,6 +3846,11 @@ int btrfs_balance(struct btrfs_balance_control *bctl,
>  		}
>  	} while (read_seqretry(&fs_info->profiles_lock, seq));
>  
> +	/* if we're not converting, the target field is uninitialized */
> +	if (!(bctl->meta.flags & BTRFS_BALANCE_ARGS_CONVERT))
> +		bctl->meta.target = fs_info->avail_metadata_alloc_bits;
> +	if (!(bctl->data.flags & BTRFS_BALANCE_ARGS_CONVERT))
> +		bctl->data.target = fs_info->avail_data_alloc_bits;

This looks good, but this also brings another side effect, @bctl would
also be kept in balance_item which will be used to resume balance in
case of crash, so it may see a different bctl->meta.target.

So would you please use local varibles for meta.target and data.target?

Thanks,

-liubo

>  	if (btrfs_get_num_tolerated_disk_barrier_failures(bctl->meta.target) <
>  		btrfs_get_num_tolerated_disk_barrier_failures(bctl->data.target)) {
>  		btrfs_warn(fs_info,
> -- 
> 2.11.0
> 
> --
> 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

  reply	other threads:[~2017-03-07 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  5:42 [PATCH] btrfs: fix a bogus warning when converting only data or metadata Adam Borowski
2017-03-07 20:34 ` Liu Bo [this message]
2017-03-07 22:34   ` [PATCH v2] " Adam Borowski
2017-03-08  1:27     ` Liu Bo
2017-03-09 13:43     ` David Sterba
2017-03-09 21:56       ` Adam Borowski

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=20170307203406.GC12408@lim.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=kilobyte@angband.pl \
    --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).