All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graham Wood <gwood@dragonhold.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: RE: [linux-lvm] Mirror between different SAN fabrics
Date: Thu, 28 Dec 2006 11:09:44 +0000	[thread overview]
Message-ID: <20061228110944.5gxv84tcg8ggg08w@www.dragonhold.org> (raw)
In-Reply-To: <OF00509E1D.6C564DF2-ONC1257252.003B531C-C1257252.003C0B39@schering.de>


> I haven't tried it in a cluster yet. I was planning on using HP's
> MC-ServiceGuard to deal with HA clustering. I don't see why the LUNs that
> are used on one system with mdadm can't be used another, since the RAID
> block is on the disk and is readable even on a system upon which it wasn't
> created on. /etc/mdadm.conf will ofcourse need to be copied and kept
> current on all cluster nodes, but with the config file and the RAID block
> on the disk, an "mdadm --assemble" should work. Importing the LVM
> structures should then also not be a problem.
Assuming that the underlying devices are "clean" this may indeed  
work... Sometimes.

However, things like the dirty region log are going to be a mess.

Imagine that you've got apache running on node 1 using one GFS volume,  
and mysql on the second using another - both backed onto the same md  
physical volume.  They will each be writing to the same DRL their  
dirty regions, and trampling all over each other's status information.

Then node2 crashes with some IO in progress.  In the time taken for it  
to reboot, the DRL could have been totally over-written by node1 - at  
this point there may be differences between the two underlying devices  
that you don't know about, and you've just caused data corruption.

Even if the devices were clean when the second node came up, the first  
has it open, and the fact that it's not in a clean/shutdown state is  
likely to be recorded too, and node2 is going to be unhappy about that  
too.

All in all, unless md is cluster "aware", it's likely to cause you  
trouble down the line....

Graham

  reply	other threads:[~2006-12-28 11:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 14:01 [linux-lvm] Mirror between different SAN fabrics mathias.herzog
2006-12-22 15:51 ` Matt P
2006-12-27 12:15   ` mathias.herzog
2006-12-27 20:47     ` Matt P
2006-12-28  8:12       ` mathias.herzog
2006-12-28  8:49         ` Christian.Rohrmeier
2006-12-28 10:13           ` mathias.herzog
2006-12-28 10:55             ` Christian.Rohrmeier
2006-12-28 11:09               ` Graham Wood [this message]
2006-12-28 11:31                 ` Christian.Rohrmeier
2006-12-28 11:42                   ` Graham Wood
2006-12-28 11:52                     ` mathias.herzog
2006-12-28 18:19                       ` Ty! Boyack
2006-12-28 19:30                         ` Matt P
2006-12-28 22:02                           ` Ty! Boyack
2006-12-28 23:24                             ` Matt P
2007-01-03 16:30                               ` mathias.herzog
2007-01-05 12:27                               ` mathias.herzog
2006-12-29 13:10                             ` [linux-lvm] Filter the Swap Partition berthiaume_wayne

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=20061228110944.5gxv84tcg8ggg08w@www.dragonhold.org \
    --to=gwood@dragonhold.org \
    --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.