From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: Trouble assembling multipath md devices between two nodes who see the same LUNs.
Date: Tue, 19 Apr 2005 09:20:36 +0200 [thread overview]
Message-ID: <20050419072036.GC29247@percy.comedia.it> (raw)
In-Reply-To: <11008ab4f.ab4f11008@bms.com>
On Mon, Apr 18, 2005 at 08:24:44PM -0400, Anu Matthew wrote:
>Thanks Larks. It is much appreciated.
>
>If the original metadata written by hostA changes by "mdadm --assemble" running on hostB, will mdmpd be able to recover the failed links on hostA when they re-surface? I am asking this because, I guess unless hostA goes down, hostA reflects the new metadata written by hostB. Will mdmpd take the new uuid into account?
DONT ACTIVATE THE ARRAY ON MORE THAN _1_ HOST AT THE SAME TIME.
whatever you do in the failover setup make it so that the md is
activated only on the active node.
>Not entirely OT, but devabel gets to the see the same uuid/serial numbers on the shared luns across hosts. It would have been cool if mdadm could too, right?
mdadm can use the UUID stored in the raid superblock, thus avoiding the
need to using devlabel (last time i looked at devlabel it was so buggy,
it could not make head or tails of a non partitioned disk)
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2005-04-19 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 0:24 Trouble assembling multipath md devices between two nodes who see the same LUNs Anu Matthew
2005-04-19 7:20 ` Luca Berra [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 21:14 Anu Matthew
2005-04-18 22:34 ` Lars Marowsky-Bree
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=20050419072036.GC29247@percy.comedia.it \
--to=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).