From: Michael Evans <mjevans1983@gmail.com>
To: "Michał Sawicz" <michal@sawicz.net>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: raid10 How do I tell what side of the mirror a disk is on?
Date: Fri, 29 Jan 2010 23:22:33 -0800 [thread overview]
Message-ID: <4877c76c1001292322u2f01d47auaa6041cd701e4176@mail.gmail.com> (raw)
In-Reply-To: <1264810392.1880.5.camel@michal-laptop.sawicz.net>
2010/1/29 Michał Sawicz <michal@sawicz.net>:
> Dnia 2010-01-30, sob o godzinie 00:50 +0100, Goswin von Brederlow pisze:
>> Does it matter? If one disk fails you know the next disk failure has a
>> 33+% chance of data loss and knowing which disk will be critical
>> doesn't
>> change that.
>
> For me it was important when I needed to have the array running (root
> fs) with only 2 disks out of 4 (not enough controllers). It would be
> nice to be able to tell which are mirrors, which are striped.
>
> --
> Cheers
> Michał (Saviq) Sawicz
>
As was noted in another reply recently; write down drive serial
numbers. Drive serial numbers can be obtained online via tools like
smartctl or hdparm (read their manuals, they're useful tools).
In your case you have a 50% chance of finding a working combination
the first time, and swapping only one cable from a disk that is
connected to one that's not would resolve the issue.
--
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-01-30 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 15:00 raid10 How do I tell what side of the mirror a disk is on? Rick Bragg
2010-01-29 23:50 ` Goswin von Brederlow
2010-01-30 0:13 ` Michał Sawicz
2010-01-30 7:22 ` Michael Evans [this message]
2010-01-30 14:09 ` Michał Sawicz
2010-01-30 11:01 ` Robin Hill
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=4877c76c1001292322u2f01d47auaa6041cd701e4176@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=michal@sawicz.net \
/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).