Linux LVM users
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Trouble: Shortened LV and vgscan fails...
Date: Wed, 5 Sep 2001 19:36:00 +0200	[thread overview]
Message-ID: <20010905193600.A23151@lug-owl.de> (raw)

Hi!

I've hit some problem...

I've (had?) one PV (one large partition on a 100GB Maxtor HDD) which
made up one VG, called data_vg usind a PE size of 1GB.. In this VG I
had so far one LV, called data_lv, using all but one PE of data_vg.

I wanted to make this LV smaller (-= 8PEs), using e2fsadm, but this
failed. The LV was still there, so I mounted it and the FS was
of the right (shortened) size, but after a reboot, vgscan fails.
Any hint on how to reactivate the VG?

MfG, JBG

# ------ short version -------
mirror:~# vgscan 
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "data_vg"
vgscan -- only found 83 of 82 LEs for LV /dev/data_vg/data_lv (0)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get data of volume group "data_vg" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating "/etc/lvmtab" and "/etc/lvmtab.d"


Long Version: http://dvmwest.gt.owl.de/~jbglaw/lvm-error.txt

# ------ long version snipplets -------
[...]
<22> pv_read_all_pe_of_vg -- /dev/hda1 with 92 PE at address 804CB88
[...]
<22> lv_read_all_lv -- BEFORE pv_read_all_pv_of_vg
<333> pv_read_all_pv_of_vg -- CALLED with vg_name: "data_vg"
<4444> vg_check_name -- CALLED with VG: data_vg
<55555> lvm_check_chars -- CALLED with name: "data_vg"
<55555> lvm_check_chars -- LEAVING with ret: 0
<4444> vg_check_name -- LEAVING with ret: 0
<333> pv_read_all_pv_of_vg -- LEAVING with ret: 0
<333> lv_copy_from_disk -- CALLED
<333> lv_copy_from_disk -- LEAVING
<22> lv_read_all_lv -- l: 255  nl: 1  vg_this->lv_cur: 1
<22> lv_read_all_lv -- LEAVING with ret: 0
<1> vg_read_with_pv_and_lv -- AFTER lv_read_all_lv; vg_this->pv_cur: 1  vg_this->pv_max: 255  ret: 0
<1> vg_read_with_pv_and_lv -- BEFORE for PE
<1> vg_read_with_pv_and_lv -- AFTER for PE
<1> vg_read_with_pv_and_lv -- BEFORE for LV
<1> vg_read_with_pv_and_lv -- vg_this->lv[0]->lv_allocated_le: 82
vgscan -- only found 83 of 82 LEs for LV /dev/data_vg/data_lv (0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<1> vg_read_with_pv_and_lv -- LEAVING with ret: -365
<1> lvm_error -- CALLED with: -365
<1> lvm_error -- LEAVING with: "vg_read_with_pv_and_lv(): allocated LE of LV"
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get data of volume group "data_vg" from physical volume(s)
<1> lvm_interrupt -- CALLED
<1> lvm_interrupt -- LEAVING
<1> lvm_unlock -- CALLED
<1> lvm_unlock -- LEAVING with ret: 0
<1> lvm_error -- CALLED with: -365
<1> lvm_error -- LEAVING with: "vg_read_with_pv_and_lv(): allocated LE of LV"
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating "/etc/lvmtab" and "/etc/lvmtab.d"

-- 
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481

                 reply	other threads:[~2001-09-05 17:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010905193600.A23151@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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