From: NeilBrown <neilb@suse.de>
To: Francis Moreau <francis.moro@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: question about mdmon --takeover
Date: Mon, 5 Aug 2013 16:59:08 +1000 [thread overview]
Message-ID: <20130805165908.2d1e291b@notabene.brown> (raw)
In-Reply-To: <CAC9WiBgFPSeKGBYxYCkw8DHk4dS6=aBhCeiMGgkj2eNgtY0asw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On Wed, 31 Jul 2013 16:30:34 +0200 Francis Moreau <francis.moro@gmail.com>
wrote:
> Hello list,
>
> I thought that using "--takeover" would hint mdmon to replace existing
> mdmon process, and therefore the old one would exit somehow.
>
> However after several "mdmon --takeover" I can see this:
> $ ps aux | grep dmon
> root 233 0.0 0.2 80388 10752 ? SLsl 14:02 0:00 @dmon
> --offroot md127
> root 3326 0.0 0.2 14920 10820 ? SLsl 15:16 0:00 mdmon
> --takeover md127
> root 3343 0.0 0.2 14920 10820 ? SLsl 15:17 0:00 mdmon
> --takeover md127
>
> Is this expected ?
>
> Thanks.
Nope. That's not expected.
mdmon should send SIGTERM to the old mdmon and then wait for it to exit.
If the new and old mdmon were compiled different and look for the pid file in
different directories that might explain what you see.
If you compile mdadm from source it will use /run/mdadm. However if your
distro doesn't have /run the the distro-provided mdadm will be compiled
differently.
It is safe to kill the old mdmons once a new one is running, but you should
probably find out what the incompatibility is...
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-05 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 14:30 question about mdmon --takeover Francis Moreau
2013-08-05 6:59 ` NeilBrown [this message]
2013-08-28 17:14 ` Francis Moreau
2013-08-28 19:42 ` Francis Moreau
2013-08-31 20:21 ` Francis Moreau
2013-09-02 2:04 ` NeilBrown
2013-09-02 7:56 ` Francis Moreau
2013-09-02 8:10 ` NeilBrown
2013-09-02 8:27 ` Francis Moreau
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=20130805165908.2d1e291b@notabene.brown \
--to=neilb@suse.de \
--cc=francis.moro@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).