From: Heinz J. Mauelshagen <Heinz.Mauelshagen@t-online.de>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] need help to recover my system
Date: Mon, 2 Oct 2000 10:20:54 +0000 [thread overview]
Message-ID: <20001002102054.A7806@srv.t-online.de> (raw)
In-Reply-To: <200010020449.e924nVl11138@webber.adilger.net>; from adilger@turbolinux.com on Sun, Oct 01, 2000 at 10:49:31PM -0600
On Sun, Oct 01, 2000 at 10:49:31PM -0600, Andreas Dilger wrote:
> You write:
> > When I booted the new 2.2.17 kernel I ran "pvscan -D" & "vgscan -D". I
> > can now do vgdisplay and lvmdisplay if I use the -D parameter. I just
> > can't activate the volume group. When I try, this is the result.
> >
> > [root@farpt1 /root]# vgchange -va y
> > vgchange -- locking logical volume manager
> > vgchange -- finding all volume group(s)
> > vgchange -- checking volume group name "vg01"
> > vgchange -- checking existence of volume group "vg01"
> > vgchange -- reading volume group data for "vg01" from lvmtab
> > vgchange -- checking volume group consistency of "vg01"
> > vgchange -- checking if all physical volumes of volume group "vg01" are
> > available
> > vgchange -- creating VGDA for "vg01" in kernel
> > vgchange -- can't open logical volume manager to activate volume group
> > "vg01"
>
> This looks like the same bug that YOSHIDA Daisuke just fixed (see message
> "Re: vgchange.c patch for devfs"):
Yes, it does.
I already inserted YOSHIDA Daisuke's code into my 0.9 develoment tree.
Heinz
>
> Cheers, Andreas
> -------------------------------------------------------------------------
> --- LVM/0.8final/tools/vgchange.c Tue Feb 22 11:09:33 2000
> +++ LVM.modified/0.8final/tools/vgchange.c Sun Oct 1 12:50:40 2000
> @@ -391,7 +391,13 @@
> if ( opt_v > 0) printf ( "%s -- creating VGDA for \"%s\" "
> "in kernel\n",
> cmd, vg_name);
> - if ( ( ret = vg_create ( vg_name, vg)) == 0)
> +
> + ret = vg_create( vg_name, vg);
> + if ( ret == -LVM_EVG_CREATE_REMOVE_OPEN) {
> + vg_create_dir_and_group( vg);
> + ret = vg_create ( vg_name, vg);
> + }
> + if ( ret == 0)
> printf ( "%s -- volume group \"%s\" successfully activated\n",
> cmd, vg_name);
> else {
>
> --
> Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
> \ would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Bartningstr. 12
64289 Darmstadt
Germany
Mauelshagen@Sistina.com +49 6151 7103 86
FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2000-10-02 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-01 3:02 [linux-lvm] need help to recover my system Les Hazelton
2000-10-01 10:01 ` Heinz J. Mauelshagen
2000-10-01 15:42 ` Les Hazelton
2000-10-01 18:10 ` Heinz J. Mauelshagen
2000-10-01 22:54 ` Les Hazelton
2000-10-02 4:49 ` Andreas Dilger
2000-10-02 6:33 ` Les Hazelton
2000-10-02 10:26 ` Heinz J. Mauelshagen
2000-10-02 9:10 ` Les Hazelton
2000-10-02 14:58 ` Les Hazelton
2000-10-02 10:20 ` Heinz J. Mauelshagen [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=20001002102054.A7806@srv.t-online.de \
--to=heinz.mauelshagen@t-online.de \
--cc=Mauelshagen@Sistina.com \
--cc=adilger@turbolinux.com \
--cc=linux-lvm@msede.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