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] Help: lvm 0.9.1_beta3 oops (desperate plea)
Date: Mon, 29 Jan 2001 16:35:48 +0000	[thread overview]
Message-ID: <20010129163548.K8567@srv.sistina.com> (raw)
In-Reply-To: <200101290653.f0T6r2h26300@webber.adilger.net>; from adilger@turbolinux.com on Sun, Jan 28, 2001 at 11:53:02PM -0700

Andreas has a good point here.

Minor correction: the names of the functions are pv_read_all_pv()
and pv_read_all_pv_of_vg().

On Sun, Jan 28, 2001 at 11:53:02PM -0700, Andreas Dilger wrote:
> Joe Harvell writes:
> > I really, really, really need the data that is on this VG.
> > 
> > So if anyone at Sistina really wants to get to the bottom of this, you
> > just got yourself a dedicated beta-tester.  I am an experienced software
> > developper with a small amount of Linux device-driver experience.  I can
> > provide hexdumps of the relevant portions of the actual partitions.
> > I am willing to run any series of tests on this machine to help find
> > the root cause of this problem.  Whatever it takes.
> 
> Not that I'm from Sistina, but one thing you could start out checking is
> in lvm_read_all_pv_of_vg(), and print out the PV list at each step of the
> way.  It may be possible that some of the PVs are being removed from the
> list, even though they are not supposed to.  The first list, returned
> from lvm_read_all_pv(), should be all of the PVs on your system.
> 
> 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-01-29 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28 21:32 [linux-lvm] Help: lvm 0.9.1_beta3 oops (desperate plea) Joe Harvell
2001-01-29  6:53 ` Andreas Dilger
2001-01-29 16:35   ` 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=20010129163548.K8567@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).