From: Wols Lists <antlists@youngman.org.uk>
To: Salatiel Filho <salatiel.filho@gmail.com>,
Andreas Klauer <Andreas.Klauer@metamorpher.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Input/Output error reading from a clean raid
Date: Tue, 24 Jan 2017 21:58:56 +0000 [thread overview]
Message-ID: <5887CE20.1020606@youngman.org.uk> (raw)
In-Reply-To: <CAGmni9qF_LjdzYtsMJ9YmHoymG=SN6p2Mta-COEhbyReQFbNTA@mail.gmail.com>
On 24/01/17 21:15, Salatiel Filho wrote:
> I really think it is very unlikely that two different disks from two
> different brands would have problems at exactly the same block.
> I have a question, who populates the badblock list ? Is the check
> action send to the /sys/block/md??/md/sync_action OR each read error
> updates it ?
I think it's a known problem - nobody seems to know quite why it happens
but when a block is added to the badblocks list it seems to get added to
every device. Given that modern hard-drives are supposed to relocate bad
blocks and not need a badblock list, I think that's why it's not been
found, most people especially those in the know just tend to disable
os-level badblocks.
Cheers,
Wol
next prev parent reply other threads:[~2017-01-24 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 14:08 Input/Output error reading from a clean raid Salatiel Filho
2017-01-23 0:18 ` John Stoffel
2017-01-23 14:42 ` Salatiel Filho
2017-01-23 16:12 ` John Stoffel
[not found] ` <20170123010334.GA7546@metamorpher.de>
2017-01-23 14:02 ` Salatiel Filho
2017-01-23 17:07 ` John Stoffel
2017-01-23 17:23 ` Wols Lists
2017-01-23 17:34 ` Andreas Klauer
2017-01-24 21:15 ` Salatiel Filho
2017-01-24 21:58 ` Wols Lists [this message]
2017-01-25 15:54 ` John Stoffel
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=5887CE20.1020606@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=Andreas.Klauer@metamorpher.de \
--cc=linux-raid@vger.kernel.org \
--cc=salatiel.filho@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).