public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: Brian Jackson <brian-kernel-list@mdrx.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: md on shared storage
Date: Tue, 12 Nov 2002 18:19:21 -0700	[thread overview]
Message-ID: <3DD1A899.8080800@mvista.com> (raw)
In-Reply-To: 20021113002529.7413.qmail@escalade.vistahp.com

Brian,

The RAID driver does indeed work with shared storage, if you don't have 
RAID autostart set as the partition type.  If you do, each host will try 
to rebuild the RAID array resulting in really bad magic.

I posted patches to solve this problem long ago to this list and 
linux-raid, but Neil Brown (md maintainer) rejected them saying that 
access to a raid volume should be controlled by user space, not by the 
kernel.  Everyone is entitled to their opinions I guess. :)

The patch worked by locking RAID volumes to either a FibreChannel host 
WWN (qlogic only) or scsi host id.  This ensured that if a raid volume 
was started, it could ONLY be started on the host that created it.  This 
worked for the autostart path as well as the start path via IOCTL.

I also modified mdadm to handle takeover for failed nodes to takeover 
RAID arrays.

I'm extending this type of support into LVM volume groups as we speak. 
 If you would like to see the patch when I'm done mail me and I'll send 
it out.  This only applies to 2.4.19.

Thanks
-steve

Brian Jackson wrote:

> Here's a question for all those out there that are smarter than me(so 
> I guess that's most of you then :) I looked around (google, kernel 
> source, etc.) trying to find the answer, but came up with nothing.
> Does the MD driver work with shared storage? I would also be 
> interested to know if the new DM driver works with shared 
> storage(though I must admit I didn't really try to answer this one 
> myself, just hoping somebody will know).
> I ask because I seem to be having some strange problems with an md 
> device on shared storage(Qlogic FC controllers). The qlogic drivers 
> spit out messages for about 20-60 lines then the machines lock up. So 
> the drivers were my first suspicion, but they were working okay 
> before. So I went back and got rid of the md device and now everything 
> is working again. Anybody got any ideas?
> My logic says that it should work fine with shared storage, but my 
> recent experience says my logic is wrong.
> --Brian Jackson
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>
>


  reply	other threads:[~2002-11-13  1:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13  0:25 md on shared storage Brian Jackson
2002-11-13  1:19 ` Steven Dake [this message]
2002-11-13  3:00   ` Michael Clark
2002-11-13  3:15     ` Brian Jackson
2002-11-13 13:22       ` Michael Clark
2002-11-13  2:51 ` Michael Clark
2002-11-13 11:46 ` Lars Marowsky-Bree
2002-11-13 17:17   ` Steven Dake
2002-11-13 17:25     ` Joel Becker
2002-11-13 17:56       ` Steven Dake
2002-11-13 17:24   ` Joel Becker
2002-11-13 15:35 ` Eric Weigle
2002-11-13 18:33   ` Brian Jackson
  -- strict thread matches above, loose matches on Subject: below --
2002-11-13 19:25 Eric Weigle

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=3DD1A899.8080800@mvista.com \
    --to=sdake@mvista.com \
    --cc=brian-kernel-list@mdrx.com \
    --cc=linux-kernel@vger.kernel.org \
    /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