Linux LVM users
 help / color / mirror / Atom feed
From: Florian Hinzmann <f.hinzmann@hamburg.de>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] Error after moving volume group to another machi
Date: Wed Sep  4 06:01:01 2002	[thread overview]
Message-ID: <XFMail.20020904130102.f.hinzmann@hamburg.de> (raw)
In-Reply-To: <XFMail.20020903224718.f.hinzmann@hamburg.de>

Uh, oh, replying to myself:

On 03-Sep-2002 Florian Hinzmann wrote:

> But the moved VG isn't detected properly. This is what I get:
> vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of volume group "vg01" from physical volume(s)
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found inactive volume group "vgpum01"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume groups

The disks are back in their original machine currently. 


pvdata gives me:

--- Physical volume ---
PV Name               /dev/hdb1
VG Name               vg01
PV Size               76.34 GB [160086526 secs] / NOT usable 8.19 MB [LVM: 166 KB]
PV#                   4
PV Status             available
Allocatable           yes (but full)
Cur LV                5
PE Size (KByte)       8192
Total PE              9769
Free PE               0
Allocated PE          9769
PV UUID               jRyOAJ-1KHk-564T-jrQS-BHWC-OKhu-JiL9d4

--- Volume group ---
VG Name               
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                256
Cur LV                9
Open LV               0
MAX LV Size           511.98 GB
Max PV                256
Cur PV                4
Act PV                4
VG Size               212.07 GB
PE Size               8 MB
Total PE              27145
Alloc PE / Size       27145 / 212.07 GB
Free  PE / Size       0 / 0
VG UUID               BVZr37-mltv-69XE-pnBS-5ryg-NcKL-k6Fcfy

--- List of logical volumes ---

pvdata -- logical volume "/dev/vg01/home" at offset   0
pvdata -- logical volume "/dev/vg01/usr" at offset   1
[...]


"VG Name" in "--- Volume group ---" is empty. Is this normal? In case
this or some other errors within the data structures within one or
more partitions is the cause of my problems: 
My setup is currently working obviosly. Is there a way to write this
working configuration into every LVM partition's metadata overwriting 
some possible errors there?


 Regards
    Florian


--
  Florian Hinzmann                         private: f.hinzmann@hamburg.de
                                            Debian: fh@debian.org
PGP Key / ID: 1024D/B4071A65
Fingerprint : F9AB 00C1 3E3A 8125 DD3F  DF1C DF79 A374 B407 1A65

  reply	other threads:[~2002-09-04  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 15:47 [linux-lvm] Error after moving volume group to another machine Florian Hinzmann
2002-09-04  6:01 ` Florian Hinzmann [this message]
2002-09-04  8:17   ` [linux-lvm] Error after moving volume group to another machi Heinz J . Mauelshagen
2002-09-06  6:51     ` Florian Hinzmann

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=XFMail.20020904130102.f.hinzmann@hamburg.de \
    --to=f.hinzmann@hamburg.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