On Sun, Sep 26, 2004 at 01:27:57PM -0700, Eric Hopper wrote:
> But, since pvmove doesn't seem to work yet, I
pvmove does work, but I am aware of the following restrictions
if you want to avoid the risk of freezing:
You must not disable o_direct when configuring;
[I've heard some distributions/architectures may do this]
You must not set log activation to 1 in the config file;
[That settings's only needed for a particular sort of debugging]
You must not pvmove a filesystem that lvm itself uses directly;
[For 2.6.8 kernels, version 2.00.24 (if compiled against up-to-date
headers that define O_NOATIME correctly) is reported to improve
things substantially in this case; for 2.4 a kernel patch
doing something similar gets applied by default.]
Don't try to mix snapshots with pvmove [untested].
I have also not tested with udev, nor with md underneath PVs.
Also:
The allocation algorithm is as yet unable to break up contiguous
space: you still have to break it up yourself if it doesn't find
enough contiguous space. [e.g. pvmove /dev/hda:100-199]
Test mode works a different way in LVM2 - it's designed for testing
and simply disables all writes at the lowest level of the code
(to guarantee safety) - but reports success to the calling function.
Many code paths don't yet say 'stop here if this is test mode' so
they stop instead with an error when they find an inconsistency
because they thought they changed something, but it got read back
unchanged.
Alasdair
--
agk@redhat.com
_______________________________________________
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/
