From: Wols Lists <antlists@youngman.org.uk>
To: William Morgan <therealbrewer@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Two raid5 arrays are inactive and have changed UUIDs
Date: Wed, 15 Jan 2020 23:44:38 +0000 [thread overview]
Message-ID: <5E1FA3E6.2070303@youngman.org.uk> (raw)
In-Reply-To: <CALc6PW5Y-SvUZ5HOWZLk2YcggepUwK0N===G=42uMR88pDfAVA@mail.gmail.com>
On 15/01/20 22:12, William Morgan wrote:
> All 4 drives have the same event count and all four show the same
> state of AAAA, but the first and last drive still show bad blocks
> present. Is that because ddrescue copied literally everything from the
> original drives, including the list of bad blocks? How should I go
> about clearing those bad blocks? Is there something more I should do
> to verify the integrity of the data?
Read the wiki - the section on badblocks will be - enlightening - shall
we say.
https://raid.wiki.kernel.org/index.php/The_Badblocks_controversy
Yes, the bad blocks are implemented within md, so they got copied across
along with everything else. So your array should be perfectly fine
despite the badblocks allegedly there ...
Cheers,
Wol
next prev parent reply other threads:[~2020-01-15 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALc6PW4OKR2KVFgzoEbRJ0TRwvqi5EZAdC__HOx+vJKMT0TXYQ@mail.gmail.com>
[not found] ` <959ca414-0c97-2e8d-7715-a7cb75790fcd@youngman.org.uk>
2020-01-10 1:19 ` Two raid5 arrays are inactive and have changed UUIDs William Morgan
2020-01-10 1:55 ` Wols Lists
2020-01-13 22:40 ` William Morgan
2020-01-14 14:47 ` William Morgan
2020-01-14 15:23 ` Wols Lists
2020-01-15 22:12 ` William Morgan
2020-01-15 23:44 ` Wols Lists [this message]
2020-01-19 17:02 ` William Morgan
2020-01-19 17:07 ` William Morgan
2020-01-19 17:41 ` Wols Lists
2020-01-19 20:12 ` William Morgan
2020-01-19 21:10 ` Wol's lists
2020-01-24 14:10 ` Nix
2020-01-20 8:49 ` Robin Hill
2020-01-20 15:00 ` William Morgan
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=5E1FA3E6.2070303@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=therealbrewer@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;
as well as URLs for NNTP newsgroup(s).