From: "Doug Griswold" <griswld@cio.sc.gov>
To: linux-raid@vger.kernel.org
Subject: md multipath w/ 2 hba's
Date: Tue, 09 Sep 2003 14:14:07 -0400 [thread overview]
Message-ID: <sf5de036.073@gw.state.sc.us> (raw)
I don't know if this is exactly the right place to ask this question,
but here it goes. I have installed 2 emulex hbas in a red hat as2.1
server. I first saw duplicate paths to each lun. Now I am trying to
get failover paths to work so if one path goes down the other will pick
up. What I am seeing is the path to /dev/sdj is the only one working.
What I have done so far is edited my /etc/raidtab and put this entry in
raiddev /dev/md0
raid-level multipath
nr-raid-disks 2
chunk-size 4
persistent-superblock 1
device /dev/sdb
raid-disk 0
device /dev/sdj
raid-disk 1
1. I then issued mkraid /dev/md0
2. Made filesystem
3. edited fstab and mounted the filesystem but I don't have failover.
Here is my output from /proc/mdstat
md0 : active multipath sdj[0] sdb[1]
14226368 blocks [1/1] [U]
Is what I'm trying to do feasible or am I completely off track here.
If I am on track what have I missed.
Thanks,
Doug
reply other threads:[~2003-09-09 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sf5de036.073@gw.state.sc.us \
--to=griswld@cio.sc.gov \
--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).