From: Heinz Mauelshagen <mauelshagen@sistina.com>
To: Sergey Vichik <SVichik@store-age.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Alternate Pathing?
Date: Mon, 24 Jul 2000 13:58:18 -0500 [thread overview]
Message-ID: <20000724135818.A26581@mail.sistina.com> (raw)
In-Reply-To: <DCBFB8E1BD8BD311A94D00A0C9CA44EA0CCD0E@storeage_nt>; from SVichik@store-age.com on Mon, Jul 24, 2000 at 09:25:19PM +0200
On Mon, Jul 24, 2000 at 09:25:19PM +0200, Sergey Vichik wrote:
>
> Hi,
>
>
> It seems to be a litle tricky to detect via LVM which HBA has failed or
> disconnected, because the mapping to real disks occurs at lvm_map, and you
> cannot know whether this IO proccess have ended succesfully or not in
> lvm_map.
>
> The only solutuion I see, is to pass all IO operations via write/read of LVM
> and detect failed HBA by retrying failed IO request, when eliminating every
> time one of HBAs from mapping till IO operation successfull .
That's roughly what i was thinking to do in the future.
But Martin K. Peter already mentioned that he needs to implement it anyway
and he wants to do it in the general block device layer.
This has the major advantage of beeing available for every block device
rather than only for LVM driven ones.
> Not really effective, ugly, may work.
Ugly only in terms of beeing less general.
It would work.
But the preferable place to implement it is in the request handler
which can take care of requeueing the request to the optional device (path).
Open question anyway is the administration interface.
In case of the existing non self identifying disk devices there's the
need of configuration of the alternate pathes.
> Any other idea ?
Basically Peter's.
Regards,
Heinz -- the LVM guy
next parent reply other threads:[~2000-07-24 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DCBFB8E1BD8BD311A94D00A0C9CA44EA0CCD0E@storeage_nt>
2000-07-24 18:58 ` Heinz Mauelshagen [this message]
2000-07-24 20:24 ` [linux-lvm] Alternate Pathing? Jos Visser
2000-07-24 23:00 ` Martin K. Petersen
2000-07-28 18:34 ` gerhard.fuernkranz
2000-07-23 15:35 Barry Roomberg
2000-07-23 17:16 ` Paul Jakma
2000-07-24 11:58 ` Martin K. Petersen
2000-07-24 16:20 ` Heinz Mauelshagen
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=20000724135818.A26581@mail.sistina.com \
--to=mauelshagen@sistina.com \
--cc=SVichik@store-age.com \
--cc=linux-lvm@msede.com \
/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.