linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Stuart D. Gathman" <stuart@bmsi.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM + raid + san
Date: Sun, 7 Nov 2010 17:27:53 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1011071710110.20225@bmsred.bmsi.com> (raw)
In-Reply-To: <4CD5F804.3040906@cfl.rr.com>

On Sat, 6 Nov 2010, Phillip Susi wrote:

> My understanding of a SAN is where you get a few drive enclosures and a few
> servers and plug them all into a sas expander so all of the servers can see
> all of the disks.  You seem to be talking about having all of the disks on one
> server that then serves them over ethernet with iscsi.  I wouldn't want to do
> that because it adds a good deal of overhead to the disk access and introduces
> a single point of failure.

Your idea is not typical for SAN, where the point is to centralize dealing with
physical disks. The SAN server can be internally highly redundant, addressing
the single point of failure issue.  

However, thinking how to do what you want, how about getting enclosures with
built in RAID?  For instance, There are low cost NAS and USB enclosures with
built in RAID-1.  Perhaps there are some more expensive ones with RAID 10.
(I still wouldn't use RAID5).  Then you can just use them with LVM without
as much worry about disk failure.  If an enclosure fails, however, that
PV will be offline (disrupting your service) until you replace it (moving
disks to new enclosure - so you don't lose data, other than the chaos from
any LVs that are partially offline).

> I'd rather just use LVM to manage all of the disks as part of a single volume
> group so you can immediately transfer a lv from one server to another, but I
> can't work out how to still manage to get raid without having lvm do it with
> the dm-raid5 support.

You'd have some serious locking issues.  With RAID5, each server would have to
lock each chunk before writing to it (which involves a read/modify/write
cycle).  This would create serious overhead.  And you were complaining about
SAN server overhead! :-)  RAID5 *must* be centralized.  Your scheme might work
with RAID10, but then you'd still have to ensure that writes to mirror legs
don't get out of order, with updates from multiple servers flying over the
wire.

I still think you want a traditional SAN with an enterprise SAN server with
lots of built in redundancy (or build your own .  You'll help feed the family
of a hard working salesman :-)

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

  parent reply	other threads:[~2010-11-07 22:28 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 [this message]
2010-11-09 22:15       ` Stuart D. Gathman
2010-11-10  0:21         ` Phillip Susi

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=Pine.LNX.4.64.1011071710110.20225@bmsred.bmsi.com \
    --to=stuart@bmsi.com \
    --cc=linux-lvm@redhat.com \
    --cc=psusi@cfl.rr.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).