Hi, > Basically I believe this is possible, but one problem is how to > realize rollback of the remote nilfs which will become required when > allowing user's updates or garbage collection on the remote device > after synchronization.
let's call them master / slave, I'm confused which one is remote :) I assume only the master is writable and slaves don't do any changes or cleaning. Require that all checkpoints from last sync to present are still existing. Upon dump on master, cleanerd has to be suspended and may resume after dump. Does that make things easier? By the way: When I completely disable cleanerd on the master, wouldn't it be possible to define a byte-range on the block device which makes up the difference between two checkpoints and copy that to the slaves? Regards, Pierre Beck _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
