All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Niehusmann <list039@gondor.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgcfgrestore bug followup
Date: Sun, 7 Jan 2001 22:33:00 +0100	[thread overview]
Message-ID: <20010107223300.A6050@gondor.com> (raw)
In-Reply-To: <0ada40824210711NYCSMTP2@nyc.rr.com>; from bcorsello@usa.net on Sun, Jan 07, 2001 at 04:23:50PM -0500

On Sun, Jan 07, 2001 at 04:23:50PM -0500, Brad Corsello wrote:
> (But then I pushed my luck and tried doing vgextends.  After adding three PVs,
> vgscan started to throw up with a weird error:  vg_read_with_pv_and_lv():
> allocated LE of LV" can't get data of volume group "vg1" from physical
> volume(s).  I don't know if this is related to the vgcfgrestore problem or
> not.)

This one looks like a problem I had myself. For me, the following patch
did help: (I already posted this patch, with a description, on Dec 23)

Index: pv_read_all_pv_of_vg.c
===================================================================
RCS file: /data/cvs/LVM/tools/lib/pv_read_all_pv_of_vg.c,v
retrieving revision 1.3
diff -u -1 -b -p -r1.3 pv_read_all_pv_of_vg.c
--- pv_read_all_pv_of_vg.c	2000/11/20 02:47:20	1.3
+++ pv_read_all_pv_of_vg.c	2000/12/22 23:27:00
@@ -103,2 +103,3 @@ int pv_read_all_pv_of_vg ( char *vg_name
             pv_this_sav = pv_this;
+	    if(np<pv_tmp[p]->pv_number) np=pv_tmp[p]->pv_number;
             if ( ( pv_this = realloc ( pv_this,
@@ -111,5 +112,4 @@ int pv_read_all_pv_of_vg ( char *vg_name
             }
-            pv_this[np] = pv_tmp[p];
-            pv_this[np+1] = NULL;
-            np++;
+            pv_this[pv_tmp[p]->pv_number-1] = pv_tmp[p];
+            //pv_this[np+1] = NULL; // XXX???
          }

  reply	other threads:[~2001-01-07 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07 21:23 [linux-lvm] vgcfgrestore bug followup Brad Corsello
2001-01-07 21:33 ` Jan Niehusmann [this message]
2001-01-08  0:26   ` Holger Grothe
2001-01-08  0:40     ` 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:
  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=20010107223300.A6050@gondor.com \
    --to=list039@gondor.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.