From: "Jakob Schöttl" <jschoett@gmail.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>, linux-btrfs@vger.kernel.org
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: Cannot 'mount -o degraded /dev/replacement' after a replace
Date: Sat, 9 Feb 2019 16:57:51 +0100 [thread overview]
Message-ID: <969d659b-bce1-7a72-6e50-6981dae56a94@gmail.com> (raw)
In-Reply-To: <0680cf0a-5a03-086f-d3f7-3317655401f0@gmail.com>
Am 09.02.19 um 16:32 schrieb Andrei Borzenkov:
> Running
>
> btrfs balance start -f -ssoft,convert=raid1 -dsoft,convert=raid1
> -msoft,convert=raid1 /mnt
>
> fixes it. I am not sure whether btrfs is expected to do it automatically
> as of now.
This fix seems to work for me, too. Output was:
> Done, had to relocate 5 out of 8 chunks
Tested without any subvolumes or data.
next prev parent reply other threads:[~2019-02-09 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 10:36 Cannot 'mount -o degraded /dev/replacement' after a replace Jakob Schöttl
2019-02-09 12:16 ` Qu Wenruo
2019-02-09 13:45 ` Jakob Schöttl
2019-02-09 15:32 ` Andrei Borzenkov
2019-02-09 15:57 ` Jakob Schöttl [this message]
2019-02-09 15:36 ` Andrei Borzenkov
2019-02-10 18:44 ` Chris Murphy
2019-02-11 1:36 ` Qu Wenruo
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=969d659b-bce1-7a72-6e50-6981dae56a94@gmail.com \
--to=jschoett@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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