Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Please Help, vgscan finds too much LEs
Date: Mon Sep  9 06:26:22 2002	[thread overview]
Message-ID: <20020909125734.C15934@sistina.com> (raw)
In-Reply-To: <3D78E549.8408.39D5AA@localhost>; from thorsten.pawlak@gmx.net on Fri, Sep 06, 2002 at 05:26:33PM +0200

On Fri, Sep 06, 2002 at 05:26:33PM +0200, T. Pawlak wrote:
> Hi,
> 
> this is the second email for my problem. Unfortunately i haven't got an answer to my 
> first one. So i'm posting again.
> 
> After i've pvreduce my VG vgscan can't activate it. here is the output:
> 
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- only found 28926 of 28672 LEs for LV /dev/data/home (0)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get data of 
> volume group "data" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> group
> 
> i don't know what i can do, it is very funny problem because 28926 LEs are found of 
> and only 28672 sems to be needed, where are the 254 LEs from?!?

That looks really odd :(

Could you send me the "dd bs=1k count=4k" of all PVs tar'ed+bzip2'ed to
mge@sistina.com and the /etc/lvmconf/data* archives as well, please.

> 
> i've made a pvdata -Eva from all 5 PEs, the file is about 1mb of size, so dave 
> everyones bandwidth i put it here: http://www.pawlak-world.de/pvdata
> 
> if more infos of my configuration is needed please conact me!
> 
> i'm using LVM v1.0.5 with kernel patch (i upgraded from 1.0.3 before i made the 
> pvreduce)
> 
> I hope someone can help me now! It would be very nice if i can reconstruct my data, 
> although i have a backup, but only of 60gb of the whole 200gb and it would be nice to 
> access the rest again somehow!
> 
> bye Thorsten
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

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:[~2002-09-09  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 10:27 [linux-lvm] Please Help, vgscan finds too much LEs T. Pawlak
2002-09-09  6:26 ` 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=20020909125734.C15934@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