From: Reindl Harald <h.reindl@thelounge.net>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Wolfgang Denk <wd@denx.de>, linux-raid@vger.kernel.org
Subject: Re: Disk Monitoring
Date: Thu, 29 Jun 2017 12:37:02 +0200 [thread overview]
Message-ID: <167de591-7d06-dfa7-f7e6-01a2ee4fd0e5@thelounge.net> (raw)
In-Reply-To: <CAJH6TXi8L-x7NiyAqG+22xosqAJ39LB0e_N6b-9PiMrhA2jnjg@mail.gmail.com>
Am 29.06.2017 um 12:14 schrieb Gandalf Corvotempesta:
> 2017-06-29 12:10 GMT+02:00 Reindl Harald <h.reindl@thelounge.net>:
>> there is nothing like "unused part of the array" since the linux-raid-layer
>> knows nothing about the filesystem on top and hence a raid-check (scrub)
>> reads every block as said hardware controller
>
> Yes, this during a scrub.
> Without a scrub, kernel know nothing about an unused part of the array.
>
> Let's assume a unreadable sector is found during a scrub. What
> happens? mdadm kick-out the disk from the array? It tried to
> reallocate the failed sector somewhere keeping the disk up and running
> (and thus, resolving the URE that would prevent a successful resync?)
it tries to re-write the data block (depending if repair is enabled)
normally the disk firmware itself is aware of that event and realloctes
a spare block so the rewrite just suceeds until the disk runs out of
spare sectors
but well, even if it just kicks out the disk soon enough you can replace
it, the array rebuilds and nothing happened - without smart-check/scrub
sooner or later it's detected due rebuild after a disk failed and the
array is gone
next prev parent reply other threads:[~2017-06-29 10:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 13:19 Disk Monitoring Wolfgang Denk
2017-06-29 9:52 ` Gandalf Corvotempesta
2017-06-29 10:10 ` Reindl Harald
2017-06-29 10:14 ` Gandalf Corvotempesta
2017-06-29 10:37 ` Reindl Harald [this message]
2017-06-29 14:28 ` Wols Lists
2017-06-29 10:14 ` Andreas Klauer
2017-06-29 10:14 ` Mateusz Korniak
2017-06-29 10:16 ` Gandalf Corvotempesta
2017-06-29 14:33 ` Wols Lists
2017-06-30 12:35 ` Gandalf Corvotempesta
2017-06-30 14:35 ` Phil Turmel
2017-06-30 19:56 ` Anthony Youngman
2017-07-01 13:42 ` Drew
2017-07-01 14:12 ` Gandalf Corvotempesta
2017-07-01 15:36 ` Drew
2017-06-29 10:20 ` Mateusz Korniak
2017-06-29 10:25 ` Gandalf Corvotempesta
2017-06-29 10:34 ` Reindl Harald
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 10:25 Gandalf Corvotempesta
2017-06-28 10:45 ` Johannes Truschnigg
2017-07-06 3:31 ` NeilBrown
2017-06-28 12:43 ` Wols Lists
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=167de591-7d06-dfa7-f7e6-01a2ee4fd0e5@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=gandalf.corvotempesta@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=wd@denx.de \
/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).