From: Lars Marowsky-Bree <lmb@suse.de>
To: Christoph Biardzki <cbi@cebis.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Storage - redundant path failover / failback - quo vadis linux?
Date: Wed, 16 May 2001 09:17:03 +0200 [thread overview]
Message-ID: <20010516091703.F573@marowsky-bree.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0105160815100.10476-100000@ameise.opto.de>
In-Reply-To: <Pine.LNX.4.21.0105160815100.10476-100000@ameise.opto.de>; from "Christoph Biardzki" on 2001-05-16T08:34:00
On 2001-05-16T08:34:00,
Christoph Biardzki <cbi@cebis.net> said:
> I was investigating redundant path failover with FibreChannel disk devices
> during the last weeks. The idea is to use a second, redundant path to a
> storage device when the first one fails. Ideally one could also implement
> load balancing with these paths.
>
> The problem is really important when using linux for mission-critical
> applications which require large amounts of external storage.
Yes.
Device handling under Linux in the face of HA generally faces some annoying
issues - the one you mention is actually the least of it ;-)
Error handling and reporting is the most annoying one to me - no good way to
find out whether a device has had an error. And even if the kernel logs a read
error on device sda1 - great, what LVM volumes are affected?
But on to your question... ;-)
> - The "T3"-Patch for 2.2-Kernels which patches the sd-Driver und the
> Qlogic-FC-HBA-Driver. When you pull an FC-Cable on a host equiped with two
> HBAs the failover is almost immediate and an automatic failback (after
> "repairing") is possible
I actually like this one best, if it was forward ported to 2.4.
> The low-level-approach of the "T3"-patch requires changes to the
> scsi-drivers and the hardware-drivers but provides optimal communication
> between the driver and the hardware
The changes required for the hardware drivers are rather minimal.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Perfection is our goal, excellence will be tolerated. -- J. Yahl
next prev parent reply other threads:[~2001-05-16 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 6:34 Storage - redundant path failover / failback - quo vadis linux? Christoph Biardzki
2001-05-16 7:17 ` Lars Marowsky-Bree [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-18 7:03 Stefan.Bader
2001-05-18 15:32 ` Jonathan Lundell
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=20010516091703.F573@marowsky-bree.de \
--to=lmb@suse.de \
--cc=cbi@cebis.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.