From: NeilBrown <neilb@suse.de>
To: George Shuklin <george.shuklin@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: how to get 'peer disk' in raid configuration?
Date: Thu, 28 Jun 2012 10:26:52 +1000 [thread overview]
Message-ID: <20120628102652.12521e0b@notabene.brown> (raw)
In-Reply-To: <4FEB9C69.9060608@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Thu, 28 Jun 2012 03:51:05 +0400 George Shuklin <george.shuklin@gmail.com>
wrote:
> Few days ago met intersting question:
>
> Let assume we have RAID10 on 4 disks. We want to remove two disks
> without breaking array.
>
> How we can know which drive is safe to eject? For 1st drive it obvious:
> any of. Second is more complicated: we need eject mirror part of 'second
> pair'.
Rules is simple. Don't remove adjacent devices (where the last is
considered to be adjacent to the first).
There are some pairs of adjacent devices that it is safe to remove, but it is
always safe to remove a device that is not adjacent to a removed devices.
>
> How we can know exact topology of raid? (--detail does not provide
> enough information, IMHO).
What - exactly - would you like to see in --detail.
Your answer must take into account the possibility of an odd number of
devices, of more than 2 copies of each block, and of near, far, and offset
modes.
(Patches preferred, but English-language descriptions are acceptable :-)
NeilBrown
> --
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-06-28 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 23:51 how to get 'peer disk' in raid configuration? George Shuklin
2012-06-28 0:26 ` NeilBrown [this message]
2012-06-28 4:37 ` George Shuklin
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=20120628102652.12521e0b@notabene.brown \
--to=neilb@suse.de \
--cc=george.shuklin@gmail.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).