From: Goffredo Baroncelli <kreijack@gmail.com>
To: Chris Mason <chris.mason@oracle.com>,
"Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvol find-modified
Date: Fri, 26 Mar 2010 21:36:31 +0100 [thread overview]
Message-ID: <201003262136.32330.kreijack@libero.it> (raw)
In-Reply-To: <20100326202646.GG13680@think>
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.
>
> Great.
>
> -chris
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2010-03-26 20:36 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 [this message]
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=201003262136.32330.kreijack@libero.it \
--to=kreijack@gmail.com \
--cc=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 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).