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 -- 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
