From: Lars Marowsky-Bree <lmb@suse.de>
To: Oktay Akbal <oktay.akbal@s-tec.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible Bug with MD multipath and raid1 on top
Date: Sun, 15 Sep 2002 23:12:22 +0200 [thread overview]
Message-ID: <20020915211222.GE8607@marowsky-bree.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0209150721270.25780-100000@omega.s-tec.de>
On 2002-09-15T07:29:30,
Oktay Akbal <oktay.akbal@s-tec.de> said:
> > Is this with or without the patch I recently posted to linux-kernel?
>
> Since it is the latest official Suse-2.4.18 from SLES I assume this patch
> is not included.
Oh, ok. Multipathing is known to not work perfectly right in the mainstream
kernel. In this case, you might want to try the patch.
> > So far this sounds OK.
> All disks are dead. The md0 device is missing. The same should be true for
> md1, since there is no difference in setup. Why should the raid1 no report
> both mirrors as dead ?
Oh, right. I misread your mail and just saw that the md1 was also on the same
devices. Strange indeed.
> > (Even though the updated md-mp patch will _never_ fail the last path but
> > instead return the error to the layer upwards; this protects against
> > certain scenarios in 2.4 where a device error can't be distinguished from
> > a failed path and we don't want that to lead to an inaccessible device)
> How would the failing of all Pathes then be noticed ?
Well, IO errors would occur, be reported to the caller and those would
supposedly be noticed.
However, the 2.4 error reporting can't distinguish between a path or a device
error. So a failed read (destroyed block, for example) will fail a path. As
the read request is retried on all paths if necessary, it would be highly
undesireable to fail _all_ paths because of this. The last path will remain
"accessible", but the application will see an error in this case.
> This might well be, since I don't found the qlogic-driver very impressing
> so far. To use md-multipath the multipathing (failover) functionality from
> the driver was disabled.
OK. Well, I never tested the QLogic proprietary failover because I consider it
to be the wrong approach ;-) The md layer should work though by now.
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-15 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 18:33 Possible Bug with MD multipath and raid1 on top Oktay Akbal
2002-09-14 23:07 ` Lars Marowsky-Bree
2002-09-15 5:29 ` Oktay Akbal
2002-09-15 21:12 ` Lars Marowsky-Bree [this message]
2002-09-15 7:31 ` Nachtrag: " Oktay Akbal
2002-09-15 7:39 ` Oktay Akbal
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=20020915211222.GE8607@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