From: NeilBrown <neilb@suse.de>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Martin Wilck <mwilck@arcor.de>, linux-raid@vger.kernel.org
Subject: Re: mdadm 3.3: issue with mdmon --takeover
Date: Thu, 12 Sep 2013 15:03:31 +1000 [thread overview]
Message-ID: <20130912150331.254aba60@notabene.brown> (raw)
In-Reply-To: <CAC9WiBjsC1E2HV2vmiiKmGFXBBmZ+Rh0gktvxebKqZbKqD2hpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
On Wed, 11 Sep 2013 10:11:29 +0200 Francis Moreau <francis.moro@gmail.com>
wrote:
> On Wed, Sep 11, 2013 at 9:40 AM, Francis Moreau <francis.moro@gmail.com> wrote:
> [...]
> >>
> >> I think this patch will help. The last hunk in particular should make the
> >> difference.
> >>
> >> Please let me know if it fixes the problem.
> >>
> >
> > Yes it fixes the problem.
> >
> > I had to adjust the patch to make it compile by using be64_to_cpu()
> > where needed.
> >
>
> Hmm unfortunately the following test case seems broken too, I'm not
> sure it's related however:
>
> # create a ddf array containing loop0 and loop1
> $ cat /proc/mdstat
> Personalities : [raid1]
> md124 : active raid1 loop0[1] loop1[0]
> 84416 blocks super external:/md125/0 [2/2] [UU]
>
> md125 : inactive loop1[1](S) loop0[0](S)
> 65536 blocks super external:ddf
>
> # stop the array
> $ mdadm --stop /dev/md124
> mdadm: stopped /dev/md124
> $ mdadm --stop /dev/md125
> mdadm: stopped /dev/md125
>
> # Add only one disk
> $ mdadm -I /dev/loop0
> mdadm: container /dev/md/ddf1 now has 1 device
> mdadm: /dev/md/array1 assembled with 1 device but not started
>
> # start the array
> $ mdadm -R /dev/md124
Does
mdadm -IRs
work at this point?
If so, it is just a problem with my quick reimplementation of "-R".
I've made a note to look at it when I get a chance.
NeilBrown
>
> # looks like it failed
> $ cat /proc/mdstat
> Personalities : [raid1]
> md124 : inactive loop0[0]
> 84416 blocks super external:/md125/0
>
> md125 : inactive loop0[0](S)
> 32768 blocks super external:ddf
>
> # start mdmon manually with debug trace
> $ mdmon /dev/md125
> starting mdmon for md125
> monitor: wake ( )
> no arrays to monitor... exiting
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-09-12 5:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 15:54 mdadm 3.3: issue with mdmon --takeover Francis Moreau
2013-09-04 6:08 ` NeilBrown
2013-09-04 7:36 ` Francis Moreau
2013-09-05 2:11 ` NeilBrown
[not found] ` <CAC9WiBiHcS126iFv91250d83sMrBYmRbvoqYAEhjJWjb2p5J3A@mail.gmail.com>
2013-09-05 9:03 ` Francis Moreau
2013-09-10 23:35 ` NeilBrown
2013-09-11 7:40 ` Francis Moreau
2013-09-11 8:11 ` Francis Moreau
2013-09-12 5:03 ` NeilBrown [this message]
2013-09-12 7:40 ` Francis Moreau
2013-09-12 5:00 ` NeilBrown
2013-09-11 20:51 ` Martin Wilck
2013-09-12 4:59 ` NeilBrown
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=20130912150331.254aba60@notabene.brown \
--to=neilb@suse.de \
--cc=francis.moro@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mwilck@arcor.de \
/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).