From: "bo" <bo@sosnetwork.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Error on vgscan & lvremove
Date: Thu May 23 22:14:01 2002 [thread overview]
Message-ID: <017301c202d0$c77c2410$6501a8c0@bomoon> (raw)
In-Reply-To: 20020523190023.A13788@sistina.com
Heinz,
> A 'workaround' for non-devfs configurations is
>
> ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
>
??Something wrong on "sed 's!/group!!' ", it did not work.
>
> link the single executable statically by running
> "./configure --enable-static_link" (which doesn't use the shared libs).
>
It did not work. I rebuilt LINUX kernel & LVM after
"./configure --enable-static_link".
I got the same result.
Another big issues came as follow;
I tried to go back to LVM1.0.3, but getting a big trouble.
Q1: Is it backward compatible from LVM1.1-rc2 to LVM1.0.3 or not?
I already built the volume from LVM1.1-rc2 then I went back to
LVM1.0.3.
All of LVM tools are not working as shown in the following console
output.
Q2: How could I remove this volume and rebuild? I do not care about the
data.
During boot or after the boot, I have the following errors;
[root@localhost /]# vgscan -f
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "volRaid0"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volRaid0"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volRaid0"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volRaid0" from "/etc/lvmtab"
vgscan -- found inactive volume group "volRaid5"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volRaid5"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volRaid5"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volRaid5" from "/etc/lvmtab"
vgscan -- found inactive volume group "volDisk"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volDisk"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volDisk"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volDisk" from "/etc/lvmtab"
vgscan -- found inactive volume group "volDisk2"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volDisk2"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volDisk2"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volDisk2" from "/etc/lvmtab"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
groups
[root@localhost /root]# ls /dev/*/group
ls: /dev/*/group: No such file or directory
[root@localhost /root]# vgmknodes
vgmknodes -- no volume groups found to create nodes for
Thanks for your help,
Bo
next prev parent reply other threads:[~2002-05-23 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 16:48 [linux-lvm] Error on lvcreate or lvremove! bo
2002-05-22 7:50 ` Heinz J . Mauelshagen
2002-05-22 21:51 ` bo
2002-05-23 12:04 ` Heinz J . Mauelshagen
2002-05-23 22:14 ` bo [this message]
2002-05-24 4:01 ` [linux-lvm] Error on vgscan & lvremove Heinz J . Mauelshagen
2002-05-24 16:34 ` bo
2002-05-25 5:53 ` 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='017301c202d0$c77c2410$6501a8c0@bomoon' \
--to=bo@sosnetwork.net \
--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