linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Does pv failure effect whole vg?
Date: Wed, 20 Jun 2007 17:36:23 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0706201722500.12479-100000@bmsred.bmsi.com> (raw)
In-Reply-To: <46796A73.1000504@vdberg.org>

On Wed, 20 Jun 2007, Richard van den Berg wrote:

> To answer my own question: when a pv is not available at boot time, the
> vg using that pv does not come up. So splitting vgs makes sense when you
> want to minimize the impact of one disk failure.

Hmmm.  On AIX LVM, vgs still boot when physical volumes fail, provided
there is a "quorum".  The metadata is redundantly stored on all PVs,
so a "quorum" means that more than half of the metadata copies
are available and at the same version.

I think Linux LVM stores only metadata for that PV on a PV, but there
is a backup in /etc/lvm.

If the system truly won't boot with a failed disk, that kind of adds another
reason why current LVM mirroring support is useless.

If you build your VG on raid (md devices or hardware), you solve 
the problem for now.

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

  reply	other threads:[~2007-06-20 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19  6:39 [linux-lvm] Does pv failure effect whole vg? Richard van den Berg
2007-06-20 17:57 ` Richard van den Berg
2007-06-20 21:36   ` Stuart D. Gathman [this message]
2007-06-21  7:43     ` Richard van den Berg
2007-06-21 14:45       ` Stuart D. Gathman
2007-06-21 16:31         ` Richard van den Berg
2007-06-22  3:14     ` f-lvm
2007-06-24 15:43       ` Nix

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=Pine.LNX.4.44.0706201722500.12479-100000@bmsred.bmsi.com \
    --to=stuart@bmsi.com \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).