From: "Tomáš Hrdina" <thomas.rkh@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to mount degraded RAID5
Date: Tue, 5 Jul 2016 09:12:53 +0200 [thread overview]
Message-ID: <74e4e27b-5046-0045-292a-c65367c445e1@gmail.com> (raw)
In-Reply-To: <CAJCQCtTPaxWBkmX=ADY7oh5bFjvODmuUNiGXtcBCfxw-c646LA@mail.gmail.com>
sudo btrfs-debug-tree -d /dev/sdc
btrfs-progs v4.6.1
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
ERROR: unable to open /dev/sdc
Thank you
Tomas
------------------------------------------------------------------------
*From:* Chris Murphy
*Sent:* Tuesday, July 05, 2016 12:42AM
*To:* Tomáš Hrdina
*Cc:* Chris Murphy, Btrfs Btrfs
*Subject:* Re: Unable to mount degraded RAID5
On Mon, Jul 4, 2016 at 3:10 PM, Tomáš Hrdina <thomas.rkh@gmail.com> wrote:
> http://sebsauvage.net/paste/?39c73a3440b2e903#WZnUJXNFPNz/fFuOK3QquVeOWQUopcCl0JabtuYMWew=
Both backup 0 and 1 have bad information for backup_fs_root.
backup_fs_root: 0 gen: 0 level: 0
Presumably it automatically tries backup 2 or 3 even though they have
older generations but I'm not sure.
> sudo btrfs-find-root /dev/sda
> warning, device 3 is missing
> Couldn't read chunk tree
> ERROR: open ctree failed
I'm gonna guess the system chunk is bad or damaged somehow and
therefore there's no way to get to the chunk tree. What do you get
for:
# btrfs-debug-tree -d /dev/sda
---
Tato zpráva byla zkontrolována na viry programem Avast Antivirus.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2016-07-05 7:12 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
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 [this message]
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=74e4e27b-5046-0045-292a-c65367c445e1@gmail.com \
--to=thomas.rkh@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).