From: Priya Kamala <priya.kamala@perpetual-data.com>
To: linux-raid@vger.kernel.org
Subject: Re: Query regarding disk failure
Date: Wed, 10 Jul 2013 15:17:43 +0100 [thread overview]
Message-ID: <51DD6D07.1060401@perpetual-data.com> (raw)
In-Reply-To: <20130710131119.GA26658@cthulhu.home.robinhill.me.uk>
On 10/07/2013 14:11, Robin Hill wrote:
> If the check/repair process finds a read error, it will trigger a
> rewrite of the affected block (rebuilding the data from the other
> drives). If the write fails then the disk will be removed from the RAID.
> This shouldn't happen, as the disk should either succeed in the write,
> or should remap the bad block with one of its spares.
>
> If you're getting repeated problems with this, it's likely that you are
> using consumer-level drives without TLER/ERC and have failed to adjust
> the kernel timeouts to compensate for this. In this case the rewrite
> will be triggered while the disk is still attempting the read process
> and will therefore be ignored, causing the write to fail and the disk to
> be removed.
>
Thank you for the quick response. The drives in question do support ERC.
I have some additional questions. Is the drive status changed to an
underscore in /proc/mdstat during this remap process?
This is an extract from the system log:
Apr 4 07:44:02 src@AA20NOV sd 8:0:0:0: SCSI error: return code = 0x08000002
Apr 4 07:44:02 src@AA20NOV sde: Current: sense key: Medium Error
Apr 4 07:44:02 src@AA20NOV Additional sense: No additional sense
information
Apr 4 07:44:02 src@AA20NOV Info fld=0x620cb71
Apr 4 07:44:02 src@AA20NOV end_request: I/O error, dev sde, sector
102812529
Apr 4 07:44:02 src@AA20NOV raid5:md3: read error corrected (8 sectors
at 86035184 on sde5)
Apr 4 07:44:02 src@AA20NOV raid5:md3: read error corrected (8 sectors
at 86035192 on sde5)
Apr 4 07:44:05 src@AA20NOV raid5: Disk failure on sde5, disabling
device. Operation continuing on 4 devices
Apr 4 07:44:05 src@AA20NOV md: cannot remove active disk sde5 from md3 ...
We have a service which monitors the md RAID status and tries to remove
failed disks from degraded RAIDs and it looks like that failed since the
device is active. But why would it still be active when the previous
line says that the device is being disabled?
Thanks,
Priya
next prev parent reply other threads:[~2013-07-10 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 12:09 Query regarding disk failure Priya Kamala
2013-07-10 13:11 ` Robin Hill
2013-07-10 14:17 ` Priya Kamala [this message]
2013-07-10 14:51 ` Phil Turmel
2013-07-10 15:11 ` Priya Kamala
2013-07-10 15:22 ` Phil Turmel
2013-07-10 15:45 ` Priya Kamala
2013-07-10 17:30 ` Phil Turmel
2013-07-10 17:47 ` Mikael Abrahamsson
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=51DD6D07.1060401@perpetual-data.com \
--to=priya.kamala@perpetual-data.com \
--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.