>The idea behind the cloneset is that most of the blocks (or files) >do not change in either source or target. This being the case its only necessary >to update the changed elements. This means updates are incremental. Once >the system has figured out what it needs to update its usable and if you access >an element that should be updated you will see the correctly updated version - even >though backgound resyncing is still in progress.
I still can't tell what you're describing. With RAID1 as well, only changed elements ever get updated. I have two identical filesystems, members of a RAIF set. I change one file. One file in each member filesystem gets updated, and I again have two identical filesystems. How would a cloneset work differently, and how would it be better? >This type of logic is great for backups. Can you give an example of using it for backup? -- Bryan Henderson IBM Almaden Research Center San Jose CA Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
