From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] kernel reports vg twice
Date: Tue, 9 Oct 2001 11:23:23 +0200 [thread overview]
Message-ID: <20011009112323.B25020@sistina.com> (raw)
In-Reply-To: <20011008160013.A26865@cistron.nl>; from wichert@cistron.nl on Mon, Oct 08, 2001 at 04:00:13PM +0200
Wichert,
which LVM version are you using? 1.0.1 rc4 is recommended.
Regards,
Heinz -- The LVM Guy --
On Mon, Oct 08, 2001 at 04:00:13PM +0200, Wichert Akkerman wrote:
>
> Since I got exactly no response to this I'll report it with a
> different subject.
>
> LVM still does not work for me on one of my machines work:
>
> cloud:/dev/discs/disc1# vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "vg_user"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume group
>
> cloud:/dev/discs/disc1# vgchange -a y
> vgchange -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan
>
> I did a bit of looking around and it seems the confusement is in the
> kernel: when lvm_check_kernel_lvmtab_consistency() compares the kernel
> and the lvmtab entries the list from the kernel mentions the vg_user
> volume group twice, while the lvmtab only mentions it once. This
> results in an immediate abort and as a result I can't do anything
> with the LVM tools.
>
> Wichert.
>
> --
> _________________________________________________________________
> / Nothing is fool-proof to a sufficiently talented fool \
> | wichert@wiggy.net http://www.liacs.nl/~wichert/ |
> | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
>
> ----- End forwarded message -----
>
> --
> _________________________________________________________________
> / Nothing is fool-proof to a sufficiently talented fool \
> | wichert@wiggy.net http://www.liacs.nl/~wichert/ |
> | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-10-09 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 14:00 [linux-lvm] kernel reports vg twice Wichert Akkerman
2001-10-09 9:23 ` Heinz J . Mauelshagen [this message]
2001-10-09 9:30 ` Wichert Akkerman
2001-10-10 3:58 ` Andreas Dilger
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=20011009112323.B25020@sistina.com \
--to=mauelshagen@sistina.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.