linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: Shaohua Li <shli@fb.com>
Subject: Re: [PATCH] Revert "btrfs: delete chunk allocation attemp when setting block group ro"
Date: Wed, 29 Apr 2015 11:24:09 -0700	[thread overview]
Message-ID: <20150429182409.GA23155@mew.dhcp4.washington.edu> (raw)
In-Reply-To: <c99a895bc0facef23387ef7b44c98c0df41216fa.1429431096.git.osandov@osandov.com>

On Sun, Apr 19, 2015 at 01:17:05AM -0700, Omar Sandoval wrote:
> This reverts commit 2f0810880f082fa8ba66ab2c33b02e4ff9770a5e.
> 
> This tried to fix the following test case:
> 
> 	mkfs.ext4 -F /dev/sda
> 	btrfs-convert /dev/sda
> 	mount /dev/sda /mnt
> 	btrfs device add -f /dev/sdb /mnt
> 	btrfs balance start -v -dconvert=raid1 -mconvert=raid1 /mnt
> 
> Before the reverted commit, this test case failed with ENOSPC because
> all chunks on the freshly converted filesystem were allocated, although
> many were empty. The reverted commit removed an allocation attempt in
> btrfs_set_block_group_ro(), but that fix wasn't right. After the
> reverted commit, the balance succeeds, but the data/metadata profiles
> aren't actually updated:
> 
> 	# btrfs fi df /mnt
> 	Data, single: total=208.00MiB, used=49.48MiB
> 	System, single: total=32.00MiB, used=4.00KiB
> 	Metadata, single: total=208.00MiB, used=48.00KiB
> 	GlobalReserve, single: total=4.00MiB, used=0.00B
> 
> Indeed, several users reported that this commit caused a regression and
> that converting the data and metadata profiles no longer works. This is
> because the chunk allocation in question was where we actually allocated
> the chunk with the new profile. Not seeing a more obvious fix, let's
> just revert this. We can work around the ENOSPC in the original test
> case by just issuing a balance to free up the unused block groups before
> the conversion, anyways:
> 
> 	mkfs.ext4 -F /dev/sda
> 	btrfs-convert /dev/sda
> 	mount /dev/sda /mnt
> 	btrfs balance start -v /mnt
> 	btrfs device add -f /dev/sdb /mnt
> 	btrfs balance start -v -dconvert=raid1 -mconvert=raid1 /mnt
> 
> Reported-by: Holger Hoffstätte <holger.hoffstaette@googlemail.com>
> Cc: Shaohua Li <shli@fb.com>
> Signed-off-by: Omar Sandoval <osandov@osandov.com>
> ---
> Holger reported this awhile ago and I haven't seen a proper fix make it
> to the ML. I messed around with it for awhile and came up empty, but I
> figured I might as well send this in. Applies to v4.0.
> 
>  fs/btrfs/extent-tree.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 

Has another fix for this shown up yet? Currently 4.0 and up can't
convert between data/metadata profiles, which seems like a pretty major
regression.

Thanks,
-- 
Omar

  reply	other threads:[~2015-04-29 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19  8:17 [PATCH] Revert "btrfs: delete chunk allocation attemp when setting block group ro" Omar Sandoval
2015-04-29 18:24 ` Omar Sandoval [this message]
2015-04-29 20:21   ` Chris Mason

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=20150429182409.GA23155@mew.dhcp4.washington.edu \
    --to=osandov@osandov.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=shli@fb.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;
as well as URLs for NNTP newsgroup(s).