Linux LVM users
 help / color / mirror / Atom feed
From: Guillaume Duquesnay <gduquesnay@cgg.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] VG lost, no lvmconf => Help !
Date: Thu Jan 24 09:18:03 2002	[thread overview]
Message-ID: <3C50250F.40209@cgg.com> (raw)
In-Reply-To: 20020124154339.A8972@sistina.com

Heinz J . Mauelshagen wrote:

> Can you send "vgscan -d" to me in personal email (mge@sistina.com)?
OK, i'll do that.

> What does lvm-1.0.1-1 mean. We don't have such version.

In fact, 1.0.1-1-mdk (Mandrake), you can find it on rpmfind.net

> Please check with for eg. "vgdisplay -h".

---------------
vgdisplay -h
Logical Volume Manager 1.0.1
Heinz Mauelshagen, Sistina Software  26/11/2001 (IOP 10)

vgdisplay -- display volume group information

vgdisplay [-c|--colon | -s|--short | -v[v]|--verbose [--verbose]]
         [-d|--debug] [-h|--help] [--version]
         [-A|--activevolumegroups | [-D|--disk] [VolumeGroupName...] ]

---------------


A little more info :

i tried to reimport the old PVs
----------------
]# vgimport -f -v main /dev/sda1 /dev/sda3
vgimport -- locking logical volume manager
vgimport -- checking volume group name
vgimport -- checking volume group "main" existence
vgimport -- trying to read physical volumes
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/sda1"
vgimport -- reading data of physical volume "/dev/sda1" from disk
vgimport -- checking for exported physical volume "/dev/sda1"
vgimport -- reallocating memory
vgimport -- checking consistency of physical volume "/dev/sda1"
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/sda3"
vgimport -- reading data of physical volume "/dev/sda3" from disk
vgimport -- checking for exported physical volume "/dev/sda3"
vgimport -- reallocating memory
vgimport -- checking consistency of physical volume "/dev/sda3"
vgimport -- physical volumes "/dev/sda3" and "/dev/sda1" are in 
different volume groups

----------------

Next, i said my pvdata was identical for /dev/sda1 and /dev/sda3, but i 
discover that was'nt true :
---------------
#]pvdata -P /dev/sda3
--- Physical volume ---
PV Name               /dev/sda3
VG Name               main
PV Size               1.39 GB / NOT usable 7.65 MB [LVM: 125.00 KB]
PV#                   2
PV Status             NOT available
Allocatable           yes
Cur LV                1
PE Size (KByte)       4096
Total PE              355
Free PE               99
Allocated PE          256
PV UUID               none
----------------
see that PVUUID ?

So i did try uuid_fixer, which finally give me a human readable error :
----------------
]# ./uuid_fixer /dev/sda1 /dev/sda3
/dev/sda3 - UUID corrupt
----------------
Damned.
So where do we go now ?
thanks,

Guillaume

  reply	other threads:[~2002-01-24  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 10:08 [linux-lvm] VG lost, no lvmconf => Help ! Guillaume Duquesnay
2002-01-24  8:47 ` Heinz J . Mauelshagen
2002-01-24  9:18   ` Guillaume Duquesnay [this message]
2002-01-24 10:17     ` Heinz J . Mauelshagen
2002-01-24 11:55       ` [Re: [linux-lvm] VG lost, no lvmconf => Help ! ] Corrupted PV UUID Guillaume Duquesnay
2002-01-25  4:12         ` Heinz J . Mauelshagen

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=3C50250F.40209@cgg.com \
    --to=gduquesnay@cgg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox