From: Chris Murphy <lists@colorremedies.com>
To: msk conf <msk.conf@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Can't mount (even in ro) after power outage - corrupt leaf, open_ctree failed
Date: Sun, 21 Jan 2018 14:54:26 -0700 [thread overview]
Message-ID: <CAJCQCtSRj1v-qksod3FetjVCutSL1MbLWdg1KSt1RsndJkTU=A@mail.gmail.com> (raw)
In-Reply-To: <7ebd40d4-3eea-9ad7-492f-b5d22cf935b0@gmail.com>
On Sun, Jan 21, 2018 at 8:53 AM, msk conf <msk.conf@gmail.com> wrote:
> Hello there,
>
> I would like to ask you for help with (corrupted) btrfs on my nas.
>
> After power outage I can't mount it back at all:
> UUID="e8cb7e76-7f93-4eac-aec7-ca64395d2110" /array btrfs
> noatime,compress=lzo 0 2
> UUID="e8cb7e76-7f93-4eac-aec7-ca64395d2110" /home btrfs
> noatime,compress=lzo,subvolid=3315 0 0
What do you get for
btrfs fi df /array
I want to know if all block groups are raid1.
>
> I tried combination of recovery,ro,degraded,usebackuproot, specifying
> partial partitions where fs is placed to - no success at all.
> for example
> mount -ousebackuproot,ro
> /dev/disk/by-uuid/e8cb7e76-7f93-4eac-aec7-ca64395d2110 /mnt/restore
> mount -ousebackuproot,ro,degraded /dev/sdb4 /mnt/restore
> ...
>
> Failing with:
> [ 2765.719548] BTRFS critical (device sda4): corrupt leaf, slot offset bad:
> block=3997250650112, root=1, slot=48
> [ 2765.731772] BTRFS error (device sda4): failed to read block groups: -5
> [ 2765.781993] BTRFS error (device sda4): open_ctree failed
I don't know that "degraded" will know which device to ignore when
both devices are available. But then, if everything is raid1, a
failure on sda4 should result in a retry on sdb4. There's not enough
information in the log provided. Sounds like a bad sector resulting in
an IO error.
>
> Some informations at beginning:
>
> uname -a
> Linux nas 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU/Linux
>
> btrfs --version
> btrfs-progs v4.7.3
I wouldn't use btrfs check, let alone using it with --repair, with
this version. Get something newer, ideally 4.14.1.
The thing to include in the next report is output from:
btrfs check
btrfs check --mode=lowmem
I don't recommend using --repair until you've exhausted all other
options, including any scraping necessary with btrfs restore to get
your backups up to date.
--
Chris Murphy
next prev parent reply other threads:[~2018-01-21 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 15:53 Can't mount (even in ro) after power outage - corrupt leaf, open_ctree failed msk conf
2018-01-21 21:54 ` Chris Murphy [this message]
[not found] ` <05babf08-00de-ae0f-06f3-546719674aa1@gmail.com>
[not found] ` <CAJCQCtSkPTLJ0d94_HrNmr_g+1spOBXjS8EY1RkXnXf15wUKFw@mail.gmail.com>
2018-01-21 23:24 ` Chris Murphy
2018-01-22 9:14 ` Zatkovský Dušan
2018-01-24 8:56 ` Zatkovský Dušan
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='CAJCQCtSRj1v-qksod3FetjVCutSL1MbLWdg1KSt1RsndJkTU=A@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=msk.conf@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;
as well as URLs for NNTP newsgroup(s).