I've been working with NILFS for a few weeks now, and find that the underlying filesystem is a great solution to some problems that we are trying to solve. However, the userspace utilities are far too unwieldy to work with as a practical matter.
The only missing piece is some way to automatically (via cleanerd maybe) create snapshots of the nearest checkpoint at an interval of "X" minutes, with a lifetime of "Y" minutes. Currently, there is no good way to automate this process, and the system creates such a long list of checkpoints that finding a good candidate for creating a "mountable snapshot" to restore from is prohibitively time-consuming. Ideally, the behavior of the feature should create a snapshot every X minutes from the checkpoint closest in time to the interval, and revert to checkpoint status any that are older than "Y" minutes old. Basically the goal is to keep a manageable number of snapshots to minimize the impact of a corrupted database file. Since backups are done every 24 hours here, we would set the lifetime to 1440 minutes and the interval to 15 minutes, thus limiting the worst-case data loss to 15 minutes, and with the advantage of only having to look through a list of 96 snapshots rather than potentially hundreds or thousands of checkpoints. It looks like all the code exists currently to do this, but it needs to be integrated a just a little bit more to enable this behavior. _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
