From: Chris Murphy <lists@colorremedies.com>
To: Gareth Pye <gareth@cerberos.id.au>
Cc: Chris Murphy <lists@colorremedies.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Recommendation on raid5 drive error resolution
Date: Tue, 30 Aug 2016 12:04:27 -0600 [thread overview]
Message-ID: <CAJCQCtQddXz26cjp=tGcO5d5E9N=Zmjdd=qwonjGdh+NJ7aLQQ@mail.gmail.com> (raw)
In-Reply-To: <CA+WRLO-1oJLZ56EivVTg=bycNhfpOt8ovLrLbgnNeCVKgvbxhQ@mail.gmail.com>
On Tue, Aug 30, 2016 at 3:58 AM, Gareth Pye <gareth@cerberos.id.au> wrote:
> Okay, things aren't looking good. The FS wont mount for me:
> http://pastebin.com/sEEdRxsN
Try to mount with -o ro,degraded. I have no idea which device it'll
end up dropping, but it might at least get you a read only mount so
you can get stuff off - if you want - without modifying the file
system.
One of us would have to go look in source to see what causes "[
163.612313] BTRFS: failed to read the system array on sdd" to appear
for each device. It's suspicious that every drive produces that
message, and there are no fixup messages at all ever. So it sounds
like it's not even getting far enough to figure out what's bad and
reconstruct from parity. And I don't even see csum errors either,
which is also suspicious. It's like the boot strapping itself is
failing which kinda implicates superblocks?
What do you get for
btrfs rescue super-recover -v /dev/sdX ?
--
Chris Murphy
next prev parent reply other threads:[~2016-08-30 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 7:23 Recommendation on raid5 drive error resolution Gareth Pye
2016-08-28 7:05 ` DanglingPointer
2016-08-28 17:15 ` Chris Murphy
2016-08-29 0:15 ` Gareth Pye
2016-08-29 0:18 ` Gareth Pye
2016-08-29 23:01 ` Gareth Pye
2016-08-30 9:58 ` Gareth Pye
2016-08-30 18:04 ` Chris Murphy [this message]
2016-08-30 18:28 ` Chris Murphy
2016-08-30 21:23 ` Gareth Pye
2016-08-30 21:45 ` Chris Murphy
2016-08-30 21:46 ` Gareth Pye
2016-08-31 23:04 ` Gareth Pye
2016-09-01 11:25 ` Austin S. Hemmelgarn
2016-09-07 0:35 ` Gareth Pye
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='CAJCQCtQddXz26cjp=tGcO5d5E9N=Zmjdd=qwonjGdh+NJ7aLQQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=gareth@cerberos.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.