Linux LVM users
 help / color / mirror / Atom feed
From: Tom Dawes-Gamble <tmdg@avbrief.com>
To: Mats Wichmann <mats@laplaza.org>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] lv not persistent across reboot?
Date: Wed, 27 Sep 2000 20:14:54 +0000 (UTC)	[thread overview]
Message-ID: <200009272014.UAA20254@lindbergh.avbrief.com> (raw)
In-Reply-To: <3.0.6.32.20000927105531.00eb8d30@laplaza.org> from "Mats Wichmann" at Sep 27, 2000 10:55:31 AM

Hi,

HPUX LVM will show both devices in the volume group.
One device will be the "Primary link" and the other the "Alternate link"
The lvm commands label the primary and alternate link so you know which 
is which.  There are also option to allow you to switch them around.
The primary is the first device added to the volume group.

All I/O is done to the primary link.  If however the I/O fails on the 
Primary link LVM will switch to the Alternate link and use that.
So if controler "A" goes bad you can still use the VG via Controller B.
Of course if the disk goes bad your dead in the water.

If you have two disks visible on the same two controllers then you 
can set one primary on controller A and the other primary on controller
B then if either controller fails you just loose bandwidth but you don't
stop.

If fact when the Primary goes bad it switches and becomes the
Alternate link and the Alternate becomes the new Primary link.

If you want more detail just let me know.

Tom.

On Wed Sep 27 16:55:31 2000 Mats Wichmann wrote:-
> 
> At 02:47 PM 09/27/2000 +0000, Heinz J. Mauelshagen wrote:
> >
> >Morning Steve :-{)
> >
> >On Wed, Sep 27, 2000 at 07:19:14AM -0500, Steve Brueggeman wrote:
> >> Does this imply that Linux LVM will also have problems with discs in H.A.
> >> configurations? 
> >
> >Yes.
> >
> >> 
> >> For example: Fibre Channel drives have two ports on them.  If I have a
> Linux box
> >> with two Host Adapters, and each adapter is connected to the same set of
> drives,
> >> but on different ports, will v0.8final (without the patch below) have
> unstable
> >> vgscans?
> >
> >Yes, it should.
> >
> >> 
> >> I have not been following the high availability mailing list, and a
> solution may
> >> already exist  there.  If so, and you know how, I'd be interested in a
> quick
> >> description.
> >
> >Not that i am aware of.
> 
> Does anybody have any experience to contribute about what other
> LVM systems do in these situations?  They don't have the dynamic
> scan/assignment stuff in Solaris or AIX, right?  (Showing my
> ignorance here).
> 
> My experience of FC-AL setups is limited to theoretical at this
> point, but I had been wondering how they are addressed by systems.
> Is the dual-port stuff handled within the driver such that it's
> not actually presented as two separate "devices"?  The presence
> of two ports is a redundancy (+optionally performance) issue,
> so that would almost make sense to me that one would hide the
> physical reality inside the driver.
> 
> -- mats
> 


-- 
char  *r,*e,*w="%.9s%.7s%.7s\n";extern int printf(const char*,...);int main(){
int l=*w,a,b,th=*(w-~(l/=l))-*(w+l);b=*w+~th--;a=b-th;//Aviation Briefing Ltd.
r=e="  DISPLAY'tmdg@avbr';,,;'ief.com'*>"+b;l+=~b,th-=printf(w,e-a,th+e,r);
r=e="  DISPLAY'http://www.avbrief.com/' *>"-~b,exit(~l-printf(w,e+~a,th+e,r));}

  reply	other threads:[~2000-09-27 20:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-25 23:52 [linux-lvm] lv not persistent across reboot? Tim Pepper
2000-09-26 11:35 ` Heinz J. Mauelshagen
2000-09-26 10:57   ` Jan Niehusmann
2000-09-26 14:44     ` Tim Pepper
2000-09-26 15:26       ` Jan Niehusmann
2000-09-26 18:30     ` Tim Pepper
2000-09-27 12:19   ` Steve Brueggeman
2000-09-27 14:47     ` Heinz J. Mauelshagen
2000-09-27 16:55       ` Mats Wichmann
2000-09-27 20:14         ` Tom Dawes-Gamble [this message]
2000-09-27 18:33       ` Christoph Hellwig

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=200009272014.UAA20254@lindbergh.avbrief.com \
    --to=tmdg@avbrief.com \
    --cc=linux-lvm@msede.com \
    --cc=mats@laplaza.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox