From: Phil Turmel <philip@turmel.org>
To: Mateusz Korniak <mateusz-lists@ant.gliwice.pl>
Cc: Marc MERLIN <marc@merlins.org>,
Kay Diederichs <kay.diederichs@uni-konstanz.de>,
Andreas Klauer <Andreas.Klauer@metamorpher.de>,
Adam Goryachev <mailinglists@websitemanagers.com.au>,
Roger Heflin <rogerheflin@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: force remapping a pending sector in sw raid5 array
Date: Mon, 12 Feb 2018 10:29:20 -0500 [thread overview]
Message-ID: <0780e95c-ae84-4b2b-0222-f59df368a2ee@turmel.org> (raw)
In-Reply-To: <3275011.qXpCPUrKDu@matkor-lenovo>
On 02/12/2018 05:43 AM, Mateusz Korniak wrote:
> On Sunday 11 of February 2018 12:13:45 Phil Turmel wrote:
>> On 02/10/2018 04:43 PM, Mateusz Korniak wrote:
>>
>>> data is saved under different location when such write fails for
>>> later reads?
>>
>> No. (...)
>
> So having arrays having non-empty BBL members means that array is in fact
> degraded (for tiny part, but still), right?
Yes, it's degraded wherever there's a BBL entry. To my knowledge, *no*
upper layer, whether device mapper or any filesystem, uses the
information to avoid allocations in the degraded area or to rescue the
data precariously living there. Last I looked, mdadm --detail did not
report whether the array has degraded regions. You must inspect the
output of mdadm --examine for every member.
> Is there any option for mdadm --monitor to send warning e-mail when bbl entry
> is added? (I can't see anything regarding bbl in mdadm --monitor section) ?
No. The feature is incomplete. The only mitigation is to turn it off.
Phil
next prev parent reply other threads:[~2018-02-12 15:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:14 force remapping a pending sector in sw raid5 array Marc MERLIN
2018-02-06 18:59 ` Reindl Harald
2018-02-06 19:36 ` Marc MERLIN
2018-02-06 20:03 ` Andreas Klauer
2018-02-06 21:51 ` Adam Goryachev
2018-02-06 22:02 ` Marc MERLIN
2018-02-06 22:31 ` Roger Heflin
2018-02-06 22:46 ` Marc MERLIN
2018-02-07 4:29 ` Marc MERLIN
2018-02-07 9:42 ` Kay Diederichs
2018-02-09 19:29 ` Marc MERLIN
2018-02-09 19:57 ` Kay Diederichs
2018-02-09 20:02 ` Roger Heflin
2018-02-09 20:13 ` Phil Turmel
2018-02-09 20:29 ` Marc MERLIN
2018-02-09 20:44 ` Phil Turmel
2018-02-09 21:22 ` Marc MERLIN
2018-02-09 22:07 ` Wol's lists
2018-02-09 22:36 ` Marc MERLIN
2018-02-09 20:52 ` Kay Diederichs
2018-02-11 20:52 ` Roger Heflin
2018-02-09 21:17 ` Kay Diederichs
2018-02-10 21:43 ` Mateusz Korniak
2018-02-11 15:41 ` Marc MERLIN
2018-02-11 16:41 ` Marc MERLIN
2018-02-11 17:13 ` Phil Turmel
2018-02-11 18:02 ` Wols Lists
2018-02-12 10:43 ` Mateusz Korniak
2018-02-12 15:29 ` Phil Turmel [this message]
2018-02-12 16:49 ` Marc MERLIN
2018-02-12 17:16 ` Phil Turmel
2018-02-12 17:30 ` Marc MERLIN
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=0780e95c-ae84-4b2b-0222-f59df368a2ee@turmel.org \
--to=philip@turmel.org \
--cc=Andreas.Klauer@metamorpher.de \
--cc=kay.diederichs@uni-konstanz.de \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=marc@merlins.org \
--cc=mateusz-lists@ant.gliwice.pl \
--cc=rogerheflin@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