Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Charles Polisher <cpolish@surewest.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Reshape RAID10 -> RAID1
Date: Wed, 26 Feb 2014 18:03:17 +1100	[thread overview]
Message-ID: <20140226180317.10790f0e@notabene.brown> (raw)
In-Reply-To: <20140226060532.GA18630@kevin.peecee3.com>

[-- Attachment #1: Type: text/plain, Size: 1898 bytes --]

On Tue, 25 Feb 2014 22:05:32 -0800 Charles Polisher <cpolish@surewest.net>
wrote:

> Hi all,
> 
> I hope to reshape a RAID10 (near,2) with 2 failed and physically
> removed members [_U_U] into a RAID1 hopefully [UU], for the
> benefit of seeing a healthy status.
> 
> Is following proposed invocation correct?
> 
>    mdadm --grow /dev/md2 --level=1

I think so.  If not, mdadm will complain.

It is quite easy to experiment: create some largish file, use losetup to turn
them into block device.  Then experiment with /dev/loop*

NeilBrown


> 
> Details:
> 
> root@mencius $ mdadm --query --verbose --detail /dev/md2
> /dev/md2:
>         Version : 1.1
>   Creation Time : Fri Jul 15 22:56:53 2011
>      Raid Level : raid10
>      Array Size : 1944916992 (1854.82 GiB 1991.59 GB)
>   Used Dev Size : 972458496 (927.41 GiB 995.80 GB)
>    Raid Devices : 4
>   Total Devices : 2
>     Persistence : Superblock is persistent
> 
>   Intent Bitmap : Internal
> 
>     Update Time : Tue Feb 25 22:00:46 2014
>           State : active, degraded 
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
> 
>          Layout : near=2
>      Chunk Size : 512K
> 
>            Name : localhost.localdomain:2
>            UUID : 971ee8b2:8d980355:0e5dfae9:c8bccd89
>          Events : 5326341
> 
>     Number   Major   Minor   RaidDevice State
>        0       0        0        0      removed
>        1       8       19        1      active sync   /dev/sdb3
>        2       0        0        2      removed
>        3       8        3        3      active sync   /dev/sda3
> root@mencius $ uname -a
> Linux mencius 2.6.32-358.18.1.el6.centos.plus.x86_64 #1 SMP Wed Aug 28 16:14:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> root@mencius $ mdadm --version
> mdadm - v3.2.6 - 25th October 2012
> 
> 
> Thanks,


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-02-26  7:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  6:05 Reshape RAID10 -> RAID1 Charles Polisher
2014-02-26  7:03 ` NeilBrown [this message]
2014-02-26  7:20   ` Charles Polisher

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=20140226180317.10790f0e@notabene.brown \
    --to=neilb@suse.de \
    --cc=cpolish@surewest.net \
    --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