From: Chris Mason <chris.mason@oracle.com>
To: kreijack@libero.it
Cc: "Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvol find-modified
Date: Fri, 26 Mar 2010 17:11:24 -0400 [thread overview]
Message-ID: <20100326211124.GK13680@think> (raw)
In-Reply-To: <201003262136.32330.kreijack@libero.it>
On Fri, Mar 26, 2010 at 09:36:31PM +0100, Goffredo Baroncelli wrote:
> On Friday 26 March 2010, Chris Mason wrote:
> > On Fri, Mar 26, 2010 at 09:22:07PM +0100, Dipl.-Ing. Michael Niederle wrote:
> > > Hi, Chris!
> > >
> > > > Add an optional timestamp field to filter
> > > > files that have changed since a given timestamp.
> > >
> > > Is there a possibility to derive the timestamp directly from the
> generation
> > > number?
> >
> > I'm afraid not.
> >
> > >
> > > If we have a "-e"-switch for printing extent-information we could also
> have
> > > another switch to decide whether to print directory-information or not and
> > > combine find-new and find-modified into a single command.
> >
> > Yes, that's the direction I'd like to see.
> >
> > >
> > > Meanwhile I have implemented the (very simple) command
> > >
> > > btrfs subvolume max-gen <path>
> > > Print the highest generation number in a filesystem.
> > >
>
> It is possible to combine the commands max-gen and find-new ? Something like:
>
> $ btrfs subvol find-new subvol1 snap1
>
> I think that the generation number is useful only from a developer point of
> view. But from an user point of view a command which is able to compare two
> snapshot if more useful.
In general, the end goal is backing up a snapshot the changes from a
point in time to right now. We don't actually need a snapshot to do
this, we just need the generation number and (optionally) a timestamp.
So, we could store these things into a state file that gets fed into the
next backup, but I'd like to keep a command that can print them as well.
-chris
next prev parent reply other threads:[~2010-03-26 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 10:18 btrfs subvol find-new Michael Niederle
2010-03-26 13:22 ` 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 [this message]
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=20100326211124.GK13680@think \
--to=chris.mason@oracle.com \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=mniederle@gmx.at \
/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.