From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs diff between snapshosts
Date: Mon, 19 May 2014 19:06:06 -0700 [thread overview]
Message-ID: <20140520020606.GA10656@merlins.org> (raw)
As a followup on the discussion we had on how to do a live data switch
on a partition without unmounting it since it's busy, it came back to
how do you know what changed between 2 snapshots.
btrfs send giving a file list of what was added/modified/removed is the
long term answer, and Filipe is working on patches that will offer this
in the future (thanks Filipe).
In the meantime, I found a hack/script that gives a partial diff between
2 snapshots, called it btrfs-diff but then remembered that there isn't a
page for it.
So, I made one, along with example usage:
http://marc.merlins.org/perso/btrfs/post_2014-05-19_Btrfs-diff-Between-Snapshots.html
Hope this helps.
As another temp hack, I tried to look at a quick way to parse btrfs send
output to just spit out filenames, but that wasn't too trivial (as in
with sed/perl).
If someone has something better, please share :)
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
reply other threads:[~2014-05-20 2:06 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=20140520020606.GA10656@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
/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.