From: Roman Mamedov <rm@romanrm.net>
To: Martin Steigerwald <martin.steigerwald@teamix.de>
Cc: <linux-btrfs@vger.kernel.org>, Martin <martin@lichtvoll.de>
Subject: Re: degraded BTRFS RAID 1 not mountable: open_ctree failed, unable to find block group for 0
Date: Wed, 16 Nov 2016 15:43:36 +0500 [thread overview]
Message-ID: <20161116154336.543a326b@natsu> (raw)
In-Reply-To: <18970348.FUMEOFOSb3@merkaba>
On Wed, 16 Nov 2016 11:25:00 +0100
Martin Steigerwald <martin.steigerwald@teamix.de> wrote:
> merkaba:~> mount -o degraded,clear_cache /dev/satafp1/backup /mnt/zeit
> mount: Falscher Dateisystemtyp, ungültige Optionen, der
> Superblock von /dev/mapper/satafp1-backup ist beschädigt, fehlende
> Kodierungsseite oder ein anderer Fehler
>
> Manchmal liefert das Systemprotokoll wertvolle Informationen –
> versuchen Sie dmesg | tail oder ähnlich
> merkaba:~#32> dmesg | tail -6
> [ 3080.120687] BTRFS info (device dm-13): allowing degraded mounts
> [ 3080.120699] BTRFS info (device dm-13): force clearing of disk cache
> [ 3080.120703] BTRFS info (device dm-13): disk space caching is enabled
> [ 3080.120706] BTRFS info (device dm-13): has skinny extents
> [ 3080.150957] BTRFS warning (device dm-13): missing devices (1) exceeds the limit (0), writeable mount is not allowed
> [ 3080.195941] BTRFS: open_ctree failed
I have to wonder did you read the above message? What you need at this point
is simply "-o degraded,ro". But I don't see that tried anywhere down the line.
See also (or try): https://patchwork.kernel.org/patch/9419189/
--
With respect,
Roman
next prev parent reply other threads:[~2016-11-16 10:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 10:25 degraded BTRFS RAID 1 not mountable: open_ctree failed, unable to find block group for 0 Martin Steigerwald
2016-11-16 10:43 ` Roman Mamedov [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2017-08-22 9:31 g6094199
2017-08-22 10:28 ` Dmitrii Tcvetkov
2017-08-23 13:12 g6094199
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=20161116154336.543a326b@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin.steigerwald@teamix.de \
--cc=martin@lichtvoll.de \
/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).