2,257
edits
Changes
Jump to navigation
Jump to search
Line 34:
Line 34: + + + + + + + + + + + +
Added into about dedup
{{Note|After each (but the last) dump tasks continue running and thus can modify filesystem. CRIU doesn't snapshot filesystem and assumes, that proper filesystem state for restore is provided by user}}
{{Note|After each (but the last) dump tasks continue running and thus can modify filesystem. CRIU doesn't snapshot filesystem and assumes, that proper filesystem state for restore is provided by user}}
== Data deduplication ==
After creation of such stack of images some data would get duplication in dumps. If you don't want to keep duplicates there's an ability to punch duplicate data from non-top images. There are two options for this.
; Deduplication action
: The <code>crui dedup</code> command would open the image directory and punch holes in the ''parent'' images in needed places
; Automatic deduplication while dumping
: The <code>--auto-dedup</code> option would cause every write to images with process' pages to go an punch holes in respective parent images.
The latter option appies to both <code>dump</code> and <code>page-server</code> actions and thus is extremely useful in [[disk-less migration]] scenario.
[[Category:HOWTO]]
[[Category:HOWTO]]