From: Jan Niehusmann <list039@gondor.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] vgscan -- ERROR with 2.4.0-test13-pre4
Date: Fri, 22 Dec 2000 18:17:30 +0100 [thread overview]
Message-ID: <20001222181730.A1371@gondor.com> (raw)
I installed 2.4.0-test13-pre4 which includes LVM 0.9, and the lvm tools
from http://distro.conectiva.com.br/experimental/.
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)
vgscan -d says (complete output available, but a little bit to long for
the list I think)
[...]
<1> vg_read_with_pv_and_lv -- BEFORE for LV
<1> vg_read_with_pv_and_lv -- vg_this->lv[0]->lv_allocated_le: 169
<1> vg_read_with_pv_and_lv -- LEAVING with ret: -365
<1> lvm_error -- CALLED with: -365
[...]
I added another debug output which tells me the counted number of
pe's (the variable npe). It is 75.
This is strange because lv no. 0 is on one disk. But it's not continous,
and after le no. 75, there is a jump backwards to a lower pe number:
--- Logical extents ---
LE PV PE reads writes
00000 /dev/hda5 00190 11 2
[...]
00073 /dev/hda5 00263 0 0
00074 /dev/hda5 00264 0 0
00075 /dev/hda5 00265 0 0
00076 /dev/hda5 00139 0 0
00077 /dev/hda5 00140 0 0
But I don't see how this could cause a problem.
A difference between the output of 0.8's vgscan -d and 0.9's vgscan -d
is that the order of pv is different:
<333> vg_read -- pv[0]->pv_name: "/dev/hda5"
<333> vg_read -- pv[1]->pv_name: "/dev/sda2"
<333> vg_read -- pv[2]->pv_name: "/dev/hdc4"
vs.
<333> vg_read -- pv[0]->pv_name: "/dev/sda2"
<333> vg_read -- pv[1]->pv_name: "/dev/hda5"
<333> vg_read -- pv[2]->pv_name: "/dev/hdc4"
Jan
next reply other threads:[~2000-12-22 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 17:17 Jan Niehusmann [this message]
2000-12-22 23:36 ` [linux-lvm] vgscan -- ERROR with 2.4.0-test13-pre4 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=20001222181730.A1371@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.