Hi rdiff-backup folks,
Since recent, during backing up I can see spike in IOPS up to 500 which exhaust
limit of a VM. Therefore backup process takes very long. I've straced a bit and
what I can see is: many failed lstat() syscalls:
% time seconds usecs/call callserrors syscall
o-fsync option to improve speed:
>
> --fsync, --no-fsync [opt] do (or not) often sync the file system
>(_not_ doing it is faster but can be dangerous)
>
>And, yes, the `rdiff-backup-data/increments` directory is used by
>rdiff-backup to keep track of file and directory changes.
>
f-backup goes as fast
>>as it can and I personally don't know an I/O-equivalent of "nice" (and
>>if you limit the I/O, the backup will be even slower).
>>
>>You could try the --no-fsync option to improve speed:
>>
>> --fsync, --no-fsync [opt] do (or not
>>>sequential is typically done to read/write the file's data.
>>>
>>>There is no real way to improve the situation, rdiff-backup goes as fast
>>>as it can and I personally don't know an I/O-equivalent of "nice" (and
>>>if you limit the I/O, t
f-backup goes as fast
>>as it can and I personally don't know an I/O-equivalent of "nice" (and
>>if you limit the I/O, the backup will be even slower).
>>
>>You could try the --no-fsync option to improve speed:
>>
>> --fsync, --no-fsync [opt] do (or not
