* question about how to incrementally rebuild an image out of cluster
@ 2014-08-21 3:07 =?gb18030?B?0KG93A==?=
0 siblings, 0 replies; only message in thread
From: =?gb18030?B?0KG93A==?= @ 2014-08-21 3:07 UTC (permalink / raw)
To: =?gb18030?B?Y2VwaC1kZXZlbA==?=
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 750 bytes --]
The rbd diff-related commands compare points in time of a single
image. Since children are identical to their parent when they're cloned,
if I created a snapshot right after it was cloned, I could export
the diff between the used child and the parent. Something like:
rbd clone child parent@snap
rbd snap create child@base
<use child image>
rbd snap create child@changed
rbd export-diff child@changed --from-snap base child_changes.diff
the questions are:
1. Does the child@base really necessary? It seems point the same obj with parent@snap, why should'n I use the parent@snap instead?
2. If I create child@base, comparing with use child image directly, are there some performance redundant or storage increment when writing the child image later?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-08-21 3:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-21 3:07 question about how to incrementally rebuild an image out of cluster =?gb18030?B?0KG93A==?=
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.