From: Michael E Brown <Michael_E_Brown@dell.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Jos Visser <josv@osp.nl>, linux-lvm@msede.com
Subject: Re: [linux-lvm] scsi/fc multipath failover patch
Date: Mon, 06 Nov 2000 14:01:04 -0600 [thread overview]
Message-ID: <3A070E00.C4FE25F9@dell.com> (raw)
In-Reply-To: 200011061933.eA6JXtF17815@webber.adilger.net
Andreas Dilger wrote:
> Joe Visser writes:
> > Does anyone know whether md, lvm and likeminded drivers are resistant
> > against this alternate pathing solution? I mean, when you connect a SCSI
> > (or FC disk for that matter) through two controllers, any application or
> > driver that does scanning of the attached disks and partitions will
> > encounter the same disk/partitions twice.
>
> Heinz has said that in the upcoming 0.9 release of LVM, there will be
Is there cvs repository or some such thing so that us mere mortals can
test/contribute to upcoming release? I've a lab full of machines that can be
used for the cause, several fibre-channel devices, lots of scsi external
storage, and lots of other neat toys I can do horrible experiments on without
whining about lost data.
>
> PVIDs (actually DCE UUIDs) so LVM will remove duplicate PVs from its
> lists. This can happen for reasons other than multipath, such as
> /dev/md and /dev/{hd,sd} access to the same PV.
>
> Cheers, Andreas
> --
> Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
> \ would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
prev parent reply other threads:[~2000-11-06 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 15:56 [linux-lvm] scsi/fc multipath failover patch Michael E Brown
2000-11-06 17:01 ` Jos Visser
2000-11-06 19:33 ` Andreas Dilger
2000-11-06 20:01 ` Michael E Brown [this message]
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=3A070E00.C4FE25F9@dell.com \
--to=michael_e_brown@dell.com \
--cc=adilger@turbolinux.com \
--cc=josv@osp.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox