public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Oktay Akbal <oktay.akbal@s-tec.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: md multipath with disk missing ?
Date: Mon, 9 Sep 2002 17:06:48 +0200	[thread overview]
Message-ID: <20020909150648.GD29@marowsky-bree.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0209091537020.12771-100000@omega.s-tec.de>

On 2002-09-09T15:46:15,
   Oktay Akbal <oktay.akbal@s-tec.de> said:

> Example:
> 
> We have sda - sdb (8 drives) and setup up a raidtab to tell linux that
> sda and sde are the same sdc - sdd etc.
> Now for some random error the server restarts and the former sda (path to
> that drive) is no longer available. So now we have sda,sdb...sdg.
> We do not use autodetect, but raidstart to activate the raid.
> 
> now since the former sda is missing the raidtab does not reflect the
> actual setup. The raidtab would read, that sda and sdb are the same
> drive, which is not true in that case.
> 
> (The device-ordering would not be right for a real setup, but take it as
> an example and assume sda-sde sdb-sdf...)
> 
> Would the superblock prevent the wrong use of devices ?

I hope so. But yes, your setup would break spectularly because the devices
moved and the raids wouldn't go online. This shouldn't happen with the
autostart feature, I think.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Immortality is an adequate definition of high availability for me.
	--- Gregory F. Pfister


  parent reply	other threads:[~2002-09-09 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 13:08 md multipath with disk missing ? Oktay Akbal
2002-09-09 13:27 ` Lars Marowsky-Bree
2002-09-09 13:46   ` Oktay Akbal
2002-09-09 13:50     ` Steve Mickeler
2002-09-09 20:45       ` Alan Cox
2002-09-09 15:06     ` Lars Marowsky-Bree [this message]
2002-09-10 22:51     ` Neil Brown

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=20020909150648.GD29@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oktay.akbal@s-tec.de \
    /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