From: Richard Scobie <richard@sauce.co.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: RAID1 == two different ARRAY in scan, and Q on read error corrected
Date: Sat, 19 Apr 2008 10:02:15 +1200 [thread overview]
Message-ID: <48091A67.1090906@sauce.co.nz> (raw)
In-Reply-To: <27567.1208547359@perkpartners.com>
Phil Lobbes wrote:
____________________________________________________________
>
> Apr 15 11:07:14 kernel: raid1: sdc1: rescheduling sector 517365296
> Apr 15 11:07:54 kernel: raid1:md0: read error corrected (8 sectors at 517365296 on sdc1)
> Apr 15 11:07:54 kernel: raid1: sdc1: redirecting sector 517365296 to another mirror
> Apr 15 11:08:32 kernel: raid1: sdc1: rescheduling sector 517365472
> Apr 15 11:09:09 kernel: raid1:md0: read error corrected (8 sectors at 517365472 on sdc1)
> Apr 15 11:09:09 kernel: raid1: sdc1: redirecting sector 517365472 to another mirror
These entries,
> Apr 18 14:01:45 smartd[2104]: Device: /dev/sdc, 3 Currently unreadable (pending) sectors
and this, indicate that sdc is losing sectors, so you probably want a
backup of the array.
Depending on how important the array is you could fail and remove sdc
from the array, dd if=/dev/zero of=/dev/sdc bs=1M and re-add it back.
It may then be fine for some time, but if it continues to gather pending
sectors in the short term, it is probably dying.
Otherwise just replace it with a new one.
Regards,
Richard
next prev parent reply other threads:[~2008-04-18 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 19:35 RAID1 == two different ARRAY in scan, and Q on read error corrected Phil Lobbes
2008-04-18 22:02 ` Richard Scobie [this message]
2008-04-18 23:49 ` David Lethe
2008-04-19 3:15 ` Richard Scobie
2008-04-19 17:26 ` Phil Lobbes
2008-04-19 19:58 ` Richard Scobie
2008-04-19 20:43 ` David Lethe
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=48091A67.1090906@sauce.co.nz \
--to=richard@sauce.co.nz \
--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).