On 28/10/2011 11:03, john wrote:
Hi
The same problem as described here strucked me, too: When regressing a backup, rdiff-backup starts instantly consuming memory at quite a high rate, until it reaches 3GB. Then it dies with a memory allocation error, because it is running on
With 1.2.8 on NetBSD, I was seeing insanely long backup times, as in
over a week for a 300G filesystem on which little had changed.
With ktrace, I found the problem was that fsync() was called incredibly
often (per file checked?) and my backup drive was mounted with WAPBL
(metadata journaling),
On the web page, 1.2.8 is listed as stable and 1.3.3 as
development/unstable. But, it's been a long time.
So:
are there changes since 1.3.3?
if so, should there be a new release?
is anyone who has project admin permission around?
is 1.3.3 considered stable? As in, should I upgrade
Greg,
it seems this mailing list has not seen any message of the currently
responsible project leader for a long time.
I agree in thinking that 1.3.3 is the best and most stable version so far,
It has still bugs though.
Cheers
David.
-Ursprüngliche Nachricht-
Von:
