All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume diff
Date: Wed, 22 Apr 2015 21:53:11 -0700	[thread overview]
Message-ID: <20150423045311.GB20088@merlins.org> (raw)
In-Reply-To: <pan$5278$86c57e90$b5f9efb5$e578b832@cox.net>

On Thu, Apr 23, 2015 at 03:43:35AM +0000, Duncan wrote:
> Thomas Koch posted on Wed, 22 Apr 2015 18:08:30 +0200 as excerpted:
> 
> > for incremental backups it would be useful to know the files that
> > changed between two snapshots. I found a paper about such a tool[1] that
> > adds the "btrfs subvolue diff" command, but it's not yet implemented in
> > btrfs-tools in Debian Jessie.
> > 
> > Is it in Git? Or somewhere else?
> > 
> > [1] https://www.kernel.org/doc/ols/2014/ols2014-pimpale.pdf
> 
> [Note that I'm just a btrfs user and list regular, not a dev, and that my 
> own use-case doesn't involve subvolumes, tho I played with them a bit 
> when I first got into btrfs, so my practical subvolume management 
> knowledge is limited.  But based on current git's manpages...]

Not a great answer but better than nothing:
http://marc.merlins.org/perso/btrfs/2014-05.html#Btrfs-diff-Between-Snapshots

(based on find-new)

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:[~2015-04-23  4:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 16:08 btrfs subvolume diff Thomas Koch
2015-04-23  3:43 ` Duncan
2015-04-23  4:53   ` Marc MERLIN [this message]

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=20150423045311.GB20088@merlins.org \
    --to=marc@merlins.org \
    --cc=1i5t5.duncan@cox.net \
    --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.