From: Bill Davidsen <davidsen@tmr.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Multipath and nbd
Date: Thu, 25 Oct 2007 11:08:56 -0400 [thread overview]
Message-ID: <4720B188.7050503@tmr.com> (raw)
I am at the design stage for a new server. That's when you try to
convince a client that they have an unfavorable ratio of requirements to
budget. I am thinking a raid-1, with a mirror to an nbd device running
write-mostly. I will have redundant network paths to the other machine,
one via a dedicated cable and P-t-P connection, and the other via a
switch going to the general internal network.
Am I going into deep waters to try and do something helpful with
multipath features here, or should I stick to a network only solution,
and give the switched route a higher metric to force traffic through the
dedicated link?
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
reply other threads:[~2007-10-25 15:08 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=4720B188.7050503@tmr.com \
--to=davidsen@tmr.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).