From: Michael Evans <mjevans1983@gmail.com>
To: Anshuman Aggarwal <anshuman@brillgene.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: 4 partition raid 5 with 2 disks active and 2 spare, how to force?
Date: Thu, 25 Mar 2010 20:38:27 -0700 [thread overview]
Message-ID: <4877c76c1003252038o655b2a29p9d994df27b5d2afd@mail.gmail.com> (raw)
In-Reply-To: <DFC0232A-8DCD-4815-AA08-DA7065F01221@brillgene.com>
On Thu, Mar 25, 2010 at 7:09 AM, Anshuman Aggarwal
<anshuman@brillgene.com> wrote:
> Thanks Michael, I am clear about the problem of why the multiple failure would cause me to lose data. Which is why I wanted to consult this mailing list before proceeding.
>
> Could you tell me how to keep the array read-only? and mark one or both of these spares as active forcibly? and Also, once I am able to use these spares as active and the data is not consistent in a particular stripe, how does the kernel resolve the inconsistency (as in what data does it use, the one based on the data stripes or the one based on the parity?) this one is just academic interest since it'll be difficult to figure out which is the right data anyways.
>
> Thanks,
> Anshuman
>
Please, read the wikipedia page first,
http://en.wikipedia.org/wiki/RAID
and then this
http://wiki.tldp.org/LVM-on-RAID (some links need updating, but it's
still up to date for concepts)
With that background nearly out of the way, please stop, and read them
both again. Yes, seriously. In order to prevent data loss you'll
need to have a good understanding of what RAID does, so that you can
watch out for ways it can fail.
The next step, before we do /anything/ else is for you to post the
COMPLETE output of these commands.
mdadm -Dvvs
mdadm -Evvs
They will help everyone on the list better understand the state of the
metadata records and what potential solutions might be possible.
--
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
next prev parent reply other threads:[~2010-03-26 3:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1753093Ab0CYHZE/20100325072504Z+37@vger.kernel.org>
2010-03-25 9:30 ` 4 partition raid 5 with 2 disks active and 2 spare, how to force? Anshuman Aggarwal
2010-03-25 11:37 ` Michael Evans
2010-03-25 14:09 ` Anshuman Aggarwal
2010-03-26 3:38 ` Michael Evans [this message]
2010-03-26 16:28 ` Anshuman Aggarwal
2010-03-26 19:04 ` Michael Evans
2010-03-28 15:18 ` Anshuman Aggarwal
2010-03-28 16:35 ` Anshuman Aggarwal
2010-03-29 5:32 ` Luca Berra
2010-03-29 6:41 ` Michael Evans
2010-04-06 18:07 ` linux raid recreate Anshuman Aggarwal
2010-04-06 22:55 ` Neil Brown
2010-04-07 0:24 ` Berkey B Walker
2010-04-07 7:27 ` Anshuman Aggarwal
2010-04-07 13:15 ` Neil Brown
2010-03-26 19:29 ` 4 partition raid 5 with 2 disks active and 2 spare, how to force? John Robinson
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=4877c76c1003252038o655b2a29p9d994df27b5d2afd@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=anshuman@brillgene.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).