linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: "miele@inwind.it" <miele@inwind.it>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	mingo <mingo@chiara.csoma.elte.hu>, bueso <bueso@vives.org>
Subject: Re: Can you help me on Linux SW RAID?
Date: Thu, 28 Apr 2005 13:29:04 +0200	[thread overview]
Message-ID: <20050428112904.GC17359@unthought.net> (raw)
In-Reply-To: <IFNIZD$19CF4F5AC29109D5327F89A86EC57541@libero.it>

On Thu, Apr 28, 2005 at 12:11:37PM +0200, miele@inwind.it wrote:
> 
> Hi.
> 
...
> All is wonderful but.. when all seems ok and my work seems to be finished..
> ..I'm having hard doubts on this RAID configuration and its stability.

With good reason - there is no way that this can work reliably.

> I fear that RAID SW modules that runs on each of two Linux nodes, and
> works on the same data of the shared disk array, could produce
> conflicts, misalignments, or I don't know what other..

This is exactly what will happen. It will not work.

> 
> Can you give me a comment or suggests about RAID SW use i've made?

> 

You cannot share storage between multiple SW RAID "masters".

If you take SW RAID and LVM out of the equation, you will still have
problems with the filesystem - you cannot share storage between two
nodes by mounting the same storage.  Again, both nodes will write to the
journal with no synchronization between them, both will cache data
locally with no cache synchronization, etc. etc.  Disaster lies ahead.

Look into GFS for a solution to the filesystem problem.

You can use some of the linux-ha stuff to make sure that only one node
at a time will actually use the underlying storage, if that is an
acceptable solution (pure fail-over).

But all in all, there's no plug'n'play solution for what you're trying
to accomplish.

Personally, I think I'd get a "storage box" which did the RAID for me
(that could be an off the shelf iSCSI/FC box, or it could be another
Linux box exporting a software RAID over iSCSI, it could be a lot of
things depending on your needs and budget), then, I'd look into GFS or
Oracle's recently opensourced shared filesystem for the shared
filesystem.

Maybe others on this list have better suggestions.

But first of all; stop what you are doing now, you are hurting yourself
and your data  ;)

-- 

 / jakob


  reply	other threads:[~2005-04-28 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 10:11 Can you help me on Linux SW RAID? miele
2005-04-28 11:29 ` Jakob Oestergaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-28 10:27 miele
2005-04-28 11:41 miele
2005-04-28 11:49 ` Lars Marowsky-Bree
2005-04-28 12:57 miele
2005-04-28 13:06 ` Lars Marowsky-Bree
2005-04-28 19:18   ` J. Ryan Earl
2005-04-28 19:56     ` Lars Marowsky-Bree

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=20050428112904.GC17359@unthought.net \
    --to=jakob@unthought.net \
    --cc=bueso@vives.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=miele@inwind.it \
    --cc=mingo@chiara.csoma.elte.hu \
    /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).