Difference between revisions of "Special:Badtitle/NS1198:Ploop/Why/22/en"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(Importing a new version from external source)
 
(No difference)

Latest revision as of 01:11, 24 September 2016

The idea is to do iterative migration of an image file, in the following way:

  1. Turn write tracker feature on. Now the kernel will keep track of ploop image blocks being modified.
  2. Copy all blocks of a ploop image file to a destination system.
  3. Ask write tracker which blocks were modified.
  4. Copy only these blocks.
  5. Repeat steps 3 and 4 until number of blocks is not decreasing.
  6. Freeze the container processes and repeat steps 3 and 4 last time.