From: Anthonys Lists <antlists@youngman.org.uk>
To: Nix <nix@esperi.org.uk>, Phil Turmel <philip@turmel.org>
Cc: NeilBrown <neilb@suse.com>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RFC - Raid error detection and auto-recovery (was Fault tolerance with badblocks)
Date: Tue, 16 May 2017 17:11:58 +0100 [thread overview]
Message-ID: <591B24CE.50805@youngman.org.uk> (raw)
In-Reply-To: <87efvosstq.fsf@esperi.org.uk>
On 16/05/2017 16:51, Nix wrote:
> On 16 May 2017, Phil Turmel spake thusly:
>
>> >On 05/16/2017 10:53 AM, Wols Lists wrote:
>>> >>First thing we do is read the entire stripe.
>> >
>> >A substantial performance degradation, right out of the gate...
> I'm fairly sure Wol's intention is to do this as part of a check/repair
> operation. You don't want to run like this in normal usage! (Though I
> agree that it seems unclear whether you want to do this at all.)
It's not meant to be on by default. Imho, if the sysadmin switches it
on, it's their lookout :-) Integrity over speed - some sysadmins might
make that choice.
Cheers,
Wol
prev parent reply other threads:[~2017-05-16 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 13:26 RFC - Raid error detection and auto-recovery (was Fault tolerance with badblocks) Wols Lists
2017-05-10 17:07 ` Piergiorgio Sartor
2017-05-11 23:31 ` Eyal Lebedinsky
2017-05-15 3:43 ` NeilBrown
2017-05-15 11:11 ` Nix
2017-05-15 13:44 ` Wols Lists
2017-05-15 22:31 ` Phil Turmel
2017-05-16 10:33 ` Wols Lists
2017-05-16 14:17 ` Phil Turmel
2017-05-16 14:53 ` Wols Lists
2017-05-16 15:31 ` Phil Turmel
2017-05-16 15:51 ` Nix
2017-05-16 16:11 ` Anthonys Lists [this message]
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=591B24CE.50805@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=nix@esperi.org.uk \
--cc=philip@turmel.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.