linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: How to un-degrade an array after a totally spurious failure?
Date: Mon, 8 Jun 2009 08:51:36 +0100	[thread overview]
Message-ID: <20090608075136.GA3000@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <20090608015637783.ESCT2045@cdptpa-omta01.mail.rr.com>

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

On Sun Jun 07, 2009 at 08:56:42PM -0500, Leslie Rhorer wrote:

> > -----Original Message-----
> > From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
> > owner@vger.kernel.org] On Behalf Of Carlos Carvalho
> > Sent: Sunday, June 07, 2009 8:54 PM
> > To: linux-raid@vger.kernel.org
> > Subject: RE: How to un-degrade an array after a totally spurious failure?
> > 
> > Leslie Rhorer (lrhorer@satx.rr.com) wrote on 7 June 2009 20:43:
> >  >OK, what about a RAID 6 array with one failed disk?  Is the remove & add
> >  >the best option there, or should one apply a different method?
> > 
> > It is, since that's what the raid is for. It's still operational.
> > We've done it here and it works.
> 
> Well, yes, I know it should work.  The question is, "Is it the best method?"
> 
Yes - as the array is still active then it's likely to have changed
since the drive failed.  This means that stopping the array and
re-assembling, forcing the failed drive active, could lead to
corruption.  Removing & adding it will ensure the data is updated to
match the current array state.

Of course, neither option should be pursued unless you know _exactly_
why the drive failed and know that it's safe to re-add it to the array.

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

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

  reply	other threads:[~2009-06-08  7:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 23:10 How to un-degrade an array after a totally spurious failure? Nix
2009-05-21  2:49 ` NeilBrown
2009-05-21  7:32   ` Nix
2009-05-26  8:25   ` Leslie Rhorer
2009-05-26 10:47     ` NeilBrown
2009-06-08  1:43       ` Leslie Rhorer
2009-06-08  1:54         ` Carlos Carvalho
2009-06-08  1:56           ` Leslie Rhorer
2009-06-08  7:51             ` Robin Hill [this message]
2009-06-08 13:12               ` Carlos Carvalho
2009-06-09  1:55                 ` Leslie Rhorer
2009-08-03  7:30       ` Leslie Rhorer
2009-08-03  7:43         ` NeilBrown
2009-08-03  8:28           ` Leslie Rhorer
2020-01-12  9:48 ` mdadm not sending email Leslie Rhorer
2020-01-12 12:47   ` John Stoffel
2020-01-13 14:00     ` Leslie Rhorer
2020-01-29 20:46       ` Leslie Rhorer
     [not found]         ` <CALc6PW4mf0kkU2y8mPvQsM3N-EMG2kLV3Y9-8EV-XQgLBmy_YA@mail.gmail.com>
2020-01-30 22:14           ` Leslie Rhorer

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=20090608075136.GA3000@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --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).