Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: "jdd@dodin.org" <jdd@dodin.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: fixing raid1
Date: Mon, 1 May 2017 22:19:54 +0500	[thread overview]
Message-ID: <20170501221954.52b2dd76@natsu> (raw)
In-Reply-To: <c416bcba-7a5d-a409-42ca-2eb82eca32b7@dodin.org>

On Mon, 1 May 2017 18:34:14 +0200
"jdd@dodin.org" <jdd@dodin.org> wrote:

> I have built a three disks raid1 on openSUSE 42.2. so far so good, all 
> worked perfectly
> 
> but later on I had no more use of the machine with as much disks, and 
> wanted to reclaim one disk. This one was in a esata dock.
> 
> At the moment I didn't found a way to make this cleanly (I found it it 
> too late in the linux raid wiki 
> https://raid.wiki.kernel.org/index.php/A_guide_to_mdadm#Removing_a_disk_from_an_array)
>
> so, I stopped the computer and removed the dock.
> 
> The computer rebooted perfectly, but in slightly degraded mode (see below)
> 
> I don't find a way to tell the system that it have to forget the third 
> disk. May be it's not necessary.

It appears you just need to do the 2nd step as listed in that wiki,

  mdadm --grow /dev/md127 --raid-devices=2

Did you try it? 

> # mdadm --detail /dev/md127
> /dev/md127:
>          Version : 1.0
>    Creation Time : Wed Dec 21 22:43:31 2016
>       Raid Level : raid1
>       Array Size : 976758592 (931.51 GiB 1000.20 GB)
>    Used Dev Size : 976758592 (931.51 GiB 1000.20 GB)
>     Raid Devices : 3
>    Total Devices : 2
>      Persistence : Superblock is persistent
> 
>    Intent Bitmap : Internal
> 
>      Update Time : Mon May  1 15:29:48 2017
>            State : clean, degraded
>   Active Devices : 2
> Working Devices : 2
>   Failed Devices : 0
>    Spare Devices : 0
> 
>             Name : any:jdd-raid
>             UUID : 4d57c009:5d7fc724:07376d9a:8ecb39a2
>           Events : 9592
> 
>      Number   Major   Minor   RaidDevice State
>         0       8        1        0      active sync   /dev/sda1
>         1       8       17        1      active sync   /dev/sdb1
>         -       0        0        2      removed
> --
> 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


-- 
With respect,
Roman

  reply	other threads:[~2017-05-01 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 16:34 fixing raid1 jdd
2017-05-01 17:19 ` Roman Mamedov [this message]
2017-05-01 17:43   ` jdd

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=20170501221954.52b2dd76@natsu \
    --to=rm@romanrm.net \
    --cc=jdd@dodin.org \
    --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