From: Anu Matthew <anu.matthew@bms.com>
To: linux-raid@vger.kernel.org
Subject: Trouble assembling multipath md devices between two nodes who see the same LUNs.
Date: Mon, 18 Apr 2005 17:14:53 -0400 [thread overview]
Message-ID: <4264234D.7030703@bms.com> (raw)
Hello,
I have two nodes, hostA and hostB, both of them see the same 4 multipath
LUNs.
md0 to md4 are thus visible to both the hosts, (yeah, they both do not
write to thoe md devices at the same time, hostB mounts them only when
hostA is down or has crashed, and viceversa.)
It works for a while.
While testing, the latest we have seen is, after md devices are stopped
on hostA, hostB cannot start the md devices, as the uuid changes, and
comes back with a message in --verbose mode:
mdadm: /dev/sdc has wrong uuid
mdadm: no devices found for /dev/md0
Tried copying over the mdadm.conf with the latest uuids from hostA,
still hostB cannot assemble them. I have to re-create the md devices on
hostB eventually, then after a while, hostA starts to act up: it simply
refuses to assemble.
Is there a way I can circumvent this problem? I am running rhel 3.0 (AS
and ES), and we're on mdadm - v1.5.0 - 22 Jan 2004, from Redhat's
mdadm-1.5.0-9 rpm.
Thank you so much in advance,
--AM
next reply other threads:[~2005-04-18 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 21:14 Anu Matthew [this message]
2005-04-18 22:34 ` Trouble assembling multipath md devices between two nodes who see the same LUNs Lars Marowsky-Bree
-- strict thread matches above, loose matches on Subject: below --
2005-04-19 0:24 Anu Matthew
2005-04-19 7:20 ` 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=4264234D.7030703@bms.com \
--to=anu.matthew@bms.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).