All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <alewis@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Mirroring a Drive for load-balancing AND failover
Date: Wed, 27 Jul 2005 09:24:40 -0500	[thread overview]
Message-ID: <20050727142440.GA4954@null.msp.redhat.com> (raw)
In-Reply-To: <42E786B9.2080400@mattgillen.net>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

On Wed, Jul 27, 2005 at 09:06:01AM -0400, Matthew Gillen wrote:
> Fury wrote:
> > I've racked my brain on this one, so hopefully someone will be of some help.
> > 
> > I'm trying to set up two servers which share a drive and do not have a
> > Single Point of Failure.  They are on a local network with each other.
> >  The best solution would be to have /dev/sda1 on one server mirrored
> > with /dev/sda1 on the second server.
> > ...
> > A second solution was to use GFS/GNBD.  I can export each drive to the
> > other server, and do RAID 1 (on both servers) between the local
> > /dev/sda1 and the remote gnbd device.  I then format the raid device
> > with GFS so both servers can mount it.
> > 
> > Surprisingly, this last system works.  Both systems can mount the
> > drive and read-write to it.  However, if either server in this
> > configuration drops dead, the other server cannot deal with the dead
> > gnbd device, and the raid device and mount point are no longer usable.
> >  I'm sure there are numerous other problems with this setup, also.
> > 
> > So I'm looking for ideas.  With two servers, how can I mirror a drive
> > in real-time, and allow for failover?
> 
> You might want to use something more like iSCSI + RAID:
> http://linux-iscsi.sourceforge.net/

How is that different than GNBD + RAID?  The issue isn't the network
transport, it's recovery of a RAID on two nodes simultaneously.

-- 
AJ Lewis                                   Voice:  612-638-0500
Red Hat                                    E-Mail: alewis@redhat.com
One Main Street SE, Suite 209
Minneapolis, MN 55414
   
Current GPG fingerprint = D9F8 EDCE 4242 855F A03D  9B63 F50C 54A8 578C 8715
Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the
many keyservers out there...


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-07-27 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  8:44 [linux-lvm] Mirroring a Drive for load-balancing AND failover Fury
2005-07-27 13:06 ` Matthew Gillen
2005-07-27 14:24   ` AJ Lewis [this message]
2005-07-27 17:20     ` Matthew Gillen
2005-07-27 20:10       ` Fury
2005-07-28 15:12         ` Jonathan E Brassow

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=20050727142440.GA4954@null.msp.redhat.com \
    --to=alewis@redhat.com \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.