linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: keld@keldix.com
Cc: linux-raid@vger.kernel.org
Subject: Re: self healing of MD raid
Date: Tue, 2 Jun 2015 18:53:39 +0100	[thread overview]
Message-ID: <20150602175339.GA20741@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <20150602172236.GA23446@www5.open-std.org>

[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]

On Tue Jun 02, 2015 at 07:22:36PM +0200, keld@keldix.com wrote:

> Hi list
> 
> I wonder if MD RAID software is kind of self healing.
> That is, if a read operation gets an IO error, then the logical
> sector of the RAID can be recreated from the other sector(s)
> of the raid, and then written out on the block which gave a read error.
> 
> His could work both for the mirrored RAID types, and for the
> parity orientet RAID types.
> 
> Is that implemented in MD RAID?
> 
> Similarily the self healing process could be part of the monitoring
> background processes.
> 
> Best regaqrds
> keld

Yes, this is implemented as standard for all forms of RAID with
redundant data (parity/mirror). A read error will automatically trigger
a rewrite of the faulty block with data recovered from the other
members. This rewrite should also trigger a remapping within the drive
if the original block proves to be unwritable as well.

Running a regular check (echo check > /sys/block/mdX/md/sync_action)
will do a full read of all active members in an array and therefore
trigger rewrites for any unreadable blocks. This is often set up as part
of the standard distro cron jobs, but should be set up manually if not.

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-06-02 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 17:22 self healing of MD raid keld
2015-06-02 17:53 ` Robin Hill [this message]
2015-06-02 18:01   ` Alireza Haghdoost
2015-06-02 19:14     ` Robin Hill

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=20150602175339.GA20741@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --cc=keld@keldix.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 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).