Package: duplicity Version: 0.8.17-1+b1 Severity: normal X-Debbugs-Cc: none, Barak A. Pearlmutter <ba...@pearlmutter.net>
I ran out of storage on my remote, so I tried to reclaim some with $ duplicity remove-all-but-n-full 1 --force "${transport}/${target}" But afterwards there are just a few meg used in the target directory instead of many hundreds of gig. It would appear that a full backup failed due to space exhaustion on the remote, but that the failed full backup is (inappropriately) included in remove-all-but-n-full's count. This is just my best guess as to what's going on. But I am 100% sure that "duplicity remove-all-but-n-full 1" sometimes does not leave an intact full backup, instead it deletes nearly everything. This has happened to me repeatedly, so I'm sure there's an actual problem. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (490, 'testing'), (450, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages duplicity depends on: ii gnupg 2.2.20-1 ii libc6 2.31-5 ii librsync2 2.3.1-1 ii python3 3.9.0-4 ii python3-fasteners 0.14.1-2 ii python3-future 0.18.2-4 ii python3-lockfile 1:0.12.2-2.2 Versions of packages duplicity recommends: pn python3-oauthlib <none> ii python3-paramiko 2.7.2-1 ii python3-pexpect 4.6.0-4 ii python3-urllib3 1.25.11-1 ii rsync 3.2.3-2 Versions of packages duplicity suggests: pn lftp <none> pn ncftp <none> pn par2 <none> pn python3-boto <none> ii python3-pip 20.1.1-2 pn python3-swiftclient <none> pn tahoe-lafs <none> -- no debconf information