All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: Jonathan E Brassow <jbrassow@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: mirroring: [patch 1 of 8] device failure tolerance
Date: Thu, 30 Jun 2005 12:38:17 -0400	[thread overview]
Message-ID: <87f94c370506300938213c1ad8@mail.gmail.com> (raw)
In-Reply-To: <3333970fb0e372a4637169a2b97b46f7@redhat.com>

On 6/30/05, Jonathan E Brassow <jbrassow@redhat.com> wrote:
> 
> On Jun 30, 2005, at 10:13 AM, Greg Freemyer wrote:
> 
> > On 6/29/05, Jonathan E Brassow <jbrassow@redhat.com> wrote:
> >> This patch defines a couple more states that logs can return, and
> >> checks for those states in the mirror code.  The states are useful for
> >> logs that have cluster support.
> >>
> >>   brassow
> >
> > Have I been asleep?  This is the first I heard of DM having cluster
> > mirror support.  I assume the goal is something along the lines of
> > what DRBD provides.
> >
> > Can someone give a very high-level overview of current status, plans,
> > etc. related to DM Cluster Mirror support.  And if this related to the
> > DRBD project?
> 
> Please note that the "mirroring [patch x of 8]..." set for device fault
> tolerance has been replaced with the "mirroring [patch x of 6]..." set.
> 
> The cluster mirroring that I'm talking about is active/active and
> capable of handling more than 2 nodes.  It would be used in conjunction
> with a clustered file system - like GFS.  The application sitting on
> the cluster mirror should be cluster-aware.  You wouldn't be able to
> just put ext3 on there and expect it to work in a cluster capacity.
> 
> Although there are some minor things that need to happen in the mirror
> proper code (as can be seen from the smallness of the cluster patch),
> the heavy lifting is done by a cluster-aware log.  That is were you are
> keeping track of clean/dirty/recovering state.
> 
> An out-dated (but still useful for background) dock can be found at
> http://www.brassow.com/mirroring/index.html
> 
>   brassow
> 

Sounds like you have more ambitious plans than DRBD.   (They have
active-passive now and IIRC they plan the next major release to have
active-active, but I think only on 2 nodes.)

Is the GFS team planning on supporting this infrastructure.  I hope so.

Greg
-- 
Greg Freemyer
The Norcross Group
Forensics for the 21st Century

  reply	other threads:[~2005-06-30 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 18:07 mirroring: [patch 1 of 8] device failure tolerance Jonathan E Brassow
2005-06-30 11:33 ` Lars Marowsky-Bree
2005-06-30 11:33   ` [dm-devel] " Lars Marowsky-Bree
2005-06-30 15:13 ` Greg Freemyer
2005-06-30 15:38   ` Jonathan E Brassow
2005-06-30 16:38     ` Greg Freemyer [this message]
2005-06-30 18:00       ` 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=87f94c370506300938213c1ad8@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=jbrassow@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.