linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Erkki Seppala <flux-lvm@inside.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] rescuing a VG with one missing PV
Date: Tue Feb 12 15:37:02 2002	[thread overview]
Message-ID: <20020212213713.GA10944@xulfad.ton.tut.fi> (raw)
In-Reply-To: <20020212150551.A3258@sistina.com>

On Tue, Feb 12, 2002 at 03:05:51PM +0100, Heinz J . Mauelshagen wrote:
> Get LVM from CVS at www.sistina.com and either use the -s option of pvcreate
> I implemented recently to fake the size you need or run "vgcfgrestore -i ..."
> which ignores the size of the device and restores metadata anyway
> at your own risk.

Thanks! This seems to be doing the trick. There seemed to be one typo
in the CVS at the moment I checked out my version, but I imagine it'll
be fixed as soon as someone tries to compile it :-) :

---8<---
Index: vgscan.c
===================================================================
RCS file: /data/cvs/LVM/tools/vgscan.c,v
retrieving revision 1.12
diff -u -r1.12 vgscan.c
--- vgscan.c    2002/02/08 14:59:37     1.12
+++ vgscan.c    2002/02/12 21:29:00
@@ -294,7 +294,7 @@
                for ( blk_dev = l = 0; l < vg->lv_max; l++) {
                   lv = vg->lv[l];
                   if ( lv == NULL) continue;
-                  if ( lvm_tab_check_free_lv_number ( lv) == FALSE) {
+                  if ( lvm_tab_check_free_lv_numbers ( lv) == FALSE) {
                      printf ( "%s -- changing minor number on \"%s\"\n",
                               cmd, lv->lv_name);
                      if ( lv->lv_access & LV_SNAPSHOT_ORG) {
---8<---

> Even though you lost your data anyway with the old drive, you need
> to either pvmove it away to get rid of allocated extents in that PV
> again or lvreduce LVs to make them free which you potentially don't
> like, because the extents might be further to the beginning of the
> LV.

I don't completely understand this, but I guess I will when the pvmove
has completed - it's a surprisingly slow operation. I was glad to
notice though that only one logical volume was in the failed disc.

Once again, thanks for the help :).
-- 
  _____________________________________________________________________
     / __// /__ ____  __                              Erkki Sepp�l�\   \
    / /_ / // // /\ \/ //ircnet                           Modeemi Ry\  /
   /_/  /_/ \___/ /_/\_\@modeemi.fi        http://www.modeemi.fi/~flux/

  reply	other threads:[~2002-02-12 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09  8:24 [linux-lvm] pvmoving from a pv with bad sectors Erkki Seppala
2002-02-09  9:10 ` Erkki Seppala
2002-02-11 14:53   ` [linux-lvm] rescuing a VG with one missing PV Erkki Seppala
2002-02-12  3:24     ` Heinz J . Mauelshagen
2002-02-12  6:58       ` Erkki Seppala
2002-02-12  8:07         ` Heinz J . Mauelshagen
2002-02-12 15:37           ` Erkki Seppala [this message]
2002-02-13  3:27             ` 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=20020212213713.GA10944@xulfad.ton.tut.fi \
    --to=flux-lvm@inside.org \
    --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).