All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@ubuntukylin.com>
To: Sage Weil <sweil@redhat.com>, Josh Durgin <josh.durgin@inktank.com>
Cc: ceph-devel@vger.kernel.org,
	MingXin Liu <mingxinliu@ubuntukylin.com>,
	Yunchuan Wen <yunchuanwen@ubuntukylin.com>,
	Li Wang <liwang@ubuntukylin.com>
Subject: [PATCH] rbd: merge diff files
Date: Mon,  5 Jan 2015 17:05:56 +0800	[thread overview]
Message-ID: <cover.1420444746.git.liwang@ubuntukylin.com> (raw)

RBD supplies the 'export-diff' to 
export a diff file between two clones. 
This is inconvinient for periodical backup, 
since a bunch of diff files wastes the disk
space by keeping multiple copies of the 
data on the same location, and complicates 
and slows down the recovery process. 
In this case, only one diff file is expected. 
This motivates us to develop a 'merge-diff' 
tool. The semantic is straightforward,
it merges two diff files into one single diff 
file. Multiple diff files could be easily 
merged by further using some simple shell 
tricks.

The patches are at:
https://github.com/ceph/ceph/pull/3292

MingXin Liu (6):
  rbd: add an option merge-diff
  rbd: parse merge-diff arguments
  rbd: write a diff description into the merged diff file
  rbd: parse diff file header for diff merging
  rbd: parse diff file body for diff merging
  rbd: test case for rbd merge-diff

Yunchuan Wen (1):
  rbd: merge two diff files into one single file

 qa/workunits/rbd/merge_diff.sh | 475 +++++++++++++++++++++++++++++++++++++++++
 src/rbd.cc                     | 384 ++++++++++++++++++++++++++++++++-
 2 files changed, 855 insertions(+), 4 deletions(-)
 create mode 100755 qa/workunits/rbd/merge_diff.sh

-- 
1.9.1


                 reply	other threads:[~2015-01-05  9:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1420444746.git.liwang@ubuntukylin.com \
    --to=liwang@ubuntukylin.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.com \
    --cc=mingxinliu@ubuntukylin.com \
    --cc=sweil@redhat.com \
    --cc=yunchuanwen@ubuntukylin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.