From: Dmitrii Tcvetkov <demfloro@demfloro.ru>
To: g6094199@freenet.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: degraded BTRFS RAID 1 not mountable: open_ctree failed, unable to find block group for 0
Date: Tue, 22 Aug 2017 13:28:16 +0300 [thread overview]
Message-ID: <20170822132816.1bd0a511@job> (raw)
In-Reply-To: <2bee7fc8-3724-0ade-ed7f-28cc296c0595@chefmail.de>
On Tue, 22 Aug 2017 11:31:23 +0200
g6094199@freenet.de wrote:
> So 1st should be investigating why did the disk not get removed
> correctly? Btrfs dev del should remove the device corretly, right? Is
> there a bug?
It should and probably did. To check that we need to see output of
btrfs filesystem show
and output of
btrfs filesystem usage <mountpoint>
If there are non-raid1 chunks then you need to do soft balance:
btrfs balance start -mconvert=raid1,soft -dconvert=raid1,soft <mountpoint>
The balance should finish very quickly as you probably have only one of
data and metadata single chunks. They appeared during writes when the
filesystem was mounted read-write in degraded mode.
next prev parent reply other threads:[~2017-08-22 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 9:31 degraded BTRFS RAID 1 not mountable: open_ctree failed, unable to find block group for 0 g6094199
2017-08-22 10:28 ` Dmitrii Tcvetkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-23 13:12 g6094199
2016-11-16 10:25 Martin Steigerwald
2016-11-16 10:43 ` Roman Mamedov
2016-11-16 10:55 ` Martin Steigerwald
2016-11-16 11:00 ` Roman Mamedov
2016-11-16 11:04 ` Martin Steigerwald
2016-11-16 12:57 ` Austin S. Hemmelgarn
2016-11-16 17:06 ` Martin Steigerwald
2016-11-17 20:05 ` Chris Murphy
2016-11-17 20:20 ` Austin S. Hemmelgarn
2016-11-19 20:27 ` Chris Murphy
2016-11-20 11:58 ` Niccolò Belli
2016-11-17 20:46 ` Martin Steigerwald
2016-11-16 11:18 ` Martin Steigerwald
2016-11-16 12:48 ` Austin S. Hemmelgarn
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=20170822132816.1bd0a511@job \
--to=demfloro@demfloro.ru \
--cc=g6094199@freenet.de \
--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.