archive mirror
 help / color / mirror / Atom feed
From: Michael Marxmeier <>
Subject: Re: [linux-lvm] Reliability
Date: Thu, 08 Jun 2000 2:31:19 MESZ	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>; from "Heinz J. Mauelshagen" at Jun 7, 100 7:43 pm

> 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.

As far as i can see Quorum support looks like the saner option:
If you loose a disk and only restore the partition table and VGDA
the replacement disk still mostly contains garbage (eg. not a fs).
So we could as well activate the VG and leave LVs with extents
on offline PVs disabled?

Any reason why this might not work?


Michael Marxmeier           Marxmeier Software AG
E-Mail:      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420

  reply	other threads:[~2020-11-27 16:17 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
2020-11-27 16:17   ` Michael Marxmeier [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).