Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Semyon Enskiy <semyon.enskiy@yandex.ru>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Recovering RAID5 with 2, actually 1, faulty disks.
Date: Wed, 25 Nov 2015 11:58:57 -0500	[thread overview]
Message-ID: <5655E8D1.2050906@turmel.org> (raw)
In-Reply-To: <166511448468944@web24o.yandex.ru>

On 11/25/2015 11:29 AM, Semyon Enskiy wrote:
>>>  Maybe assemble command should include sdj3 device too?
>>>  Like
>>>  # mdadm -v --assemble --update=revert-reshape /dev/md3 /dev/sd[a-j]3
>>>  not
>>>  # mdadm -v --assemble --update=revert-reshape /dev/md3 /dev/sd[a-i]3
>>
>> Yes, my mistake. :-( Try again, including 'sdj3'.
>>
>> Phil
> 
> # mdadm -v --assemble --update=revert-reshape /dev/md3 /dev/sd[a-j]3
> mdadm: looking for devices for /dev/md3
> mdadm: superblock on /dev/sdj3 doesn't match others - assembly aborted
> 
> # mdadm -v --assemble --update=revert-reshape --force /dev/md3 /dev/sd[a-j]3
> mdadm: looking for devices for /dev/md3
> mdadm: superblock on /dev/sdj3 doesn't match others - assembly aborted
> 
> Note, that --examine in previous message shows delta devices value "-1" for
> all members of array, excepting sdj3, which has value "1", without minus
> symbol.

Hmmm. That's interesting.  That means mdadm wrote the revert-reshape
before it finished assembly.  Try this:

mdadm --stop /dev/md3

mdadm --assemble --update=revert-reshape /dev/md3 /dev/sdj3

That should fail w/ not enough to start, but apply the revert to that
one drive.  Then --stop again, and try with [a-j].

Phil


  reply	other threads:[~2015-11-25 16:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 15:28 Recovering RAID5 with 2, actually 1, faulty disks Semyon Enskiy
2015-11-23 15:35 ` Semyon Enskiy
2015-11-23 15:47   ` Wols Lists
2015-11-23 15:57     ` Semyon Enskiy
2015-11-23 16:08       ` Wols Lists
2015-11-23 18:24 ` Phil Turmel
2015-11-25 12:12   ` Semyon Enskiy
2015-11-25 13:22     ` Phil Turmel
2015-11-25 14:48       ` Semyon Enskiy
2015-11-25 14:55         ` Semyon Enskiy
2015-11-25 15:44           ` Phil Turmel
2015-11-25 16:29             ` Semyon Enskiy
2015-11-25 16:58               ` Phil Turmel [this message]
2015-11-25 17:32                 ` Semyon Enskiy
2015-11-25 17:49                   ` Phil Turmel
2015-11-26 13:21                     ` Semyon Enskiy
  -- strict thread matches above, loose matches on Subject: below --
2015-12-02 13:35 Semyon Enskiy

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=5655E8D1.2050906@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=semyon.enskiy@yandex.ru \
    /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