From: Neil Brown <neilb@suse.de>
To: Luca Berra <bluca@comedia.it>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [mdadm PATCH 5/9] mdmon: mdmon_pid should return pid from either dir
Date: Wed, 3 Mar 2010 17:55:54 +1100 [thread overview]
Message-ID: <20100303175554.54a91d49@notabene.brown> (raw)
In-Reply-To: <20100303064403.GB21832@maude.comedia.it>
On Wed, 3 Mar 2010 07:44:03 +0100
Luca Berra <bluca@comedia.it> wrote:
> On Wed, Mar 03, 2010 at 12:50:31PM +1100, Neil Brown wrote:
> >On Sun, 28 Feb 2010 15:43:40 +0100
> >Luca Berra <bluca@comedia.it> wrote:
> >
> >> mdmon_pid is called by mdmon_running to check if mdmon is running, so
> >> the pid file should be checked in either VAR_RUN or ALT_RUN
> >
> >I don't agree with this.
> >
> >The only time that any code should care about ALT_RUN is when mdmon is
> >starting. It chooses VAR_RUN or ALT_RUN to use, and possibly looks for an
> >old instance to kill.
> >
> >When starting mdmon without "--takeover", if it decided to use VAR_RUN, it
> >would not check ALT_RUN to see if an old mdmon was running. So I have
> >replaced you patch with a patch to include that extra check when starting
> >mdmon without --takeover.
> >Maybe that is the case you intended to address??
>
> No,
> the problem i try to address is in mdadm, not mdmon
> When mdadm needs to manage arrays with external metadata it will look
> for mdmon using mdmon_running(). If mdmon is running but did not yet
> take over mdadm will refuse to operate stating that mdmon is not
> running.
>
> I had to mount --bind ALT_RUN VAR_RUN in order to repair my imsm on
> sunday morning.
Ahhh..
I would rather you did
mdmon --takeover --all
which would effectively move the key fines from ALT_RUN to VAR_RUN.
Would that have worked in your case?
NeilBrown
next prev parent reply other threads:[~2010-03-03 6:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 15:05 [mdadm PATCH 0/2] *** mdmon fixes *** Luca Berra
2010-02-27 15:07 ` [mdadm PATCH 1/2] fix mdmon option parsing Luca Berra
2010-02-27 15:21 ` Luca Berra
2010-03-02 5:40 ` Neil Brown
2010-03-02 7:42 ` Luca Berra
2010-02-27 15:07 ` [mdadm PATCH 2/2] fix mdmon takeover Luca Berra
2010-03-03 0:52 ` Neil Brown
2010-02-28 14:41 ` [mdadm PATCH 0/2] *** mdmon fixes *** Luca Berra
2010-02-28 14:42 ` [mdadm PATCH 3/9] add missing newline to mdmon usage message Luca Berra
2010-02-28 14:42 ` [mdadm PATCH 4/9] mdmon: check select a writable pid_dir Luca Berra
2010-03-03 1:07 ` Neil Brown
2010-02-28 14:43 ` [mdadm PATCH 5/9] mdmon: mdmon_pid should return pid from either dir Luca Berra
2010-03-03 1:50 ` Neil Brown
2010-03-03 6:44 ` Luca Berra
2010-03-03 6:55 ` Neil Brown [this message]
2010-03-03 7:09 ` Luca Berra
2010-02-28 14:44 ` [mdadm PATCH 6/9] mdmon: connect_monitor should use socket " Luca Berra
2010-03-03 1:51 ` Neil Brown
2010-02-28 14:45 ` [mdadm PATCH 7/9] mdmon: move pid_dir to mdmon.c Luca Berra
2010-02-28 14:45 ` [mdadm PATCH 8/9] mdmon: rework startup and takeover logic Luca Berra
2010-03-03 1:52 ` Neil Brown
2010-03-03 6:48 ` Luca Berra
2010-02-28 14:46 ` [mdadm PATCH 9/9] allow redefinition of VAR_RUN Luca Berra
2010-03-03 1:53 ` Neil Brown
2010-02-28 15:41 ` [mdadm PATCH 0/2] *** mdmon fixes *** Bill Davidsen
2010-02-28 17:37 ` Luca Berra
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=20100303175554.54a91d49@notabene.brown \
--to=neilb@suse.de \
--cc=bluca@comedia.it \
--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).