From: Roman Mamedov <rm@romanrm.net>
To: Anthony Youngman <antlists@youngman.org.uk>
Cc: Nix <nix@esperi.org.uk>, John Stoffel <john@stoffel.org>,
Mateusz Korniak <mateusz-lists@ant.gliwice.pl>,
Ron Leach <ronleach@tesco.net>,
linux-raid@vger.kernel.org
Subject: Re: Recovery on new 2TB disk: finish=7248.4min (raid1)
Date: Tue, 2 May 2017 03:03:07 +0500 [thread overview]
Message-ID: <20170502030307.4d7a77dd@natsu> (raw)
In-Reply-To: <6398208a-1345-bdec-4be6-a8bd98bfb089@youngman.org.uk>
On Mon, 1 May 2017 22:53:14 +0100
Anthony Youngman <antlists@youngman.org.uk> wrote:
> That's what I understood you to mean, but you are aware that SOME raid
> management still has to be done with echo > /sys/... ?
>
> So mdadm isn't perfect, not by a long chalk, yet :-)
Well, why not post some examples of what you find yourself doing often
via /sys, that's not available in mdadm (maybe as a new thread).
One that I remember is the "want_replacement" mechanism, which was initially
only available via "echo > /sys/..." but quickly got added to mdadm as
"--replace".
People (and various outdated wikis) also tend to suggest using "echo check..."
or "echo repair...", but those are available in mdadm as well, via "--action=".
Lastly, I change the "stripe_cache_size" via /sys/, but that's fine-tuning,
which feels OK to do via sysfs parameters, whereas needing to use sysfs for the
most basic operations of managing the storage system does not.
--
With respect,
Roman
next prev parent reply other threads:[~2017-05-01 22:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:57 Recovery on new 2TB disk: finish=7248.4min (raid1) Ron Leach
2017-04-27 14:25 ` John Stoffel
2017-04-27 14:43 ` Reindl Harald
2017-04-28 7:05 ` Ron Leach
2017-04-27 14:54 ` Mateusz Korniak
2017-04-27 19:03 ` John Stoffel
2017-04-27 19:42 ` Reindl Harald
2017-04-28 7:30 ` Mateusz Korniak
2017-04-30 12:04 ` Nix
2017-04-30 13:21 ` Roman Mamedov
2017-04-30 16:10 ` Nix
2017-04-30 16:47 ` Roman Mamedov
2017-05-01 21:13 ` Nix
2017-05-01 21:44 ` Anthony Youngman
2017-05-01 21:46 ` Roman Mamedov
2017-05-01 21:53 ` Anthony Youngman
2017-05-01 22:03 ` Roman Mamedov [this message]
2017-05-02 6:10 ` Wols Lists
2017-05-02 10:02 ` Nix
2017-05-01 23:26 ` Nix
2017-04-30 17:16 ` Wols Lists
2017-05-01 20:12 ` Nix
2017-04-27 14:58 ` Mateusz Korniak
2017-04-27 19:01 ` Ron Leach
2017-04-28 7:06 ` Mateusz Korniak
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=20170502030307.4d7a77dd@natsu \
--to=rm@romanrm.net \
--cc=antlists@youngman.org.uk \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz-lists@ant.gliwice.pl \
--cc=nix@esperi.org.uk \
--cc=ronleach@tesco.net \
/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).