I think these requests, when materialized, would be very useful and become attractive features for NILFS2 because the natural advantages (COW & preserving previous versions of files) of NILFS2 become very convenient for the users to access to recover old versions of or deleted files. Actually, I thought it may be possible to use BASH scripting to list versions of files. The script may work by mounting checkpoints one by one retrogradely to find the specified files with different mtime until the absence of the file in a certain checkpoint. But the performance would be low. How to collect these versions for users to view easily(without mounting by the user again)? I don't know if it is possible to make a "hardlink" inode in the current "checkpoint" that points to an old version of file. This way, the duplication load could be spared. But I wondered if that would interfere with garbage collection. Just sharing some ideas. Anyway, thank you for taking these requests into consideration ^^ Anticipating, Eric Lan 2016-02-13 0:58 GMT+08:00 Ryusuke Konishi <konishi.ryusuke@xxxxxxxxxxxxx>: > On Fri, 5 Feb 2016 00:59:17 +0800, Eric Lan <tenoreamer@xxxxxxxxx> wrote: >> Hello, >> >> Recently, I have installed NILFS2 and feel it quite cool. I wonder if >> you are insterested in developing a program that can trace back all >> the check points to list the revision history of a specified file. >> With certain argument specified, these versions of files can be >> collected into a directory for the user to choose a good one from. >> >> Such program may be easily extended to have the function of >> "undelete". That is, to collect a series of versions of or the most >> recent version of a specific file that exist only in the past >> checkpoints. > > None of your requests look easy to implement ;) > > Anyway, I added them to the todo list at > http://nilfs.sourceforge.net/en/current_status.html > > Thanks, > Ryusuke Konishi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
