Thanks Milan,
You are correct - exclusively locking the LV allows it to be pvmove'd.
I can't quite remember the steps I took but in case the following
benefits someone else, it was something along the lines of:
# lvchange -aey lv
# pvmove -n lv pv
# lvchange -aen lv
--
Russell Howe
Package: clvm
Version: 2.02.39-7
Severity: important
Forgive me if I'm mistaken, but it seems impossible to use pvmove on
lenny with clustered volume groups.
# pvmove /dev/mapper/3600508b30094ae20a92f2e5ab341002e
FATAL: Module dm_cmirror not found.
/sbin/modprobe failed: 1
As far as I
cmirror is now implemented as a userspace component that uses a generic
upstream kernel module that allows you to write a mirror log in userspace.
I recently added it to Fedora as an lvm2 subpackage, so I suggest copying
something from there:
On 02/17/2010 02:44 PM, Russell Howe wrote:
Forgive me if I'm mistaken, but it seems impossible to use pvmove on
lenny with clustered volume groups.
FYI: with upstream packages you can use pvmove on clustered LV without
cmirror if LV is activated exclusively (on one node only).
If you need
4 matches
Mail list logo