Henk Slager <eye1tm <at> gmail.com> writes: > > sri <toyours_sridhar <at> yahoo.co.in> writes: > > > > > Hi, > > > > 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 <newer_snapshot> `btrfs subvolume show > <older_snapshot> | grep Generation | awk '{print $2}'` | awk '{ print $17 }' > | sort | uniq > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo <at> vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >
Thank you. As I checked only blocks related to file are shown. sample output: btrfs subvolume find-new snap2 15 inode 264 file offset 0 len 8192 disk start 351559680 offset 0 gen 16 flags NONE mman.h inode 265 file offset 0 len 8192 disk start 351567872 offset 0 gen 16 flags NONE mount.h inode 266 file offset 0 len 2374 disk start 0 offset 0 gen 16 flags INLINE msg.h inode 267 file offset 0 len 12288 disk start 351576064 offset 0 gen 16 flags NONE mtio.h transid marker was 16 I think it showed blocks changed w.r.t file data block. 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? Above fs is created on 2 disks /dev/sdd and /dev/sdd of 3 gb. No raid configured. I think it is just strped with 6gb size around. How should I interpret: inode 266 file offset 0 len 2374 disk start 0 offset 0 gen 16 flags INLINE msg.h ?? disk start is 0 here. Is this w.r.t what? and offset 0 is offset inside block represented by disk start ? thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html