cwillu wrote (ao):

quoted

While developing snapper I faced similar problems and looked at
find-new but unfortunately it is not sufficient. E.g. when a file
is deleted find-new does not report anything, see the reply to my
mail here one year ago [1]. Also for newly created empty files
find-new reports nothing, the same with metadata changes.

For a system-wide undo'ish sort of thing that I think autosnapper is
going for, it should work quite nicely, but you're right that it
doesn't help a whole lot with a backup system.  It can't tell you
which files were touched or deleted, but it will still tell you that
_something_ in the subvolume was touched, modified or deleted (at
least, as of the last commit), which is all you need if you're only
ever comparing it to its source.

Tar can remove deleted files for you during a restore. This is (imho) a
really cool feature of tar, and I use it in combination with btrfs
snapshots.

https://www.gnu.org/software/tar/manual/tar.html#SEC94

"The option `--listed-incremental' instructs tar to operate on an
incremental archive with additional metadata stored in a standalone
file, called a snapshot file. The purpose of this file is to help
determine which files have been changed, added or deleted since the last
backup"

"When extracting from the incremental backup GNU tar attempts to restore
the exact state the file system had when the archive was created. In
particular, it will delete those files in the file system that did not
exist in their directories when the archive was created"

	Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net