>> Several implementations of union file system fusion were evaluated. >> The results of the evaluation is shown at the below link- >> http://www.4shared.com/download/7IgHqn4tce/1_online.png > > As far as I know, aufs supports NFS branches and also you can export > aufs via NFS. > For example, > http://sourceforge.net/p/aufs/mailman/message/20639513/ > > I am not sure of this. These results were given to me by Cern and I really have to check this out to make sure it works. >> 2. if only the file metadata are modified, then do not >> copy the whole file on the read-write files system but >> only the metadata (stored with a file named as the file >> itself prefixed by '.me.') > > Once I have considered such approach to implement it in aufs. > But I don't think it a good idea to store metadata in multiple places, > one in the original file and the other is in .me. file. > For such purpose, a "block device level union" (instead of filesystem > level union) may be an option for you, such as "dm snapshot". > I imagine that this would make things more complicated as ideally this should be done in a filesystem driver. Again a "block device level union" would all the more have lesser chances of getting this filesystem driver included in the mainline kernel as kernel maintainers prefer the drivers to be as simple as possible. Before taking any approach I really want to discuss it with kernel maintainers as to what solution they are expecting. The truth is that the architecture of Linux kernel is such that a stackable filesystem implementation would surely involve some vicious hacks. Regards, Saket Sinha -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
