From: Chris Murphy <lists@colorremedies.com>
To: "Tomáš Hrdina" <thomas.rkh@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to mount degraded RAID5
Date: Mon, 4 Jul 2016 14:43:30 -0600 [thread overview]
Message-ID: <CAJCQCtTPXY7=9vi9Ai2VrCEHzsEj_J0gurAVH5JGLJYmKmUpPw@mail.gmail.com> (raw)
In-Reply-To: <dc944146-50ce-b2fd-189c-a2c9f5a957c3@gmail.com>
On Mon, Jul 4, 2016 at 1:11 PM, Tomáš Hrdina <thomas.rkh@gmail.com> wrote:
> Result from dmesg:
> http://sebsauvage.net/paste/?4e8e95b5eafbf675#ybToBzZ/WAoRjjugeH6N2YXZKEBlswaNI/J41GBmFYU=
[10849.041749] BTRFS info (device sda): allowing degraded mounts
[10849.041754] BTRFS info (device sda): disk space caching is enabled
[10849.041756] BTRFS: has skinny extents
[10849.090553] BTRFS error (device sda): bad tree block start
10160120763642806272 12678831570944
[10849.090676] BTRFS error (device sda): bad tree block start
10160120763642806272 12678831570944
[10849.090700] BTRFS: failed to read chunk tree on sda
[10849.100153] BTRFS: open_ctree failed
Try 'mount -o ro,degraded,recovery
>
> sudo btrfs check /dev/sda
> warning, device 3 is missing
> checksum verify failed on 12678831570944 found 3DC57E3E wanted 771D2379
> checksum verify failed on 12678831570944 found 3DC57E3E wanted 771D2379
> bytenr mismatch, want=12678831570944, have=10160133442474442752
> Couldn't read chunk tree
> Couldn't open file system
Want and have are way far apart. If the mount command above still
fails then I'd like to see:
# btrfs-show-super -fa /dev/sda
# btrfs-show-super -fa /dev/sdb
Pretty much look for any discrepancies in generation, root and
chunk_root addresses, both in the main part of the super as well as in
the backups.
# btrfs-find-root /dev/sda
Maybe it's possible to use a different tree to get it mounted. I don't
know what happened but merely a failing device should not either break
checksums or lose the ability to mount the proper tree; but for sure
one of the backups should work.
Have you done a scrub on this file system and do you know if anything
was fixed or if it always found no problem?
--
Chris Murphy
next prev parent reply other threads:[~2016-07-04 20:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 18:09 Unable to mount degraded RAID5 Tomáš Hrdina
2016-07-04 18:41 ` Chris Murphy
[not found] ` <95f58623-95a4-b5d2-fa3a-bfb957840a31@gmail.com>
2016-07-04 19:01 ` Chris Murphy
2016-07-04 19:11 ` Tomáš Hrdina
2016-07-04 20:43 ` Chris Murphy [this message]
2016-07-04 21:10 ` Tomáš Hrdina
2016-07-04 22:42 ` Chris Murphy
2016-07-04 22:59 ` Chris Murphy
2016-07-05 7:12 ` Tomáš Hrdina
2016-07-05 3:48 ` Andrei Borzenkov
2016-07-05 15:13 ` Chris Murphy
2016-07-05 18:40 ` Tomáš Hrdina
2016-07-05 23:19 ` Chris Murphy
2016-07-06 8:07 ` Tomáš Hrdina
2016-07-06 16:08 ` Chris Murphy
2016-07-06 17:50 ` Tomáš Hrdina
2016-07-06 18:12 ` Chris Murphy
2016-07-09 17:30 ` Tomáš Hrdina
2016-07-09 18:33 ` Chris Murphy
2016-07-10 7:01 ` Tomáš Hrdina
2016-07-10 20:08 ` Chris Murphy
2016-07-11 17:17 ` Tomáš Hrdina
2016-07-11 19:25 ` Chris Murphy
[not found] <CAFDLS-CtnVDtD8d=Wtp0tVokKJ6pjptpX7MR862dThBJvSPC5g@mail.gmail.com>
2016-07-06 17:12 ` Fwd: " Gonzalo Gomez-Arrue Azpiazu
2016-07-06 18:19 ` Chris Murphy
2016-07-07 12:24 ` Gonzalo Gomez-Arrue Azpiazu
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='CAJCQCtTPXY7=9vi9Ai2VrCEHzsEj_J0gurAVH5JGLJYmKmUpPw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=thomas.rkh@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).