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: Wed, 2 May 2001 12:45:04 +0000	[thread overview]
Message-ID: <20010502124504.G30791@sistina.com> (raw)
In-Reply-To: <200104301816.MAA19335@lynx.turbolabs.com>; from adilger@turbolinux.com on Mon, Apr 30, 2001 at 12:16:56PM -0600

On Mon, Apr 30, 2001 at 12:16:56PM -0600, Andreas Dilger wrote:
> Heinz writes:
> > 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?
> 
> It is surely a fix for some of the problems.

Which other problems do you see and are you able to define?

> Of course, the need for the
> fix will be reduced as time goes on,

That's why I asked in the first place.

Maybe the /etc/lvmconf/ to /etc/lvmtab.d/ copy and echo to /etc/lvmtab
trick plus "vgchange -ay" and dummy change on VGs does it anyway?

> so maybe a comment/#ifdef on the code
> so that it will be removed at a later date.
> 
> Cheers, Andreas
> -- 
> Andreas Dilger                               Turbolinux filesystem development
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
> _______________________________________________
> 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-05-02 12:45 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
2001-04-30 18:16               ` Andreas Dilger
2001-05-02 12:45                 ` 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=20010502124504.G30791@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.