linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM don't work anymore (wrong version?)
Date: Wed, 14 Feb 2001 17:56:02 +0000	[thread overview]
Message-ID: <20010214175602.I2960@srv.sistina.com> (raw)
In-Reply-To: <B45465FD9C23D21193E90000F8D0F3DF683959@mailsrv.linkvest.ch>; from Jean-Eric.Cuendet@linkvest.com on Wed, Feb 14, 2001 at 05:45:04PM +0100

On Wed, Feb 14, 2001 at 05:45:04PM +0100, Jean-Eric Cuendet wrote:
> 
> > > pvcreate -- ERROR: VGDA in kernel and lvmtab are NOT 
> > consistent; please run
> > > vgscan
> > > What's that?
> > 
> > You shouldn't be able to get that message with LVM 0.9.1 beta3 at all.
> > Are you by accident using an older version?
> 
> No, I'm sure it's beta3 and after beta4 (I tried it, just in case)
> 
> > If vgscan still complains and you have your 
> > /etc/lvmconf/vg.conf (assuming
> > that your VG is named vg :) VGDA backup file you can reactivate your
> > VG with:
> > 
> > rm -rf /etc/lvmtab*
> > mkdir /etc/lvmtab.d
> > echo -ne "vg\0" > /etc/lvmtab
> > cp /etc/lvmconf/vg.conf /etc/lvmtab.d/vg
> > vgchange -ay
> 
> It works! Thanks.

You're welcome.

> The problem is that vgscan creates a file /etc/lvmtab without the VG name.
> The file had only \0 in it!
> I think that there is a bug. Would you like that I try somethng else?

The problem you are facing is probably related to a PV UUID bug we
recently fixed.
Send me the output of:

pvscan
pvscan -u

before changing anything in your VG.

> I'll reboot the server this evening, so I'll have beta4 for tools AND
> kernel.
> Thanks for your help.
> -jec
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz    -- The LVM Guy --

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-02-14 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 16:45 [linux-lvm] LVM don't work anymore (wrong version?) Jean-Eric Cuendet
2001-02-14 17:56 ` Heinz J. Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-16  7:41 Jean-Eric Cuendet
2001-02-16 17:11 ` Andreas Dilger
2001-02-15 10:21 Jean-Eric Cuendet
2001-02-15 20:03 ` Andreas Dilger
2001-02-14 10:15 Jean-Eric Cuendet
2001-02-14 17:26 ` 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=20010214175602.I2960@srv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).