From: "Zatkovský Dušan" <msk.conf@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Can't mount (even in ro) after power outage - corrupt leaf, open_ctree failed
Date: Wed, 24 Jan 2018 09:56:32 +0100 [thread overview]
Message-ID: <4a48db35-40c3-e640-9f1b-dfa1173f7024@gmail.com> (raw)
In-Reply-To: <ed9f0354-3c83-ed11-4f42-881929524298@gmail.com>
Ok, so I ended with btrfs restore, seems that all (or most important)
files were restored.
Now looking for another reliable filesystem which will not unrecoverably
die on power outage.
msk
Dňa 22. 1. 2018 o 10:14 Zatkovský Dušan napísal(a):
> Hi.
>
> Badblocks finished on both disks with no errors. The only messages
> from kernel
> during night are 6x perf: interrupt took too long (2511 > 2500),
> lowering kernel.perf_event_max_sample_rate to 79500
>
> root@nas:~# smartctl -l scterc /dev/sda
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-4-amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke,
> www.smartmontools.org
>
> SCT Error Recovery Control:
> Read: 70 (7.0 seconds)
> Write: 70 (7.0 seconds)
>
> root@nas:~# smartctl -l scterc /dev/sdb
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-4-amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke,
> www.smartmontools.org
>
> SCT Error Recovery Control:
> Read: 70 (7.0 seconds)
> Write: 70 (7.0 seconds)
>
> root@nas:~# btrfs-debug-tree -t chunk /dev/sda4 | grep 'METADATA\|SYSTEM'
> incorrect offsets 13686 13622
> type METADATA|RAID1 num_stripes 2
> type METADATA|RAID1 num_stripes 2
> type SYSTEM|RAID1 num_stripes 2
> type METADATA|RAID1 num_stripes 2
> type METADATA|RAID1 num_stripes 2
>
> root@nas:~# btrfs-debug-tree -t chunk /dev/sdb4 | grep 'METADATA\|SYSTEM'
> incorrect offsets 13686 13622
> type METADATA|RAID1 num_stripes 2
> type METADATA|RAID1 num_stripes 2
> type SYSTEM|RAID1 num_stripes 2
> type METADATA|RAID1 num_stripes 2
> type METADATA|RAID1 num_stripes 2
>
> (still used "old" version of btrfs tools, working remotely now, I will
> boot something newer when I will get access to that NAS at EOD)
>
> Thank you
> msk
>
>
> Dňa 22. 1. 2018 o 0:24 Chris Murphy napísal(a):
>> On Sun, Jan 21, 2018 at 4:13 PM, Chris Murphy
>> <lists@colorremedies.com> wrote:
>>> On Sun, Jan 21, 2018 at 3:31 PM, msk conf <msk.conf@gmail.com> wrote:
>>>> Hello,
>>>>
>>>> thank you for the reply.
>>>>
>>>>> What do you get for btrfs fi df /array
>>>>
>>>> Can't do that because filesystem is not mountable. I will get stats
>>>> for '/'
>>>> filesystem instead (because '/array' is an empty directory -
>>>> mountpoint on /
>>> Try
>>> $ sudo btrfs-debug-tree -t chunk /dev/mapper/first | grep
>>> 'METADATA\|SYSTEM'
>>
>> You need to adapt that /dev/ node for your case, I just copy pasted
>> that from my setup. Anyway, that will look at the chunk tree and show
>> the profile for these chunk types.
>>
>>
>
prev parent reply other threads:[~2018-01-24 8:56 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
[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 [this message]
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=4a48db35-40c3-e640-9f1b-dfa1173f7024@gmail.com \
--to=msk.conf@gmail.com \
--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 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).