linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anu Matthew <anu.matthew@bms.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Trouble assembling multipath md devices between two nodes who see the same LUNs.
Date: Mon, 18 Apr 2005 20:24:44 -0400	[thread overview]
Message-ID: <11008ab4f.ab4f11008@bms.com> (raw)

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? 

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?

Thanks,

Anu Matthew 

<snip>
> On 2005-04-18T17:14:53, Anu Matthew 
> 
> md multipath has on-disk metadata and modifies it. md is NOT
> cluster-safe for concurrent activation.
> 
> 
> Sincerely,
>    Lars Marowsky-Brée <lmb@suse.de>
> 
> -- 
> High Availability & Clustering
> SUSE Labs, Research and Development
> SUSE LINUX Products GmbH - A Novell Business
</snip> 

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2005-04-19  0:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  0:24 Anu Matthew [this message]
2005-04-19  7:20 ` Trouble assembling multipath md devices between two nodes who see the same LUNs Luca Berra
  -- 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=11008ab4f.ab4f11008@bms.com \
    --to=anu.matthew@bms.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lmb@suse.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).