Dne 27.3.2014 12:32, Derek Dongray napsal(a):
Following some disk errors while I was moving some extents, I now have a
hidden locked [pvmove0] which doesn't seem to have any physical extents
assigned, although it is shown as 4Mb long.
# lvs -a -o+seg_pe_ranges a/pvmove0
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync
Convert PE Ranges
[pvmove0] a vwC---v--- 4.00m
The simple 'lvremove a/pvmove0' (optionally with '--force') results in the
message 'Can't remove locked LV pvmove0'.
'pvmove --abort' does nothing. The presence of this volume doesn't seem to
affect other moves (which simply use [pvmove1]).
pvmove --abort has to work - unless you have some ancient version of lvm2 tools?
What's the vresion in use ?
(You could always hack your lvm2 metadata in 'vi' - if you know what you
are doing...)
Zdenek
_______________________________________________
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/
