linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with vgscan
Date: Mon, 12 Mar 2001 11:25:08 -0700 (MST)	[thread overview]
Message-ID: <200103121825.f2CIP8l04898@webber.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.30.0103100129080.12825-201000@hq.nawigator.pl> from Lukasz Trabinski at "Mar 10, 2001 01:36:38 am"

Lukasz Tribinski writes:
> I'm posting patched pv_read_all_pv_of_vg.c, too verify it.

Not related to the problem, AFAICS.

> OK. There is gzipped output from vgscan -v -d

It looks like it is not able to find LEs which are assigned to this LV.

What version of tools do you have?  It appears that with all of the
"lvm_add_dir_cache" calls you have an old version (this was fixed a few
weeks ago).  Maybe you should try the tools from CVS.

It appears you have two PVs - hdg1 and hdh1, correct?  Other than that,
I can't see what is missing.  Maybe "pvdata -a /dev/hd[gh]1" will help.
It will be long again (you have 16k+ LEs there), but it should show the
LE numbers on both PVs.

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

  parent reply	other threads:[~2001-03-12 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 23:31 [linux-lvm] Problems with vgscan Lukasz Trabinski
2001-03-10  0:04 ` Andreas Dilger
2001-03-10  0:36   ` Lukasz Trabinski
2001-03-12 14:16     ` Lukasz Trabinski
2001-03-12 18:25     ` Andreas Dilger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-24 19:00 [linux-lvm] problems " jorg de jong
2000-03-25 14:03 ` Heinz 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=200103121825.f2CIP8l04898@webber.adilger.int \
    --to=adilger@turbolinux.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).