All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LE/PE Question
Date: Fri Nov 22 15:49:04 2002	[thread overview]
Message-ID: <20021122220736.A15173@sistina.com> (raw)
In-Reply-To: <658450000.1037989977@[192.168.200.4]>; from lembark@wrkhors.com on Fri, Nov 22, 2002 at 12:32:57PM -0600

On Fri, Nov 22, 2002 at 12:32:57PM -0600, Steven Lembark wrote:
> 
> 
> -- "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> 
> >> The unit of failure, for all pratical purposes, is the LV
> >> (unless you are into using dd on raw disk devices to make
> >> your backups). If one drive is likely to fail then any LV
> >> crossing that LV is going to get fried (short of RAID) and
> >> will have to be restored.
> >
> > With LVM2 (and deprecated LVM1.1) you are able to activate a VG even
> > though some of its PVs are inaccessable.
> > If any filesystem is mountable still depends on the availability
> > of alternate superblocks and (at least) the root directory.
> 
> Which seems to mean that the unit of failure still is
> the LV: if an LV spans PV's and the PV looses data then
> the LV is unusable.

Yes, the unit of (partial) failure is the LV.
Point is, that the LV still might be partially accessable.

> The VG being able to survive an offline
> PV is a Very Good Thing but doesn't do anything to help
> someone with a filesystem on an LV with half its extents
> missing.

Well, that very much depends on _which_ extents are actually missing and
what filesystem metadata and data they contain.

I.e. if those containing (alternate) superblocks _and_ the root directory are
accessable still, user might be very happy to be able to retrieve that partial
filesystem. In particular if his updated critical files not backed up last
night are still retrievable.

Regards,
Heinz    -- The LVM Guy --

> 
> 
> --
> Steven Lembark                               2930 W. Palmer
> Workhorse Computing                       Chicago, IL 60647
>                                             +1 800 762 1582
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

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

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2002-11-22 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 14:56 [linux-lvm] LE/PE Question kalle
2002-11-21  5:04 ` Heinz J . Mauelshagen
2002-11-21 10:33   ` Steven Lembark
2002-11-22  3:45     ` Heinz J . Mauelshagen
2002-11-22 12:27       ` Steven Lembark
2002-11-22 15:49         ` Heinz J . Mauelshagen [this message]

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=20021122220736.A15173@sistina.com \
    --to=mauelshagen@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.