Dieter Stüken wrote:
> Dariush Forouher wrote:
>> I'm trying to move PEs away from two PVs (because I want to remove the
>> disks from the system), but pvmove always fails:
>
> I had some problems with pvmove some time ago, if the PV to empty
> contained parts from several different LVs. But this was due to some
> old bug with a 2.6.12 or 13 kernel. May be it's interesting to have
> a look into /etc/lvm/backup/LVM and the associated backups,
> to understand whats going on.
Uhm, this is the file created right before I started pvmove:
<SNIP>
# Generated by LVM2: Fri Jul 28 10:15:24 2006
contents = "Text Format Volume Group"
version = 1
description = "Created *before* executing 'pvmove -v /dev/hdd1 /dev/hda3'"
creation_host = "palomar" # Linux palomar 2.6.16.16 #2 PREEMPT Sun
May 14 13:56:04 CEST 2006 i686
creation_time = 1154074524 # Fri Jul 28 10:15:24 2006
LVM {
id = "GoVzA8-HPSg-FNhr-6fM3-Fo94-k2IG-462F9E"
seqno = 39
status = ["RESIZEABLE", "READ", "WRITE"]
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
physical_volumes {
pv0 {
id = "uc4kn4-xMQ7-M4vw-1thl-OcCF-LIV9-aeRTn0"
device = "/dev/hda3" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 33147 # 129.48 Gigabytes
}
pv1 {
id = "tNzm5d-ClTt-0vJ6-ZQA9-0eYQ-IwKy-tbxV6o"
device = "/dev/hdd1" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 9541 # 37.2695 Gigabytes
}
pv2 {
id = "CfA2kz-5Gt8-Zshc-3Eou-fscj-1Lfn-xOEQSY"
device = "/dev/sda3" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 54833 # 214.191 Gigabytes
}
pv3 {
id = "L6S26w-zr8S-t0RN-si42-zWEd-rJA5-Ms0JIb"
device = "/dev/sdb1" # Hint only
status = ["ALLOCATABLE"]
pe_start = 384
pe_count = 59618 # 232.883 Gigabytes
}
}
logical_volumes {
data {
id = "zscrIa-BwvW-rktv-3L5P-QP67-BkfG-ri3NZL"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 3
segment1 {
start_extent = 0
extent_count = 59618 # 232.883 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv3", 0
]
}
segment2 {
start_extent = 59618
extent_count = 3468 # 13.5469 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 6073
]
}
segment3 {
start_extent = 63086
extent_count = 99 # 396 Megabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv2", 54734
]
}
}
}
}
</SNIP>
I diff'ed it againt more recent backups and against /etc/lvm/backup/LVM.
They are pretty much the same (except the "seqno" attribute).
I'd be already happy if I could free /dev/sda3 (which is _nearly_
unused). Then I could create a new VG and move the files around by hand
(like in the old days, when we had to use partitions). But even thats
not possible since all disks big enough to hold the data are bound by
this (damaged?) VG.
ciao
Dariush
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
