From: Mike Hardy <mhardy@h3c.com>
To: linux-raid@vger.kernel.org
Subject: Re: Question: array locking, possible?
Date: Tue, 07 Feb 2006 10:16:20 -0800 [thread overview]
Message-ID: <43E8E3F4.1050409@h3c.com> (raw)
In-Reply-To: <20060207185517.7bc96486@mwdsp001.swissptt.ch>
Chris Osicki wrote:
>
> To rephrase my question, is there any way to make it visible to the
> other host that the array is up an running on the this host?
>
> Any comments, ideas?
Would that not imply an "unlock" command before you could run the array
on the other host?
Would that not then break the automatic fail-over you want, as no
machine that died or hung would issue the unlock command, meaning that
the fail-over node could not then use the disks
It's an interesting idea, I just can't think of a way to make it work
unattended
It might be possible wrap the 'mdadm' binary with a script that "checks"
(maybe via some deep check using ssh to execute remote commands, or just
a ping) the hosts status and just prints a little table of host status
that can only be avoided by passing a special --yes-i-know flag to the
wrapper
-Mike
next prev parent reply other threads:[~2006-02-07 18:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 17:55 Question: array locking, possible? Chris Osicki
2006-02-07 18:16 ` Mike Hardy [this message]
2006-02-08 10:49 ` Chris Osicki
2006-02-07 19:26 ` Paul Clements
2006-02-08 10:55 ` Chris Osicki
2006-02-08 20:45 ` Jure Pečar
2006-02-09 10:25 ` Chris Osicki
2006-02-10 0:00 ` Neil Brown
2006-02-10 17:17 ` Paul Clements
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 18:28 Stern, Rick (Serviceguard Linux)
2006-02-09 20:48 ` Luca Berra
2006-02-13 17:52 ` Chris Osicki
2006-02-13 21:53 ` Luca Berra
2006-02-13 22:54 ` Luca Berra
2006-02-13 17:12 ` Chris Osicki
2006-02-13 17:21 Stern, Rick (Serviceguard Linux)
2006-02-13 17:58 ` Chris Osicki
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=43E8E3F4.1050409@h3c.com \
--to=mhardy@h3c.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.