> If your dir contains 10.000 files you sync the parents' mtime 10.000 times, > whereas the optimal solution would sync it only once (well, obviously). > So this cannot be the optimal strategy to solve the problem. > Additionally one can not be content with the datapath during healing right > through the client, because the data has to be processed twice server->client, > client->server. If you are healing a huge amount of data your healing client > is quite stressed by the healing, with merely no (network) performance left > for its real job. > For sure your idea of implementation is straight forward for the case of > "healing-by-single-stating". But I heard on the list you are planning for > "auto-healing" anyways, and that would possibly be a good chance to implement > a simple user-space tool that does healing in an optimized way. For the 2.1 release we plan to bring in self-healing in the background and also healing only the differences between files, and not the entire file like now. We will keep this issue in mind while designing it. > That sound like taking quite some time. Are we talking about days, weeks, > months here? A few weeks. Vikas
