From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Gareth Pye <gareth@cerberos.id.au>,
Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Recommendation on raid5 drive error resolution
Date: Thu, 1 Sep 2016 07:25:14 -0400 [thread overview]
Message-ID: <0cad7942-096c-1ea4-bf31-a4e959bcc4f8@gmail.com> (raw)
In-Reply-To: <CA+WRLO9ZazygSMfLjpfXO_bYMmJVecd3be44EKJWMDORFXiVKg@mail.gmail.com>
On 2016-08-31 19:04, Gareth Pye wrote:
> ro,degraded has mounted it nicely and my rsync of the more useful data
> is progressing at the speed of WiFi.
>
> There are repeated read errors from one drive still but the rsync
> hasn't bailed yet, which I think means there isn't any overlapping
> errors in any of the files it has touched thus far. Am I right or is
> their likely to be corrupt data in the files I've synced off?
Unless you've been running with nocow or nodatasum in your mount
options, then what you've concluded should be correct. I would still
suggest verifying the data by some external means if possible, this type
of situation is not something that's well tested, and TBH I'm amazed
that things are working to the degree that they are.
>
> On Wed, Aug 31, 2016 at 7:46 AM, Gareth Pye <gareth@cerberos.id.au> wrote:
>> Or I could just once again select the right boot device in the bios. I
>> think I want some new hardware :)
>>
>> On Wed, Aug 31, 2016 at 7:23 AM, Gareth Pye <gareth@cerberos.id.au> wrote:
>>> On Wed, Aug 31, 2016 at 4:28 AM, Chris Murphy <lists@colorremedies.com> wrote:
>>>> But I'd try a newer kernel before you
>>>> give up on it.
>>>
>>>
>>> Any recommendations on liveCDs that have recent kernels & btrfs tools?
>>> For no apparent reason system isn't booting normally either, and I'm
>>> reluctant to fix that before at least confirming the things I at least
>>> partially care about have a recent backup.
>>>
>>> --
>>> Gareth Pye - blog.cerberos.id.au
>>> Level 2 MTG Judge, Melbourne, Australia
>>
>>
>>
>> --
>> Gareth Pye - blog.cerberos.id.au
>> Level 2 MTG Judge, Melbourne, Australia
>
>
>
next prev parent reply other threads:[~2016-09-01 11:25 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
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 [this message]
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=0cad7942-096c-1ea4-bf31-a4e959bcc4f8@gmail.com \
--to=ahferroin7@gmail.com \
--cc=gareth@cerberos.id.au \
--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).