linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Disk Died - Ideas?
Date: Thu, 27 Sep 2001 09:55:16 -0600	[thread overview]
Message-ID: <20010927095516.C19527@turbolinux.com> (raw)
In-Reply-To: <53040000.1001601637@dizzy>

On Sep 27, 2001  09:40 -0500, Steven Lembark wrote:
> <broken record>
> 
> boot once.
> 
> vgexport /dev/vgwhatever;
> vgimport /dev/vgwhatever <list of drives that didn't croak>
> 
> you will now have your VG back on line with whatever portion of the
> data is no the clean drives.  any LV's spanning the dead drive are
> likely to be lost anyway.  It'll take you less time to vgextend the
> imported group onto a new, working drive an recover backups onto
> new LV's than almost anything else you can try.
> 
> </broken record>

bzzzt.  This _may_ work on HPUX and AIX, but I _highly_ doubt it will
work with Linux LVM.  The Linux LVM code requires that all of the disks
be present, and that they all have the correct data (no metadata backups
yet).  You could hack the vgscan code so that it doesn't require this,
but it would probably end up causing grief somewhere else before you
could actually read from the LV.

AFAIK, not even HPUX or AIX would allow you to read from a partial LV
(which is the situation we are discussing here), so it wouldn't help.
What _would_ be very useful is a tool that reads the LVM metadata
directly, creates a list of available LEs (in order) and dumps them
to a file, writing zeros for LEs that are not available (and writing
large warnings for each missing LE).

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  reply	other threads:[~2001-09-27 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 15:02 [linux-lvm] Disk Died - Ideas? Jeff Layton
2001-09-25 16:56 ` lembark
2001-09-25 17:09 ` Andreas Dilger
2001-09-27 11:39   ` Jeff Layton
2001-09-27 14:40     ` Steven Lembark
2001-09-27 15:55       ` Andreas Dilger [this message]
2001-09-27 15:32         ` Kevin Corry
2001-09-27 16:09         ` Steven Lembark
2001-09-27 15:42     ` Andreas Dilger

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=20010927095516.C19527@turbolinux.com \
    --to=adilger@turbolabs.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 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).