All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Salatiel Filho <salatiel.filho@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Input/Output error reading from a clean raid
Date: Mon, 23 Jan 2017 18:34:11 +0100	[thread overview]
Message-ID: <20170123173411.GA9270@metamorpher.de> (raw)
In-Reply-To: <CAGmni9pazRfia++-s5Hn4FT+ubVzEhsnrQrKC3cSLja53-SizQ@mail.gmail.com>

On Mon, Jan 23, 2017 at 11:02:24AM -0300, Salatiel Filho wrote:
> mdadm mdadm --examine-badblocks /dev/sdd1 /dev/sdg1 /dev/sdf1  /dev/sde1
> 
> Bad-blocks on /dev/sdd1:
>           1515723072 for 512 sectors
> Bad-blocks on /dev/sde1:
>           1515723072 for 512 sectors

md believes you have bad blocks in identical places so it won't return 
whatever data is in these blocks. Thus you get read errors even if there 
is no bad block on the disk itself. Those bad block entries can be caused 
by cable or controller flukes, making temporary problems permanent...

Personally I disable the bad block list everywhere.

You can search this list for old messages regarding --examine-badblocks, 
this problem came up several times. Clearing the mdadm bad block list is 
worth a try. There's an undocumented option, update=force-no-bbl or such.

Regards
Andreas Klauer

  parent reply	other threads:[~2017-01-23 17:34 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 [this message]
2017-01-24 21:15       ` Salatiel Filho
2017-01-24 21:58         ` Wols Lists
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=20170123173411.GA9270@metamorpher.de \
    --to=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 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.