Hi,
I can't remember having seen this issue reported upstream, so, of
course, it didn't get fixed. I didn't notice because I keep an eye on
disk space, but I understand that it doesn't help if you've just stepped
into the issue, so I'd very much like to address it fast.
An enhancement
Control: found -1 2.2.2-1
On Fri, 2023-02-03 at 15:15 -0800, Otto Kekäläinen wrote:
> If you can still reproduce this issue or find other issues in how
> rdiff-backup itself works, please report it to upstream at
> https://github.com/rdiff-backup/rdiff-backup.
I no longer use rdiff-backup so I
Thanks Alexis, Tommi, Paul and many others for using rdiff-backup and
contributing to the bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310442!
The latest version of rdiff-backup 2.2.2-1 is now available in Debian
Sid and Bookworm: https://tracker.debian.org/pkg/rdiff-backup
If
On Thu, 2023-01-19 at 15:28 -0300, Pablo Mestre wrote:
> I'm going to look deeper into this issue and try to reproduce the bug.
FTR I managed to reproduce it by using GNOME Disks to create a small
disk image in a file, format it with ext4, mount it and repeatedly
backup a small dataset into it
Hi Paul
I'm going to look deeper into this issue and try to reproduce the bug.
Also I will contact the upstream.
Thanks for your reply
El 4/1/23 a las 00:33, Paul Wise escribió:
On Tue, 2023-01-03 at 17:56 -0300, Pablo Mestre wrote:
Several months have passed since the last check
Control: reopen -1
On Tue, 2023-01-03 at 17:56 -0300, Pablo Mestre wrote:
> Several months have passed since the last check regarding the bug and no
> response has been issued.
Looks like you didn't CC any of the people who were affected,
the Debian bug tracker does not subscribe anyone by
Hi
Thank you very much for reporting this error.
I would like to ask you if this error is still present in the most
recent versions of rdiff-backup. Currently after a series of
improvements and bug fixes, rdiff-backup is at version 2.0.5 [1]
It would be very helpful if you checked again if this
Another way to work-around this problem is to add a large (empty) file
on the backup volume (dd if=/dev/zero of=/backup/blob count=1000
bs=1M). Then, whenever rdiff-backup fails when the device becomes
full, remove that file and you can run --check-destination-dir to fix
up the repository.
--
Package: rdiff-backup
Version: 0.13.4-3
If the backup target fills up, there's no way to recover.
--check-destination-dir and --remove-older-than both just
complain about lack of space.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
9 matches
Mail list logo
