From: Nathan Brown <agent2x0r@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Switched Distro's. No more LVM; uuid issue
Date: Tue, 20 Sep 2005 22:10:26 -0500 [thread overview]
Message-ID: <de78cd7e0509202010398788bf@mail.gmail.com> (raw)
I was running Slackware 10.1 and I was required to switch over to
Fedora Core 4. I backed up my /etc/lvm folder because I knew I'd run
into problems. Well, I ran into problems as expected....
Just about any LVM related command will give me the error:
"Couldn't find device with uuid 'k4Px6F-wwSG-mDY6-tne2-RNVx-G3fI-mWUw4r"
Now, according to my volume group (homevg) backup, it is refering to
my second partition in the strip: /dev/sdb1.
Here is the output from pvdisplay.
# pvdisplay /dev/hdc4
pvdisplay Warning: Volume group homevg is not consistent
pvdisplay --- Physical volume ---
pvdisplay PV Name /dev/sdc4
pvdisplay VG Name homevg
pvdisplay PV Size 92.11 GB / not usable 0
pvdisplay Allocatable yes (but full)
pvdisplay PE Size (KByte) 4096
pvdisplay Total PE 23581
pvdisplay Free PE 0
pvdisplay Allocated PE 23581
pvdisplay PV UUID F0YSMA-brB8-gQOJ-qqV9-Lxzf-lnUe-sLgRCd
# pvdisplay /dev/hdb1 *THIS IS THE DEVICE IN QUESTION*
[...]
pvdisplay Using physical volume(s) on command line
pvdisplay Opened /dev/sdb1 RO
pvdisplay /dev/sdb1: block size is 1024 bytes
pvdisplay /dev/sdb1: lvm1 label detected
pvdisplay Closed /dev/sdb1
pvdisplay lvmcache: /dev/sdb1 now in VG homevg
pvdisplay Reading physical volume data /dev/sdb1 from disk
pvdisplay Opened /dev/sdb1 RO
pvdisplay /dev/sdb1: block size is 1024 bytes
pvdisplay Found /dev/sdb1 in VG homevg
pvdisplay Closed /dev/sdb1
pvdisplay --- Physical volume ---
pvdisplay PV Name /dev/sdb1
pvdisplay VG Name homevg
pvdisplay PV Size 111.79 GB / not usable 38.94 MB
pvdisplay Allocatable yes (but full)
pvdisplay PE Size (KByte) 32768
pvdisplay Total PE 3576
pvdisplay Free PE 0
pvdisplay Allocated PE 3576
pvdisplay PV UUID kGdagE-JBqu-WX3Z-sdm1-rJlv-FMS3-HbZ6r5
pvdisplay
pvdisplay Dumping persistent device cache to /etc/lvm/.cache
pvdisplay Wiping internal VG cache
# pvdisplay /dev/sda1
pvdisplay Warning: Volume group homevg is not consistent
pvdisplay --- NEW Physical volume ---
pvdisplay PV Name /dev/sda1
pvdisplay VG Name
pvdisplay PV Size 186.31 GB
pvdisplay Allocatable NO
pvdisplay PE Size (KByte) 0
pvdisplay Total PE 0
pvdisplay Free PE 0
pvdisplay Allocated PE 0
pvdisplay PV UUID ytCX8B-ntz8-ORnO-GZwx-xwts-baEQ-3Cce2t
OK now that I have that out of the way, here is my backup volume
group file I made just before reinstalling.
/etc/lvm/backup/homevg:
----------------------------------------------------------------------------------
Generated by LVM2: Mon Sep 19 23:07:13 2005
contents = "Text Format Volume Group"
version = 1
description = "Created *after* executing 'vgcfgbackup'"
creation_host = "localhost" # Linux localhost 2.6.7 #15 SMP Sun Sep 11
15:49:42 EDT 2005 i686
creation_time = 1127185633 # Mon Sep 19 23:07:13 2005
homevg {
id = "HdvlZ1-G66R-V4BR-Xx4d-6ghu-eejx-tWJmt6"
seqno = 11
status = ["RESIZEABLE", "READ", "WRITE"]
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
physical_volumes {
pv0 {
id = "F0YSMA-brB8-gQOJ-qqV9-Lxzf-lnUe-sLgRCd"
device = "/dev/hdg4" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 23581 # 92.1133 Gigabytes
}
pv1 {
id = "k4Px6F-wwSG-mDY6-tne2-RNVx-G3fI-mWUw4r"
device = "/dev/hde" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 28618 # 111.789 Gigabytes
}
pv2 {
id = "ytCX8B-ntz8-ORnO-GZwx-xwts-baEQ-3Cce2t"
device = "/dev/sdb1" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 47694 # 186.305 Gigabytes
}
}
logical_volumes {
homelv {
id = "tNfaTb-xv86-a2IF-VqKZ-sfn6-MSEv-F4RcdP"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 3
segment1 {
start_extent = 0
extent_count = 23581 # 92.1133 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 23581
extent_count = 28618 # 111.789 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 0
]
}
segment3 {
start_extent = 52199
extent_count = 46575 # 181.934 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv2", 0
]
}
}
}
}
-----------------------------------------------------------------------------------------------------
FINALLY:
Notice the UUID for PV2. Thats the UUID that LVM is complaining about,
but according to pvdisplay, that UUID doesnt exist.
What do I do!?
-- Nathan Brown
reply other threads:[~2005-09-21 3:10 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=de78cd7e0509202010398788bf@mail.gmail.com \
--to=agent2x0r@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).