From: Roman Mamedov <rm@romanrm.net>
To: Dag Nygren <dag@newtech.fi>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 1 not fixing up sector errors?
Date: Fri, 15 Apr 2016 12:56:32 +0500 [thread overview]
Message-ID: <20160415125632.099c1fbd@natsu> (raw)
In-Reply-To: <29813347.d6oRyCVBGp@dag.newtech.fi>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Thu, 14 Apr 2016 16:03:59 +0300
Dag Nygren <dag@newtech.fi> wrote:
> Hi!
>
> Have set up a RAID1 here for temporary storage of some backup files.
> As I am using Seagate barracudas I am prepared for sector errors :-).
> that's why I am using RAID1.
>
> Anyway I do get those occasional "Pending Reallocate" with
> the appropriate corresponding
> Unrecovered read error - auto reallocate failed
> in the log.
>
> A resync of the array will rewrite the failing sector
> and the drive seems to reallocate it and all is fine again .
>
> But I was expecting the MD layer to try to fixup that sector
> automatically by using the data from the other drive ??
>
> Is there something I need to explicitly enable?
> Or am I expecting too much ;-)
I have seen this behavior too. The only somewhat logical explanation that I
have, is that some drives are only able to remap bad sectors if a larger area
around the sector is overwritten, and not just the sector itself. But this is
not scientific or verified.
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-04-15 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 13:03 RAID 1 not fixing up sector errors? Dag Nygren
2016-04-14 14:22 ` Andreas Klauer
2016-04-14 14:43 ` Dag Nygren
2016-04-14 14:56 ` Andreas Klauer
2016-04-15 7:56 ` Roman Mamedov [this message]
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=20160415125632.099c1fbd@natsu \
--to=rm@romanrm.net \
--cc=dag@newtech.fi \
--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 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.