From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: md resync ignoring unreadable sectors
Date: Sun, 08 Feb 2015 10:49:54 +1100 [thread overview]
Message-ID: <54D6A4A2.20909@eyal.emu.id.au> (raw)
In-Reply-To: <20150208040438.156a8554@natsu>
On 08/02/15 10:04, Roman Mamedov wrote:
> On Sun, 08 Feb 2015 09:39:47 +1100
> Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
>
>> The error did not show up during normal operation (or during scrub), only during the smartctl long test.
>> What triggered the error for you?
>
> Just appeared during boot-up after a reboot (after 50 days uptime) which was
> performed for some hardware upgrades (RAM, SATA controller). The error doesn't
> go away after swapping the SATA controller for different one.
>
>> I looked up the size of the different parts of the RAID to arrive at that conclusion. Dumping the sectors
>> around the bad area also showed it to be all zeroes.
>
> I wouldn't expect mdadm to have any headers or unused areas as far as 133 MB
> into a RAID member.
>
You can also read the earlier discussion starting 26/Feb/14:
Subject: how to handle bad sectors in md control areas?
cheers
--
Eyal Lebedinsky (eyal@eyal.emu.id.au)
next prev parent reply other threads:[~2015-02-07 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 21:47 md resync ignoring unreadable sectors Roman Mamedov
2015-02-07 22:39 ` Eyal Lebedinsky
2015-02-07 23:04 ` Roman Mamedov
2015-02-07 23:42 ` Phil Turmel
2015-02-07 23:49 ` Roman Mamedov
2015-02-07 23:43 ` Eyal Lebedinsky
2015-02-07 23:49 ` Eyal Lebedinsky [this message]
2015-02-08 17:23 ` 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=54D6A4A2.20909@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--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 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).