All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@linuxcare.com>
To: Jos Visser <josv@osp.nl>
Cc: Heinz Mauelshagen <mauelshagen@sistina.com>,
	Sergey Vichik <SVichik@store-age.com>,
	linux-lvm@msede.com
Subject: Re: [linux-lvm] Alternate Pathing?
Date: 24 Jul 2000 19:00:47 -0400	[thread overview]
Message-ID: <yq1lmyr6sm8.fsf@tyra.mkp.net> (raw)
In-Reply-To: Jos Visser's message of "Mon, 24 Jul 2000 22:24:47 +0200"

>>>>> "Jos" == Jos Visser <josv@osp.nl> writes:

Jos> Alternate pathing depends on the driver being able to decide that
Jos> a device probed via a particular controller is exactly the same
Jos> device as one that it has already seen through a controller that
Jos> has been probed earlier. I think it will be hard to decide on a
Jos> unique identifier that works for all types of block devices
Jos> (serial number?)

Fortunately, (at least in the FC-AL case) most vendors are smart
enough to assign UUIDs to their devices.  SCSI inquiries also help.
Finally, ext2 and XFS also have UUIDs in their superblocks.  Hence we
have several ways to get hints about the physical setup.

It is my intention to feature a pluggable driver scheme depending on
the physical device in the other end.  Also, some devices require to
be poked to initiate failover/failback.

Worst case (i.e. with incredibly stupid hardware) people will have to
specify the paths manually.

-- 
Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc.
mkp@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

  reply	other threads:[~2000-07-24 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DCBFB8E1BD8BD311A94D00A0C9CA44EA0CCD0E@storeage_nt>
2000-07-24 18:58 ` [linux-lvm] Alternate Pathing? Heinz Mauelshagen
2000-07-24 20:24   ` Jos Visser
2000-07-24 23:00     ` Martin K. Petersen [this message]
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=yq1lmyr6sm8.fsf@tyra.mkp.net \
    --to=mkp@linuxcare.com \
    --cc=SVichik@store-age.com \
    --cc=josv@osp.nl \
    --cc=linux-lvm@msede.com \
    --cc=mauelshagen@sistina.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.