From: Dariush Forouher <dariush@forouher.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Strange pvmove problem
Date: Fri, 28 Jul 2006 12:19:41 +0200 [thread overview]
Message-ID: <44C9E4BD.9070204@forouher.de> (raw)
Hi!
I'm trying to move PEs away from two PVs (because I want to remove the
disks from the system), but pvmove always fails:
# pvmove /dev/hdd1 /dev/sda3
Wiping cache of LVM-capable devices
Finding volume group "LVM"
Archiving volume group "LVM" metadata (seqno 51).
Creating logical volume pvmove0
Moving 3468 extents of logical volume LVM/data
Found volume group "LVM"
Updating volume group metadata
Creating volume group backup "/etc/lvm/backup/LVM" (seqno 52).
Found volume group "LVM"
Found volume group "LVM"
Suspending LVM-data (253:1)
Found volume group "LVM"
Creating LVM-pvmove0
Loading LVM-pvmove0 table
device-mapper: reload ioctl failed: Invalid argument
ABORTING: Temporary mirror activation failed. Run pvmove --abort.
Found volume group "LVM"
Loading LVM-pvmove0 table
device-mapper: reload ioctl failed: Invalid argument
Loading LVM-data table
device-mapper: reload ioctl failed: Invalid argument
After that the system remains in an unstable state. All [vg|pv|lv]*
commands hang and the LV becomes unaccessible too.
After rebooting and excecuting "pvmove" without any arguments the VG
becomes accessible again and I'm back where I started (without any PE
moved). Trying to move data from another PV makes no difference.
The system's running with Debian Testing and Kernel 2.6.16.16.
Can anyone please help me finding out whats causing this?
ciao
Dariush
# pvdisplay
File descriptor 3 left open
File descriptor 4 left open
File descriptor 6 left open
File descriptor 8 left open
--- Physical volume ---
PV Name /dev/hda3
VG Name LVM
PV Size 129.48 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 33147
Free PE 33147
Allocated PE 0
PV UUID uc4kn4-xMQ7-M4vw-1thl-OcCF-LIV9-aeRTn0
--- Physical volume ---
PV Name /dev/hdd1
VG Name LVM
PV Size 37.27 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 9541
Free PE 6073
Allocated PE 3468
PV UUID tNzm5d-ClTt-0vJ6-ZQA9-0eYQ-IwKy-tbxV6o
--- Physical volume ---
PV Name /dev/sda3
VG Name LVM
PV Size 214.19 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 54833
Free PE 54734
Allocated PE 99
PV UUID CfA2kz-5Gt8-Zshc-3Eou-fscj-1Lfn-xOEQSY
--- Physical volume ---
PV Name /dev/sdb1
VG Name LVM
PV Size 232.88 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 59618
Free PE 0
Allocated PE 59618
PV UUID L6S26w-zr8S-t0RN-si42-zWEd-rJA5-Ms0JIb
# vgdisplay
File descriptor 3 left open
File descriptor 4 left open
File descriptor 6 left open
File descriptor 8 left open
--- Volume group ---
VG Name LVM
System ID
Format lvm2
Metadata Areas 4
Metadata Sequence No 55
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 4
Act PV 4
VG Size 613.82 GB
PE Size 4.00 MB
Total PE 157139
Alloc PE / Size 63185 / 246.82 GB
Free PE / Size 93954 / 367.01 GB
VG UUID GoVzA8-HPSg-FNhr-6fM3-Fo94-k2IG-462F9E
# lvdisplay
File descriptor 3 left open
File descriptor 4 left open
File descriptor 6 left open
File descriptor 8 left open
--- Logical volume ---
LV Name /dev/LVM/data
VG Name LVM
LV UUID zscrIa-BwvW-rktv-3L5P-QP67-BkfG-ri3NZL
LV Write Access read/write
LV Status available
# open 1
LV Size 246.82 GB
Current LE 63185
Segments 3
Allocation inherit
Read ahead sectors 0
Block device 253:1
next reply other threads:[~2006-07-28 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 10:19 Dariush Forouher [this message]
2006-07-28 13:13 ` [linux-lvm] Strange pvmove problem Dieter Stüken
2006-07-28 13:43 ` Dariush Forouher
2006-07-28 15:00 ` Dieter Stüken
2006-07-28 16:21 ` Dariush Forouher
2006-07-31 14:15 ` Heinz Mauelshagen
2006-08-16 7:35 ` Dariush Forouher
2006-07-28 22:45 ` Dariush Forouher
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=44C9E4BD.9070204@forouher.de \
--to=dariush@forouher.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.