All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Suddenly cannot change metadata profile any longer
Date: Sun, 15 Feb 2015 21:01:07 +0000 (UTC)	[thread overview]
Message-ID: <pan.2015.02.15.21.01.07@googlemail.com> (raw)


Here's a new one (with kernel 3.18.7++):

$btrfs --version
Btrfs v3.18.2 (also tried 3.19-rc2)

$mount /dev/sdf1 /mnt/usb

$btrfs filesystem df /mnt/usb
Data, single: total=8.00MiB, used=256.00KiB
System, single: total=32.00MiB, used=16.00KiB
Metadata, single: total=1.00GiB, used=112.00KiB
GlobalReserve, single: total=16.00MiB, used=0.00B

Note: metadata=single - done right after mkfs for the initial balance.

$btrfs balance start -mconvert=dup /mnt/usb    
Done, had to relocate 2 out of 3 chunks

root>btrfs filesystem df /mnt/usb              
Data, single: total=8.00MiB, used=512.00KiB
System, single: total=32.00MiB, used=16.00KiB
Metadata, single: total=1.00GiB, used=192.00KiB
GlobalReserve, single: total=16.00MiB, used=0.00B

Wait, what? Still single?

This used to work, but somehow no longer does (verified on another
filesystem). If it's dup, it stays dup; if it's single, it stays single.

What works is the very first balance after the mkfs - it successfully
changes from the initial default dup to single, but subsequent balances
don't work. They also don't really fail.

Any ideas what might have caused this? Must have been a recent patch.

Holger


             reply	other threads:[~2015-02-15 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 21:01 Holger Hoffstätte [this message]
2015-02-16 15:18 ` Suddenly cannot change metadata profile any longer (BISECTED) Holger Hoffstätte
2015-02-22 18:01   ` Holger Hoffstätte
2015-02-23 19:39     ` 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=pan.2015.02.15.21.01.07@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.