From: Andrew Dunn <andrew.g.dunn@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, nfbrown@novell.com
Subject: Re: Raid Degradation best practices
Date: Sat, 07 Nov 2009 08:12:55 -0500 [thread overview]
Message-ID: <4AF57257.7010207@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0911070650380.4559@p34.internal.lan>
I am using RAID6, on 9 WD1001FALS drives.
The VERY important data is backed up to multiple external drives and
stored at a separate location.
I figured out my issue last night. I had an issue with the array where
it was doing the silly /dev/md_d0 thing, so when I stopped that and
started the new one I did '--assume-clean' then when I started copying
my information back to the array multiple devices dropped out. Their
SMART information passes just fine, so it must have been the array was
not clean.
This was my mistake, but in the future when I have a real drive failure
I was curious to see how you approach that issue.
Thanks,
Justin Piszcz wrote:
>
>
> On Fri, 6 Nov 2009, Andrew Dunn wrote:
>
>> 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
>>
>> --
>> 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
>>
>
> How did you lose the drives then?
>
> If it is a mission-critical array, what RAID type are you using?
>
> Are you backing up the data regularly, since it is mission-critical?
>
> Justin.
>
--
Andrew Dunn
http://agdunn.net
next prev parent reply other threads:[~2009-11-07 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 12:47 Raid Degradation best practices Andrew Dunn
2009-11-07 11:51 ` Justin Piszcz
2009-11-07 13:12 ` Andrew Dunn [this message]
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=4AF57257.7010207@gmail.com \
--to=andrew.g.dunn@gmail.com \
--cc=jpiszcz@lucidpixels.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 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).