All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problem with UUID, vgscan, vgcfgrestore
Date: Fri, 27 Apr 2001 10:47:02 +0000	[thread overview]
Message-ID: <20010427104702.A16169@sistina.com> (raw)
In-Reply-To: <200104251626.f3PGQf2M031290@webber.adilger.int>; from adilger@turbolinux.com on Wed, Apr 25, 2001 at 10:26:41AM -0600

On Wed, Apr 25, 2001 at 10:26:41AM -0600, Andreas Dilger wrote:
> David Vidal writes:
> > I'll send them tomorrow. You say that there are problems with VGs created
> > with <beta4. My kernel is has beta2-lvm, and because of compiling errors
> > in the newer beta6+-versions, I couldn't update the driver (tools are
> > actually working). Is there a way to [sozusagen] update the on-disc
> > structures in order to avoid conflicts with the new tools?
> 
> It doesn't matter what version the kernel code is, as long as the tools
> are newer than beta2 you are OK.  If the on-disk UUIDs are bad, then
> all you need to do is some sort of simple change (add a 1 PE LV and
> remove it), and the on-disk VGDA should be re-written with the correct
> UUIDs.
> 
> You can check the on-disk UUIDs with "pvdata -U" for each PV.  They
> should all match.

I am about to implement a vgscan option in order to support the recreation
of the "invalid PV UUID list problem" in case a VG can't be found by vgscan
any more.

What's your opinion (Andreas?) about it?

Do we have too many people which can't do the lvcreate/lvremove trick
so that this work makes sense?

> 
> Cheers, Andreas
> -- 
> 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
> _______________________________________________
> 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-04-27 10:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02  5:43 [linux-lvm] Problem with UUID, vgscan, vgcfgrestore Diederick van Dijk
2001-04-02 21:00 ` Andreas Dilger
2001-04-03  5:34   ` Diederick van Dijk
2001-04-03  6:23     ` Andreas Dilger
2001-04-03  7:51       ` Diederick van Dijk
2001-04-03 20:43         ` Diederick van Dijk
2001-04-03 21:36           ` Andreas Dilger
2001-04-03 22:15             ` Diederick van Dijk
2001-04-03 22:30               ` Andreas Dilger
2001-04-25 11:51     ` David Vidal Rodriguez
2001-04-25 15:49       ` Heinz J. Mauelshagen
2001-04-25 14:03         ` David Vidal Rodriguez
2001-04-25 16:26           ` Andreas Dilger
2001-04-27 10:47             ` Heinz J. Mauelshagen [this message]
2001-04-30 18:16               ` Andreas Dilger
2001-05-02 12:45                 ` 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=20010427104702.A16169@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.