From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Chris Murphy" <lists@colorremedies.com>,
"Tomáš Hrdina" <thomas.rkh@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to mount degraded RAID5
Date: Tue, 5 Jul 2016 06:48:45 +0300 [thread overview]
Message-ID: <577B2E1D.5070808@gmail.com> (raw)
In-Reply-To: <CAJCQCtTPXY7=9vi9Ai2VrCEHzsEj_J0gurAVH5JGLJYmKmUpPw@mail.gmail.com>
04.07.2016 23:43, Chris Murphy пишет:
>
> Have you done a scrub on this file system and do you know if anything
> was fixed or if it always found no problem?
>
scrub on degraded RAID5 cannot fix anything by definition, because even
if scrub finds discrepancies, it does not have enough data to
reconstruct them. I would actually avoid it - the worst that can happen
if it attempts to replace remaining data with something faked.
next prev parent reply other threads:[~2016-07-05 3:48 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
2016-07-05 3:48 ` Andrei Borzenkov [this message]
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=577B2E1D.5070808@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--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).