All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [lvm-commit] cvs commit: LVM/tools/lib pv_read_all_pv_of_vg.c
Date: Wed, 7 Feb 2001 15:35:15 -0600	[thread overview]
Message-ID: <20010207153515.O22166@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102071814030.1193-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Wed, Feb 07, 2001 at 06:29:24PM -0200

[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]

On Wed, Feb 07, 2001 at 06:29:24PM -0200, Rik van Riel wrote:
> On Wed, 7 Feb 2001, Heinz Mauelshagen wrote:
> 
> >   Modified files:        (Branch: LVM_0-9-patches)
> >     tools/lib            pv_read_all_pv_of_vg.c 
> >   Log:
> >   fixed multiple access path avoidance problem
> >   leading to removed but valid PV structure;
> >   this could probably be the reason for lost PVs we faced in the past
> 
> I've gathered a bit more debugging output to see why even
> this fix failed to make vgscan run.
> 
> It turns out the LVM utilities messed up some of the info
> in the PV headers so badly that there's no way to reasonably
> expect the LVM utilities to pick up their mess ...
> 
> I have attached the output from pvdata -a on the PVs to:
> 	http://bugzilla.sistina.com/show_bug.cgi?id=193
> 
> Would it be an idea to have some debugging tool around which
> allows us to fix (simple) things like this ourselves ?

It looks like the following *should* fix things for you (this from Patrick):

 o Grab the latest CVS code for LVM.
 o Create a very small LV (or extend an existing one) to force a meta-data
   update.
 o The UUIDs should be cleaned up

If this is not possible with your setup, or does not work for you, let me
know and we'll see what else we can do to fix the problem.

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-379-3951
1313 5th St SE, Suite 111              Fax:    612-379-3952
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
Proofread carefully to see if you any words out.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-02-07 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010207134128.9EA0716B31@postfix.conectiva.com.br>
2001-02-07 20:29 ` [linux-lvm] Re: [lvm-commit] cvs commit: LVM/tools/lib pv_read_all_pv_of_vg.c Rik van Riel
2001-02-07 21:35   ` AJ Lewis [this message]
2001-02-07 22:47     ` Rik van Riel
2001-02-07 23:00       ` Rik van Riel

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=20010207153515.O22166@sistina.com \
    --to=lewis@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.