[Csync2] speed of "-cr /"

[Lars Ellenberg]

On Thu, Jun 10, 2010 at 06:29:08PM +1000, Aristedes Maniatis wrote:
> On 10/06/10 6:02 PM, Lars Ellenberg wrote:
> >For -R, its just config parsing, and SQL.
> >
> >For -c, it is one lstat for every record fetched.
> >100000 lstat calls may take some time;-)
> 
> In that case we've come a bit full circle with this conversation. Where we started:
> 
> * why does csync2 ignore the 'include' parameters when running -c?

why do you have 100000 "stale" no longer relevant records in your database?

> If the performance issue is lstat, why is csync2 running lstat on
> files which don't match the include/exclude parameters for the
> configuration which it is running?

Because they are not supposed to be in the database in the first place.

If you change your csync2.cfg to no longer include somthing that had
been included before, you need to csync2 -R to get rid of those entries.

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.