From: Frank Mohr <f_mohr@yahoo.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvscan fails (more informations)
Date: Wed, 28 Jul 2004 16:05:02 +0200 [thread overview]
Message-ID: <4107B28E.C22CF115@yahoo.de> (raw)
In-Reply-To: 4106E0D6.10D6AA3D@yahoo.de
Frank Mohr wrote:
>
> Hi
>
> after a system crash my system can't find it's LVM volumes:
>
some more informations:
- the system didn't crash but was switched of before "vgchange -a n" was
called
- pvdisplay shows "PV Status available" for all PV's
- vgcfgrestore
even some backups back doesn't help
- vgcfgrestore -t -ll -f /etc/lvmconf/DATAVG.conf -n DATAVG
showns the same results as pvdisplay
- pvdisplay on all 3 partions shown "good" results
- pvdata -a /dev/hdb1 /dev/hdc1 /dev/hdd1
looks good
displays the same "VG UUID" for all PV's
- tried vgimport -f -v DATAVG /dev/hdb1 /dev/hdc1 /dev/hdd1
odie:~/LVM/1.0.8/tools # vgimport -f -v DATAVG /dev/hdb1 /dev/hdc1
/dev/hdd1
vgimport -- locking logical volume manager
vgimport -- checking volume group name
vgimport -- checking volume group "DATAVG" existence
vgimport -- trying to read physical volumes
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/hdb1"
vgimport -- reading data of physical volume "/dev/hdb1" from disk
vgimport -- checking for exported physical volume "/dev/hdb1"
vgimport -- checking consistency of physical volume "/dev/hdb1"
vgimport -- reallocating memory
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/hdc1"
vgimport -- reading data of physical volume "/dev/hdc1" from disk
vgimport -- checking for exported physical volume "/dev/hdc1"
vgimport -- checking consistency of physical volume "/dev/hdc1"
vgimport -- reallocating memory
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/hdd1"
vgimport -- reading data of physical volume "/dev/hdd1" from disk
vgimport -- checking for exported physical volume "/dev/hdd1"
vgimport -- checking consistency of physical volume "/dev/hdd1"
vgimport -- reallocating memory
vgimport -- physical volumes "/dev/hdc1" and "/dev/hdb1" are in
different volume groups
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose]
VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]
odie:~/LVM/1.0.8/tools #
next prev parent reply other threads:[~2004-07-28 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 23:10 [linux-lvm] pvscan fails Frank Mohr
2004-07-27 23:17 ` Erik Ch. Ohrnberger
2004-07-28 14:37 ` Frank Mohr
2004-07-28 14:05 ` Frank Mohr [this message]
2004-07-28 16:37 ` [linux-lvm] pvscan fails (some more debugging - cause found) Frank Mohr
2004-08-01 10:06 ` Frank Mohr
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=4107B28E.C22CF115@yahoo.de \
--to=f_mohr@yahoo.de \
--cc=linux-lvm@redhat.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.