From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: "David C. Rankin" <drankinatty@suddenlinkmail.com>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Feature request: Remove the badblocks list
Date: Wed, 2 Sep 2020 18:50:42 +0200 (CEST) [thread overview]
Message-ID: <482823895.1019975.1599065442417.JavaMail.zimbra@karlsbakk.net> (raw)
In-Reply-To: <319708c9-cfda-ca0f-9d68-330cac8b6d7a@websitemanagers.com.au>
> Based in the linked page, you would need to do something like this:
>
> 1) Create a clean array with correctly working disks
>
> 2) Tell the underlying block device to pretend there is a read error on
> a specific sector of one disk
>
> 3) Ask MD to replace the "bad" block device with a "good" one
Do you have a howto on 2,3?
> 4) See what happens with the BBL
>
> 5) Various steps of reading/writing to that specific stripe, and
> document the outcome/behavior
or this - how?
> 6) Replace another drive, and document the results
>
> Hint: there is a block device that could sit between your actual block
> device and MD, and it can "pretend" there are certain errors. The
> answers here seem to contain relevant information:
> https://stackoverflow.com/questions/1870696/simulate-a-faulty-block-device-with-read-errors
>
> As I said, I suspect that if a reproducible error is found, then it
> should be easier to fix the bug.
>
> OTOH, you could just remove the BBL from your arrays, and ensure you
> create new arrays without the BBL.
Anything better than just "mdadm ... --assemble --update=force-no-bbl"?
Vennlig hilsen
roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
Hið góða skaltu í stein höggva, hið illa í snjó rita.
next prev parent reply other threads:[~2020-09-02 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 18:00 Feature request: Remove the badblocks list Roy Sigurd Karlsbakk
2020-08-18 19:26 ` Wols Lists
2020-08-18 19:34 ` Piergiorgio Sartor
2020-08-18 19:43 ` Phil Turmel
2020-08-18 21:03 ` Håkon Struijk Holmen
2020-08-22 1:42 ` David C. Rankin
2020-09-02 13:36 ` Roy Sigurd Karlsbakk
2020-09-02 14:34 ` Adam Goryachev
2020-09-02 14:50 ` Roy Sigurd Karlsbakk
2020-09-02 15:09 ` Adam Goryachev
2020-09-02 15:25 ` Roy Sigurd Karlsbakk
2020-09-02 16:32 ` Adam Goryachev
2020-09-02 16:50 ` Roy Sigurd Karlsbakk [this message]
2020-09-02 19:45 ` Håkon Struijk Holmen
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=482823895.1019975.1599065442417.JavaMail.zimbra@karlsbakk.net \
--to=roy@karlsbakk.net \
--cc=drankinatty@suddenlinkmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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).