linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Niederle" <mniederle@gmx.at>
To: linux-btrfs@vger.kernel.org
Subject: btrfs subvol find-new
Date: Fri, 26 Mar 2010 11:18:07 +0100	[thread overview]
Message-ID: <20100326111807.24dcc2f0@simplux> (raw)

I want to write a differential backup tool for btrfs snapshots.

The new "btrfs subvol find-new"-command sounds great on first encounter, but I'm
missing informations about updated directories. I would need a list of updated
directories to scan for deleted files.

I had a look at find_updated_files() in btrfs-list.c. To me it seems as if
the ioctl would only return the extents of regular files.

The function find_root_gen() in btrfs-list.c seems to return the newest
generation in a given snapshot. It would be nice to have this exported as a
user command (e.g. "btrfs subvol newest-gen") then one could use the output of 

btrfs subvol newest-gen <old snapshot>

(plus 1) as the input generation number to

btrfs subvol find-new <new snapshot> <gen+1>

(I'm using kernel 2.6.32.10 with the most current btrfs-kernel modules and
userland tools as of last Saturday.)

Greetings, Michael

             reply	other threads:[~2010-03-26 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 10:18 Michael Niederle [this message]
2010-03-26 13:22 ` btrfs subvol find-new Chris Mason
2010-03-26 18:51   ` btrfs subvol find-modified Dipl.-Ing. Michael Niederle
2010-03-26 19:36     ` Chris Mason
2010-03-26 20:22       ` Dipl.-Ing. Michael Niederle
2010-03-26 20:26         ` Chris Mason
2010-03-26 20:36           ` Goffredo Baroncelli
2010-03-26 21:11             ` Chris Mason
2010-03-26 22:23               ` Goffredo Baroncelli
2010-03-27  9:52               ` directory order in btrfs Dipl.-Ing. Michael Niederle
2010-03-26 21:38             ` btrfs subvol diff Dipl.-Ing. Michael Niederle

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=20100326111807.24dcc2f0@simplux \
    --to=mniederle@gmx.at \
    --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).