From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume diff
Date: Thu, 23 Apr 2015 03:43:35 +0000 (UTC) [thread overview]
Message-ID: <pan$5278$86c57e90$b5f9efb5$e578b832@cox.net> (raw)
In-Reply-To: 201504221808.30242.thomas@koch.ro
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...]
The closest thing in git-master, based on my build from a few days ago,
is btrfs subvolume find-new. That lists the recently modified files
since <generation>, where generation is fed to the command, with a
subvolume's current generation obtainable btrfs subvolume list using its
-g option. (btrfs subvolume show might also list current gen, the manpage
is vague on what information it shows, and without local subvolumes to
test it with...)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-04-23 3:43 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 [this message]
2015-04-23 4:53 ` Marc MERLIN
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='pan$5278$86c57e90$b5f9efb5$e578b832@cox.net' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).