From: Phillip Susi <psusi@cfl.rr.com>
To: "Stuart D. Gathman" <stuart@bmsi.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM + raid + san
Date: Tue, 09 Nov 2010 19:21:13 -0500 [thread overview]
Message-ID: <4CD9E579.8070507@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1011091705030.27920@bmsred.bmsi.com>
On 11/09/2010 05:15 PM, Stuart D. Gathman wrote:
> Actually, this would be an interesting driver to develop. If each
> server primarily works on its own LV, then there shouldn't be much
I think the existing dm raid driver would work for this; it just needs
to be finished and integrated with lvm. Unlike mdadm, the dm raid
driver is only activated on the physical extents of the physical volumes
that make up the logical volume, rather than the whole disk or
partition, so each host should be able to use the cluster locking daemon
to make sure only one activates any given lv at a time. If a server
goes down then another can activate the lv and take over.
> It is an interesting idea to avoid a traditional SAN as a single point of
> failure (the switch connecting the hosts and disks would still be a single
> point of failure, but a switch is simpler than a SAN server). All hosts would
> have to be trusted.
And switches can be redundant. I understand that at least some sas
drives have two redundant ports that can each be connected to a
different expander and the servers can be connected to both expanders.
prev parent reply other threads:[~2010-11-10 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 1:26 [linux-lvm] LVM + raid + san Phillip Susi
2010-11-05 4:39 ` Stuart D. Gathman
2010-11-07 0:51 ` Phillip Susi
2010-11-07 3:38 ` Eugene Vilensky
2010-11-07 4:03 ` allan
2010-11-07 19:55 ` Phillip Susi
2010-11-07 22:27 ` Stuart D. Gathman
2010-11-09 22:15 ` Stuart D. Gathman
2010-11-10 0:21 ` Phillip Susi [this message]
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=4CD9E579.8070507@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-lvm@redhat.com \
--cc=stuart@bmsi.com \
/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).