From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Blocks changed since previous snapshot of subvolume
Date: Sat, 19 Mar 2016 00:13:34 +0000 (UTC) [thread overview]
Message-ID: <pan$7e7ac$bd9bc70$d69021d4$d407b0e8@cox.net> (raw)
In-Reply-To: loom.20160318T133531-909@post.gmane.org
sri posted on Fri, 18 Mar 2016 13:36:50 +0000 as excerpted:
> Henk Slager <eye1tm <at> gmail.com> writes:
>
>> sri <toyours_sridhar <at> yahoo.co.in> writes:
>> >
>> > I Would like to know between 2 snapshots of a subvolume, can we
>> > identify what all blocks modified particular to that subvolume ?
>> >
>> > there can be many subvolume and snapshots present on the btrfs but i
>> > want only blocks modified since first snapshot for the specific
>> > subvolume. blocks should include metadata and data blocks.
>>
>> Not directly diff blocks, rather files, you could do something like
>> this:
>>
>> btrfs subvolume find-new [...]
>>
>>
> Thank you. As I checked only blocks related to file are shown.
>
> is there a way to get other blocks modified such as meta data such as
> inodes blocks modified and corresponding directory inode blocks along
> with files?
This would include the change data itself as well, and I'm not sure if
the format once the actual binary level changes themselves are removed is
practically consumable by humans or not, but it occurs to me that this is
precisely the information that btrfs send -p provides. If you can strip
the changes themselves out and what's left is either human readable or
can be processed to human readable, then it should be exactly what you're
after, the changed blocks, for data and metadata both.
--
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
prev parent reply other threads:[~2016-03-19 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 10:47 [PATCH] btrfs-progs: subvol sync: fix memory corruption, undersized array David Sterba
2016-03-17 14:10 ` Blocks changed since previous snapshot of subvolume sri
2016-03-17 20:36 ` Henk Slager
2016-03-18 13:36 ` sri
2016-03-19 0:13 ` Duncan [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='pan$7e7ac$bd9bc70$d69021d4$d407b0e8@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).