From: Klaus Agnoletti <ultra@mailme.dk>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Problems after upgrading LVM
Date: Mon Dec 3 12:36:02 2001 [thread overview]
Message-ID: <1007411943.2423.2.camel@ultra> (raw)
Hi,
I recently updated from linux 2.4.6 to 2.4.13-ac8, from LVM 0.9something
to 1.0.1rc4.
I am using debian, so I grabbed the two packages - lvm10 and lvm-common.
Something must be wrong though, cause I can't mount my LVM anymore.
This is what happens :
Vault:~# mount /glftpd/site
mount: /dev/site_vg/lvol1 is not a valid block device
Vault:~# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/hda8" is associated to an unknown VG (run
vgscan)
pvscan -- inactive PV "/dev/hdb1" is associated to an unknown VG (run
vgscan)
pvscan -- total: 2 [71.35 GB] / in use: 2 [71.35 GB] / in no VG: 0 [0]
Vault:~# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
group
Vault:~# vgcfgrestore -n site_vg /dev/hdb1
vgcfgrestore -- ERROR: different structure size stored in
"/etc/lvmconf/site_vg.conf" than expected in file vg_cfgrestore.c [line
139]
vgcfgrestore -- ERROR "vg_cfgrestore(): read" restoring volume group
"site_vg"
Vault:~# vgchange -ay
vgchange -- no volume groups found
What's the matter ? Is it a problem that can be fixed by uuid_fixer ?
Thanks in advance,
Klaus
next reply other threads:[~2001-12-03 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 12:36 Klaus Agnoletti [this message]
2001-12-03 15:04 ` [linux-lvm] Problems after upgrading LVM Petro
2001-12-04 0:55 ` Klaus Agnoletti
2001-12-06 0:18 ` Klaus Agnoletti
2001-12-06 4:00 ` Ulrich Wiederhold
2001-12-10 21:05 ` [linux-lvm] reinstall system with volumes intact? Steve Wray
2001-12-12 0:15 ` [linux-lvm] reinstall, import, export question Steve Wray
2001-12-12 0:47 ` Steven Lembark
2001-12-12 7:46 ` Lewis Bergman
2001-12-12 16:12 ` Steve Wray
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=1007411943.2423.2.camel@ultra \
--to=ultra@mailme.dk \
--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.