From: Lars Marowsky-Bree <lmb@suse.de>
To: Oktay Akbal <oktay.akbal@s-tec.de>, linux-kernel@vger.kernel.org
Subject: Re: md multipath with disk missing ?
Date: Mon, 9 Sep 2002 15:27:13 +0200 [thread overview]
Message-ID: <20020909132713.GA29@marowsky-bree.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0209091504270.12771-100000@omega.s-tec.de>
On 2002-09-09T15:08:31,
Oktay Akbal <oktay.akbal@s-tec.de> said:
> Can someone tell me, how md multipathing works, when a drive fails
> completly ?
Well, if the drive (not the path to it) fails _completely_, it won't be
detected by the md autostart (as it can't find the md superblock).
If it fails completely during runtime, all paths but the last one to it will
be disabled, as a drive failure can't be distinguished from a path failure in
the wonderful 2.4 error handling ;-)
But then, all requests send down the last path will fail, because the target
is broken, not the path.
In short, multipathing doesn't help a bit here; how could it?
> Does this only work with raid-autodetection ?
> When no autodetection is done and a drive is missing, would a raidstart
> kill the raid, since the drives are now available with other devices (sda
> instead of former sdb...) ?
I don't understand your question, sorry.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Immortality is an adequate definition of high availability for me.
--- Gregory F. Pfister
next prev parent reply other threads:[~2002-09-09 13:21 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 [this message]
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
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=20020909132713.GA29@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