From: Jan Niehusmann <list039@gondor.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscan -- ERROR with 2.4.0-test13-pre4
Date: Sat, 23 Dec 2000 00:36:35 +0100 [thread overview]
Message-ID: <20001223003635.A986@gondor.com> (raw)
In-Reply-To: <20001222181730.A1371@gondor.com>; from list039@gondor.com on Fri, Dec 22, 2000 at 06:17:30PM +0100
On Fri, Dec 22, 2000 at 06:17:30PM +0100, Jan Niehusmann wrote:
> Now, when I try to boot the new kernel, I get the following message from
> vgscan:
>
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get data of
> volume group "vg1" from physical volume(s)
Ok, I found the problem: The sort order of the pv's is wrong, and 0.9 is
missing the code that sorts them. 0.8final's pv_read_all_pv_of_vg.c contains
for ( p = 0; pv_tmp[p] != NULL; p++) {
if ( strcmp ( pv_tmp[p]->vg_name, vg_name) == 0) {
pv_this[pv_tmp[p]->pv_number-1] = pv_tmp[p];
np++;
}
}
and 0.9's doesn't.
The following patch fixes it (I did this fix to prove my theory, it may
not be the right way to do it):
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???
}
prev parent reply other threads:[~2000-12-22 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 17:17 [linux-lvm] vgscan -- ERROR with 2.4.0-test13-pre4 Jan Niehusmann
2000-12-22 23:36 ` Jan Niehusmann [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=20001223003635.A986@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.