On Thu, Nov 18, 2010 at 3:12 PM, Alasdair G Kergon <agk@redhat.com> wrote: > On Thu, Nov 18, 2010 at 01:30:11PM -0500, Stirling Westrup wrote: >> I do think the fact that pvmove does no user-visible checkpointing is >> a bug. > > The man page explains how pvmove works. No data is removed until it > is safely available in its new location. pmove's man page leaves a LOT to be desired. It gives the bare syntax of saying how to move individual extents, or ranges thereof, but gives no semantic information whatsoever. It doesn't even go so far as to SAY that the syntax is for moving individual extents. It mentions checkpointing, but gives no further information. It certainly doesn't say anything about how often they are done, or under what circumstances. Nor is there any mention of how one would know when the last checkpoint was taken. I'm not the first person who's asked about this either, as I discovered while trying to google for information that should have been in the man page. > Checkpoints are done after each contiguous piece of data to move. > So if your data is contiguous, you'll get no checkpoints. > The code was designed to handle more-frequent checkpoints in such > cases, but nobody's seen the need to implement that feature yet. > (I don't think we even have a bugzilla requesting it.) Perhaps no one has made a request, because there isn't even enough information available for someone to KNOW what to request? -- Stirling Westrup Programmer, Entrepreneur. https://www.linkedin.com/e/fpf/77228 http://www.linkedin.com/in/swestrup http://technaut.livejournal.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/
