Linux LVM users
 help / color / mirror / Atom feed
From: Anthony Johnson <anthony@storix.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Quorums / VGDAs
Date: Fri Sep 13 15:31:02 2002	[thread overview]
Message-ID: <3D80D4CB.C244DFA6@storix.com> (raw)
In-Reply-To: 20020911123312.D26854@sistina.com

Heinz, 
I'm having some trouble understanding these answers. Perhaps I am
misunderstanding the purpose of a "quorum" on Linux. On AIX, quorums
ensure that at least one copy of the latest VGDA is alsays avaialble by
ensuring there are always a quorum (over half) of the VGDA copies
available. The VGDA is stored on each PV (and sometimes 2 copies are
stored on each PV). If you lose quorum, you lose the VG (to ensure we
don't varyon with an old copy).

You imply that a "quorum" requires ALL of the PVs be avialable in Linux.
The dictionary definition of a "quorum", however, is more than half. If
a VG in Linux can be varied on with only one good copy of a VGDA (in
perhaps a 3-PV VG), then how do you ensure that you are always looking
at and updating the most recent copy? If, for instance, I have a 4-disk
VG, and I lose 2 disks, then shutdown and varon the VG with the
alternate 2 disks (the previously missing ones), I will be seeing only
the older VGDA. Is the VGDA also stored in the /etc/lvmtab.d? If so, can
you varyon if this VGDA was removed?

I guess the big question is: How does LVM for Linux ensure that we are
always using the most recent VGDA data (in case we're looking at active
PVs that were previously missing). I have to do a lecture to an AIX
group on the differences between LVM on AIX and Linux, and quorums were
always a big issue for AIX.

Thanks,
Anthony

> > 1) What defines a quorum - over 50% of the PVs in the VG, or over 50%
> >    of the VGDAs?
> 
> VG quorum is given in case all of its PVs are available.
> 
> > 2) How many VGDAs are stored on each physical volume. From AIX
> >    experience, this varied depending on the number of PVs in the VG.
> 
> In the LVM1 metadata there's allways 1 VGDA on each PV which has internal
> redundancy.
> With the new LVM2 formats you can have as many VGDA copies as you like.
> 
> > 3) If quorum is lost on an active VG, is the entire VG automatically
> >    varied off?
> 
> No, it will stay accessable with the exception of the dead PV(s).
> 
> > 4) Can a VG without quorum be forcefully varied on?
> 
> With LVM1.1 (see CVS; WARNING: his is interim development code!) and with final
> LVM2 later this year, you can activate a VG which has lost quorum.

  reply	other threads:[~2002-09-13 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 13:54 [linux-lvm] Quorums / VGDAs Anthony Johnson
2002-09-11  5:57 ` Heinz J . Mauelshagen
2002-09-13 15:31   ` Anthony Johnson [this message]
2002-09-16  6:38     ` Heinz J . 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=3D80D4CB.C244DFA6@storix.com \
    --to=anthony@storix.com \
    --cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox