All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problem: "only found 768 of 769 LEs for LV /dev/vg00/lvol1"
Date: Wed, 12 Sep 2001 13:10:15 +0100	[thread overview]
Message-ID: <20010912131015.A589@btconnect.com> (raw)
In-Reply-To: <2558.213.191.82.129.1000287790.squirrel@hactar.dnsalias.net>; from helldog@gmx.net on Wed, Sep 12, 2001 at 11:43:10AM +0200

Could you tell me which release of LVM you used to create the volume
group in the first place please ?

- Joe

On Wed, Sep 12, 2001 at 11:43:10AM +0200, Julian Glashoff wrote:
> Hello,
> 
> I have a problem with my volume group:
> I was using kernel 2.4.7 with LVM 1.0.1-rc1.
> I tried to extend a logical volume (/dev/vg00/lvol2) by 4Gig and got the
> error message "No such device or address in kernel".
> Then I tried to extend /dev/vg00/lvol1 by 1 extent just to test if I was
> able to change volumes at all whereupon the system completely crashed.
> On the next reboot I got the following message from vgscan:
> -------------------------------------------------------------------
> # vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found inactive volume group "vg00"
> vgscan -- only found 768 of 769 LEs for LV /dev/vg00/lvol1 (1)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get
> data of volume group "vg00" from physical volume(s)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating
> "/etc/lvmtab" and "/etc/lvmtab.d"
> -------------------------------------------------------------------
> And now I am unable to access the volume group.
> Then I tried to restore the backups with the following result:
> -------------------------------------------------------------------
> # vgcfgrestore -n vg00 -l
> vgcfgrestore -- ERROR: different structure size stored in
> "/etc/lvmconf/vg00.conf" than expected in file vg_cfgrestore.c [line 120]
> vgcfgrestore -- ERROR "vg_cfgrestore(): read" restoring volume group "vg00"
> -------------------------------------------------------------------
> The documentation says this would be caused by an incorrect LVM version.
> I was using 1.0.1-rc1 and have tried to restore the backups with every
> version from 0.9.1-beta1 up to 1.0.1-rc2 and all versions give me the same
> error.
> 
> Is there anything I can do to restore my volume group?
> 
> The output of "pvdata -a" can be found here:
> 
> http://hactar.dnsalias.net/lvm/pvdata.hda5
> http://hactar.dnsalias.net/lvm/pvdata.hda7
> http://hactar.dnsalias.net/lvm/pvdata.hdc2
> 
> --
> Julian Glashoff
> <helldog@gmx.net>
> 
> 
> 
> _______________________________________________
> 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

      reply	other threads:[~2001-09-12 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-12  9:43 [linux-lvm] Problem: "only found 768 of 769 LEs for LV /dev/vg00/lvol1" Julian Glashoff
2001-09-12 12:10 ` Joe Thornber [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=20010912131015.A589@btconnect.com \
    --to=thornber@btconnect.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.