From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Roman Mamedov <rm@romanrm.net>, 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, 02 May 2017 11:02:34 +0100 [thread overview]
Message-ID: <87efw7ink5.fsf@esperi.org.uk> (raw)
In-Reply-To: <590822E2.1080009@youngman.org.uk> (Wols Lists's message of "Tue, 2 May 2017 07:10:42 +0100")
On 2 May 2017, Wols Lists outgrape:
> On 01/05/17 23:03, Roman Mamedov 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).
>
> I *should* do, rather than I *do* do, but your everyday general
> maintenance tasks, like scrubbing?
You can scrub with mdadm now. :) IIRC (I haven't started using it yet)
the syntax is something like
mdadm --misc --action=check /dev/md/my-array
or
mdadm --misc --action=repair /dev/md/my-array
(though frankly it has never been clear to me which is preferable for a
regular scrub. Probably check on a RAID-6, repair on a RAID-5 where such
failures are much more potentially catastrophic...)
next prev parent reply other threads:[~2017-05-02 10:02 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
2017-05-02 6:10 ` Wols Lists
2017-05-02 10:02 ` Nix [this message]
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=87efw7ink5.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz-lists@ant.gliwice.pl \
--cc=rm@romanrm.net \
--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 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.