All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Dunn <andrew.g.dunn@gmail.com>
To: linux-raid@vger.kernel.org, nfbrown@novell.com
Subject: Raid Degradation best practices
Date: Fri, 06 Nov 2009 07:47:55 -0500	[thread overview]
Message-ID: <4AF41AFB.3000302@gmail.com> (raw)

This morning my array lost a drive, then another. This was not due to
drive failures of hardware issues.

I did not have any data on the array so I wiped the drives and
re-created it. So far everything seems fine.

I would like to know what some of your practices are for the scenario
where you loose a drive or more on a mission critical array. I chose the
newbish route because I didn't have enough time or expertise to diagnose
the problems further. Typically this means it will happen again, and I
will still be unprepared.

Would appreciate your input, thanks.

-- 
Andrew Dunn
http://agdunn.net


             reply	other threads:[~2009-11-06 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 12:47 Andrew Dunn [this message]
2009-11-07 11:51 ` Raid Degradation best practices Justin Piszcz
2009-11-07 13:12   ` Andrew Dunn
2009-11-07 15:02     ` Goswin von Brederlow

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=4AF41AFB.3000302@gmail.com \
    --to=andrew.g.dunn@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=nfbrown@novell.com \
    /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.