From: Arthur Britto <ahbritto@iat.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: End to end SMART to RAID repair
Date: Mon, 23 Jun 2008 17:05:44 -0700 [thread overview]
Message-ID: <1214265944.31695.25.camel@loss.redstem.com> (raw)
In-Reply-To: <18528.10923.329740.465179@notabene.brown>
On Tue, 2008-06-24 at 08:58 +1000, Neil Brown wrote:
> On Sunday June 22, ahbritto@iat.com wrote:
> > smartmontools (http://smartmontools.sourceforge.net/) can be configured
> > to passively scan hard drives for defects in the background. The block
> > numbers of pending unreadable sectors are logged via syslog. These
> > sectors will be remapped when written too.
> >
> > It would be great if this worked end to end with linux software raid to
> > automatically repair the bad sector.
>
> Well, you can just get md to do a scan (echo check >
> /sys/block/mdXX/md/sync_action) and it will find any read errors and
> correct them.
True. However, a SMART on disk check requires no main board
resources. Some drives, when idle, may do background checking anyway.
This would provide a way to correct the error without needing to scan
the whole volume and other components with an md check. Error checking
may be less intrusive (vs retries to the exclusion of other work) than
normal for an attempted sector read. At least manufactures have the
option to give priority to actual read requests over background defect
checking.
> Extracting numbers from syslog is a fairly messy thing to try to do.
> Maybe if smartmontools could report these in some other way -
> e.g. run a program giving device and block number, we could write a
> script that feeds that info to md.
> We would need to map the device+offset to partition+offset, then find
> out if that is a member of an md array, then request a limited-range
> 'check', which I think is possible with current code...
>
> Do you know if smartmontools can provide this info in a more
> controlled way?
I was thinking, a non-smartmontools specific method would be best. That
is: (1) some way for the md driver to request notification about pending
uncorrected read errors from a region of a block device and (2) some way
for a trusted application to inform the kernel about pending uncorrected
read errors (e.g. echo "start-stop > /sys/...").
-Arthur
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2008-06-24 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1214199855.4296.8.camel@loss.redstem.com>
[not found] ` <18528.10923.329740.465179@notabene.brown>
2008-06-24 0:05 ` Arthur Britto [this message]
2008-06-24 11:24 ` End to end SMART to RAID repair Ric Wheeler
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=1214265944.31695.25.camel@loss.redstem.com \
--to=ahbritto@iat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).