You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NILFS2 is filesystem that by design creates snapshot after any data change, so it can be easily rolled back to any time without specificaly making snapshots at that time using cron... Is it possible to mimick such feature using inotify to watch file changes and make snapshots accordingly? Maybe not for every inotify event, but at least for some.
The text was updated successfully, but these errors were encountered:
I haven't done much research lately, but many years ago I was looking at inotify and found that you have to have a watch on every directory in the filesystem to get all change events. For a big file-system, this may be problematic. It probably would be ok for smaller filesystems.
I wonder if there's another mechanism that would be better? Like dtrace, or is there some way to see if the ZFS master block has been updated? Or maybe take regular snapshots, but then go through and preen the older ones that have a "USED" size of 0 (which I think means it contains no deltas, so no written data).
NILFS2 is filesystem that by design creates snapshot after any data change, so it can be easily rolled back to any time without specificaly making snapshots at that time using cron... Is it possible to mimick such feature using inotify to watch file changes and make snapshots accordingly? Maybe not for every inotify event, but at least for some.
The text was updated successfully, but these errors were encountered: