From: Reindl Harald <h.reindl@thelounge.net>
To: antlists <antlists@youngman.org.uk>,
David Woodhouse <dwmw2@infradead.org>,
linux-raid@vger.kernel.org
Subject: Re: Spurious bad blocks on RAID-5
Date: Tue, 25 May 2021 19:49:46 +0200 [thread overview]
Message-ID: <bb85ee01-f93e-8184-973d-1c46d56016fa@thelounge.net> (raw)
In-Reply-To: <03a8ce28-3699-6dd9-b3ad-baf1e6dd8668@youngman.org.uk>
Am 25.05.21 um 18:49 schrieb antlists:
> On 25/05/2021 01:41, David Woodhouse wrote:
>> I see no actual I/O errors on the underlying drives, and S.M.A.R.T
>> reports them healthy. Yet MD thinks I have bad blocks on three of them
>> at exactly the same location:
>>
>> Bad-blocks list is empty in /dev/sda3
>> Bad-blocks list is empty in /dev/sdb3
>> Bad-blocks on /dev/sdc3:
>> 13086517288 for 32 sectors
>> Bad-blocks on /dev/sdd3:
>> 13086517288 for 32 sectors
>> Bad-blocks on /dev/sde3:
>> 13086517288 for 32 sectors
>>
>> That seems very unlikely to me. FWIW those ranges are readable on the
>> underlying disks, and contain all zeroes.
>>
>> Is the best option still to reassemble the array with
>> '--update=force-no-bbl'? Will that*clear* the BBL so that I can
>> subsequently assemble it with '--update=bbl' without losing those
>> sectors again?
>
> A lot of people swear AT md badblocks. If you assemble with force
> no-bbl, the recommendation will be to NOT re-enable it.
>
> Personally, I'd recommend using dm-integrity rather than badblocks, but
> that (a) chews up some disk space, and (b) is not very well tested with
> mdraid at the moment.
>
> For example, md-raid should NEVER have any permanent bad blocks, because
> it's a logical layer, and the physical layer will fix it behind raid's
> back. But raid seems to accumulate and never clear bad-blocks ...
and why is that crap implemented in a way that replace a disk with bad
blocks don't reset the bad blocks for the given device?
that's pervert
prev parent reply other threads:[~2021-05-25 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 0:41 Spurious bad blocks on RAID-5 David Woodhouse
2021-05-25 16:49 ` antlists
2021-05-25 17:49 ` Reindl Harald [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=bb85ee01-f93e-8184-973d-1c46d56016fa@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=antlists@youngman.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-raid@vger.kernel.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.