>A cloneset is only syncronized at the point in time that you tell it to resync. >The source and target fs are useable independently. When you resync the >target is reset to be indentical to the source at the point in time of the sync. >Its also immediatly useable - the sync and access to the source and target >are coordinated so users of the target see the correct data, even if the sync >is still running in background. > >This allows things likes: > >... These applications sure seem like a better fit for ordinary snapshots. It looks like with the cloneset, there's a whole superfluous copy of the filesystem, whereas with a snapshot, you have to have storage space and I/O time only for data that changes after the snapshot. I'm sure I could dream up an application for this -- maybe you want that second copy as a backup or it gives you additional data transfer capacity. I just don't see the panacea so far. -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
