linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@Sistina.com>
To: Jan Niehusmann <jan@gondor.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Reliability
Date: Wed, 7 Jun 2000 19:43:35 +0200	[thread overview]
Message-ID: <20000607194335.B17473@hmsysv.t-online.de> (raw)
In-Reply-To: <20000607190757.A18846@gondor.com>; from jan@gondor.com on Wed, Jun 07, 2000 at 07:07:57PM +0200


Quorum support is a solution to deal with the activation of a VG without having
all PVs available which belong to it.

This actually is usefull in case you have associated all LEs of specific LVs
to available PVs and want to access those.
In real life scenarios this can't be garanteed though which leads to partitally
destroyed (unusable) LV contents and in consequence to filesystem errors.

Therefore qourum is IMO not really usefull.

The tradeoff of the existing solution nevertheless is that reconstruction of
the partition table and the VGDA is necessary on a replacement disk (subsystem)
which takes some time :-{(
After this we almost have the same scenario as with quorum.
The difference is that no I/O errors are returned in case of accessing
bad LEs.

Heinz

On Wed, Jun 07, 2000 at 07:07:57PM +0200, Jan Niehusmann wrote:
> What happens when one of several drives in a vg fails? Is the whole vg
> lost or only lv's that are on that pv? In the latter case, what about
> lv's that are only partly located on that pv?
> 
> I once observed that with a corrupted partition table, causing one pv
> to be lost, the whole vg didn't get detected. As I was able to reconstruct
> the partition table, I didn't try very hard to get the vg running 
> without that drive. 
> 
> Jan

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                Sistina Software Inc.
Senior Consultant/Developer                      Bartningstr. 12
                                                 64289 Darmstadt
                                                 Germany
Mauelshgen@Sistina.com                           +49 6151 710386
                                                      FAX 710396
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2000-06-07 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-07 17:07 [linux-lvm] Reliability Jan Niehusmann
2000-06-07 17:43 ` Heinz J. Mauelshagen [this message]
2020-11-27 16:17   ` Michael Marxmeier
2000-06-08 10:11     ` Jan Niehusmann

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=20000607194335.B17473@hmsysv.t-online.de \
    --to=mauelshagen@sistina.com \
    --cc=jan@gondor.com \
    --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;
as well as URLs for NNTP newsgroup(s).