From: Graham Cobb <g.btrfs@cobb.uk.net>
To: Menion <menion@gmail.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs: convert metadata from raid5 to raid1
Date: Mon, 17 Feb 2020 18:05:10 +0000 [thread overview]
Message-ID: <a42ef272-3ea7-5d44-8261-6665fa1d4a60@cobb.uk.net> (raw)
In-Reply-To: <20200217141708.GE1235@savella.carfax.org.uk>
On 17/02/2020 14:17, Hugo Mills wrote:
> On Mon, Feb 17, 2020 at 03:12:35PM +0100, Menion wrote:
>> ok thanks
>> I have launched it (in a tmux session), after 5 minutes the command
>> did not return yet, but dmesg and btrfs balance status
>> /array/mount/point report it in progress (0%).
>> Is it normal?
>
> Yes, it's got to rewrite all of your metadata. This can take a
> while (especially if you have lots of snapshots or reflinks -- such as
> from running a deduper). You should be able to see progress happening
> fairly regularly in dmesg. This is typically one chunk every minute or
> so, although some chunks can take much *much* longer.
Also, you can watch what is happening by using "btrfs filesystem usage
/your/mount/point". You should see "Metadata,RAID5:" going down and
"Metadata,RAID1" going up. I often leave:
watch -n 10 btrfs fi usage /mount/point
running in a window while doing these sorts of things so I can see how
things are going at a glance.
next prev parent reply other threads:[~2020-02-17 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:43 btrfs: convert metadata from raid5 to raid1 Menion
2020-02-17 13:49 ` Swâmi Petaramesh
2020-02-17 13:50 ` Menion
2020-02-17 13:51 ` Menion
2020-02-17 13:55 ` Hugo Mills
2020-02-17 13:54 ` Hugo Mills
2020-02-17 13:55 ` Swâmi Petaramesh
2020-02-17 14:12 ` Menion
2020-02-17 14:17 ` Hugo Mills
2020-02-17 18:05 ` Graham Cobb [this message]
2020-02-18 8:34 ` Menion
2020-02-18 8:41 ` Nikolay Borisov
2020-02-18 8:43 ` Menion
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=a42ef272-3ea7-5d44-8261-6665fa1d4a60@cobb.uk.net \
--to=g.btrfs@cobb.uk.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=menion@gmail.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