pvmove -n /dev/xenvg/imprimatur_cache /dev/sdb /dev/sdc
Error locking on node tig-hyperc-1: Internal lvm error, check syslog
Failed to activate imprimatur_cache
syslog contains:
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Volume group for uuid not found: wKj56UijD2ZIn9d15fxqvWUwcD47TCdqsKXbiumi66SWoXQGA9Jy0sCoJo01EHpM
The UUID that it claims it can't find is the UUID of the new PV:
pvdisplay /dev/sdc
--- Physical volume ---
PV Name /dev/sdc
VG Name xenvg
PV Size 8.17 TB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 2141695
Free PE 2141695
Allocated PE 0
PV UUID NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U
vgdisplay seems to indicate that the associated volume group is OK and
has the full capacity of sdc available to it:
vgdisplay xenvg
--- Volume group ---
VG Name xenvg
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 315
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 108
Open LV 19
Max PV 0
Cur PV 2
Act PV 2
VG Size 13.25 TB
PE Size 4.00 MB
Total PE 3473500
Alloc PE / Size 122112 / 477.00 GB
Free PE / Size 3351388 / 12.78 TB
VG UUID wKj56U-ijD2-ZIn9-d15f-xqvW-UwcD-47TCdq
Has anybody seen anything like this? Any clues you might be able to
share?
Thanks.
noah
On 07/01/10 10:43, Noah Meyerhans wrote:
> pvmove -n /dev/xenvg/imprimatur_cache /dev/sdb /dev/sdc
> Error locking on node tig-hyperc-1: Internal lvm error, check syslog
> Failed to activate imprimatur_cache
>
> syslog contains:
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find device with uuid 'NeyE2O-CPSF-tP9v-kK5G-8g02-nTsw-M8Ls5U'.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Couldn't find all physical volumes for volume group xenvg.
> Jan 7 09:31:57 tig-hyperc-1 lvm[3028]: Volume group for uuid not found: wKj56UijD2ZIn9d15fxqvWUwcD47TCdqsKXbiumi66SWoXQGA9Jy0sCoJo01EHpM
>
>
Well I use LVM but in Redhat maybe you need to reaload extends on nodes:|
clvmd -R
|
Look at this:
http://kbase.redhat.com/faq/docs/DOC-3786
And make sure your lvm.conf has filters for the disks associated with
the sd* devices.
--
----------------------------------------------------------------------
"You don't know where your shadow will fall",
Somebody.-
----------------------------------------------------------------------
Ing. Olaf Reitmaier Veracierta<ola...@gmail.com>
----------------------------------------------------------------------
Personal Web Page -- http://olafrv.googlepages.com
----------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Thanks, this is the most promising lead yet. Alas, etch's clvmd is too
old to have that flag. Hopefully rebooting the nodes will take care of
that, but of course, that's not exactly something that can happen
trivially.
noah