All of lore.kernel.org
 help / color / mirror / Atom feed
From: Berkey B Walker <berk@panix.com>
To: Richard <richard@sauce.co.nz>
Cc: Kyler Laird <kyler-keyword-linuxraid00.a7e7f0@lairds.com>,
	linux-raid@vger.kernel.org
Subject: Re: recovering from a controller failure
Date: Sat, 29 May 2010 17:43:53 -0400	[thread overview]
Message-ID: <4C018A99.9030900@panix.com> (raw)
In-Reply-To: <4C01849D.8080101@sauce.co.nz>


Good find, Richard.  Simplifies things a lot.  I liked the phrase 
"Abusively looping"  , as that was a technique I used to use (30 yr. ago)
b-


Richard wrote:
> Kyler Laird wrote:
>
>> I'd like to know if this is something I can recover.  I do have backups
>> but it's a huge pain to recover this much data.
>
> This happened to me before I discovered that LSI SAS1068E no longer 
> reliably tolerate querying via smartd/smartctl.
>
> Have a look at https://bugzilla.kernel.org/show_bug.cgi?id=14831
>
> and there is a patch that seems to fix it here:
>
> http://lkml.org/lkml/2010/4/26/335
>
> Use hdparm if you need serial numbers.
>
> In the the half dozen or so tests I have done, where more than 2 
> drives have been thrown out of md RAID6 arrays due to these controller 
> resets,
> reassembly using --force has worked with no data corruption, but this 
> may have been good luck.
>
> Regards,
>
> Richard
> -- 
> 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
>

  parent reply	other threads:[~2010-05-29 21:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29 19:07 recovering from a controller failure Kyler Laird
2010-05-29 19:46 ` Berkey B Walker
2010-05-29 20:44   ` Kyler Laird
2010-05-29 21:18 ` Richard
2010-05-29 21:36   ` Kyler Laird
2010-05-29 21:38     ` Richard
2010-05-29 21:45       ` Kyler Laird
2010-05-29 21:50         ` Richard
2010-05-30  0:15           ` Kyler Laird
2010-05-30  0:28             ` Richard
2010-05-30  0:54               ` Richard
2010-05-30  3:33             ` Leslie Rhorer
2010-05-30 13:17               ` CoolCold
2010-05-30 22:38                 ` Leslie Rhorer
2010-05-31  8:33                   ` CoolCold
2010-05-31  8:50                     ` Leslie Rhorer
2010-05-30 18:55               ` Richard Scobie
2010-05-30 22:23                 ` Leslie Rhorer
2010-05-29 21:59         ` Richard
2010-05-29 21:43   ` Berkey B Walker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-31 18:27 Kyler Laird
2010-06-01 15:49 ` Kyler Laird
2010-06-01 19:15   ` Richard Scobie

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=4C018A99.9030900@panix.com \
    --to=berk@panix.com \
    --cc=kyler-keyword-linuxraid00.a7e7f0@lairds.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    /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.