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 03:45:02 2002	[thread overview]
Message-ID: <20021122103810.A12967@sistina.com> (raw)
In-Reply-To: <448380000.1037896711@[192.168.200.4]>; from lembark@wrkhors.com on Thu, Nov 21, 2002 at 10:38:31AM -0600

On Thu, Nov 21, 2002 at 10:38:31AM -0600, Steven Lembark wrote:
> 
> 
> -- "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> 
> > On Tue, Nov 19, 2002 at 09:50:39PM +0100, kalle@idlar.nu wrote:
> >> Hi!
> >>
> >> Im researching some diffrent what-if-scenarios to be more prepared if
> >> our lvm fails. and I'm wondering..Is there any utility to find which
> >> file (or fs inode) a specific LE/PE is assigned to?
> >
> ># lvdisplay -v /dev/YourVG/YourLV # displays mapping logical -> physical
> ># extents lvdisplay -v /dev/YourPV # displays mapping physical -> logical
> ># extents
> >
> >>   What I would like to acomplish it to be able to know what files are
> >>   located on a specific disk in a
> >>
> >> VG/LV. So if I detect that a disk in a LV is starting to fail I would
> >> like to know which files are more
> >>
> >> likely to be non-recoverable.
> >
> > You need to 'ask' the filesystem, where it puts stuff ;)
> > I.e. "debugfs /dev/YourVG/YourLV" for ext[23].
> 
> 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.

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

-- 

Regards,
Heinz    -- The LVM Guy --

*** 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  3:45 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 [this message]
2002-11-22 12:27       ` Steven Lembark
2002-11-22 15:49         ` 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=20021122103810.A12967@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.